[Spacewalk-list] trouble upgrading sw 0.5 to 0.6

[Milan Zazrivec]

On Tuesday 25 August 2009 17:44:58 Michiel van Es wrote:
> Hi,
>
> I am trying to upgrade a Spacewalk 0.5 version to 0.6
> running CentOS 5.3 i386 as OS.
> I follow the instructions on:
> https://fedorahosted.org/spacewalk/wiki/HowToUpgrade
> and get the following error when I want to upgrade jabberd:
>
> [root at devmx01 backup]# yum upgrade jabberd
> Loaded plugins: fastestmirror, priorities
> Loading mirror speeds from cached hostfile
>   * epel: ftp.nluug.nl
>   * base: mirror.leaseweb.com
>   * updates: mirror.leaseweb.com
>   * addons: mirror.leaseweb.com
>   * extras: mirror.leaseweb.com
> 85 packages excluded due to repository priority protections
> Setting up Upgrade Process
> Resolving Dependencies
> There are unfinished transactions remaining. You mightconsider running
> yum-compl
>                ete-transaction first to finish them.
> --> Running transaction check
> ---> Package jabberd.i386 0:2.2.8-2.el5 set to be updated
> --> Processing Dependency: libgc.so.1 for package: jabberd
> --> Processing Dependency: libmysqlclient.so.15(libmysqlclient_15) for
> package:
>                jabberd
> --> Processing Dependency: libmysqlclient.so.15 for package: jabberd
> --> Processing Dependency: libudns.so.0 for package: jabberd
> --> Processing Dependency: libgsasl.so.7 for package: jabberd
> --> Running transaction check
> ---> Package udns.i386 0:0.0.9-3.el5 set to be updated
> ---> Package libgsasl.i386 0:0.2.29-1.el5 set to be updated
> --> Processing Dependency: libntlm.so.0 for package: libgsasl
> ---> Package mysql.i386 0:5.0.45-7.el5 set to be updated
> ---> Package gc.i386 0:7.1-5.el5 set to be updated
> --> Running transaction check
> ---> Package libntlm.i386 0:1.0-1.el5 set to be updated
> --> Finished Dependency Resolution
>
> Dependencies Resolved
>
> ===========================================================================
>===== Package            Arch           Version                 Repository
> Size
> ===========================================================================
>===== Updating:
>   jabberd            i386           2.2.8-2.el5             epel
>     593 k
> Installing for dependencies:
>   gc                 i386           7.1-5.el5               epel
>     151 k
>   libgsasl           i386           0.2.29-1.el5            epel
>     100 k
>   libntlm            i386           1.0-1.el5               epel
>      43 k
>   mysql              i386           5.0.45-7.el5            base
>     4.1 M
>   udns               i386           0.0.9-3.el5             epel
>      63 k
>
> Transaction Summary
> ===========================================================================
>===== Install      5 Package(s)
> Update       1 Package(s)
> Remove       0 Package(s)
>
> Total size: 5.1 M
> Is this ok [y/N]: y
> Downloading Packages:
> Running rpm_check_debug
> Running Transaction Test
> Finished Transaction Test
>
>
> Transaction Check Error:
>    file /etc/jabberd/server.pem from install of jabberd-2.2.8-2.el5.i386
> conflict
>               s with file from package
> rhn-org-httpd-ssl-key-pair-devmx01.buro-1.0-1.noarch
>
> DOes anyone know how to solve this?
>
> I tried to run the next cert steps:
> ===============
> At this point, jabberd ver. 2.2.8 should be installed on your system.
>
> For jabberd, osa-dispatcher and osad clients to work correctly, SSL
> certificate used by jabberd services needs to have correct user & group
> ownership (user & group == jabber).
>
> Check user and group ownership of file containing SSL certificate and
> private key used by jabberd services for setting up encrypted channels:
>
> # ls -l /etc/pki/spacewalk/jabberd/server.pem
>
> This will either say "jabber" :
>
> # ls -l /etc/pki/spacewalk/jabberd/server.pem
> -rw------- 1 jabber jabber 7244 Aug  6 16:53
> /etc/pki/spacewalk/jabberd/server.pem
>
> or it will say "jabberd" :
>
> # ls -l /etc/pki/spacewalk/jabberd/server.pem
> -rw------- 1 jabberd jabberd 7244 Aug  7 10:20
> /etc/pki/spacewalk/jabberd/server.pem
>
> If the user and group ownership says "jabber", you can safely skip rest
> of this step and continue with a step named "Package upgrade" below.
>
> If the user and group ownership says "jabberd", you need to do following
> steps:
>
> As root run:
>
> # getent passwd jabberd && userdel -r jabberd
>
> As root, run upgrade-cert.sh script attached to this page:
>
> # ./upgrade-cert.sh
>
> This script will try to re-create new rpm package containing your
> original SSL certificates and instruct you to do these additional steps
> that you are required to do:
>
>      * Uninstall original package containing your certificate files
>
>      * Install updated package with your original certificate files
> =================
>
> But got the following error:
>
> [root at devmx01 backup]# getent passwd jabberd && userdel -r jabberd
> jabberd:x:100:101:Jabber Daemon:/:/bin/false
> userdel: / not owned by jabberd, not removing
> [root at devmx01 backup]# cd /root/
> [root at devmx01 ~]# vim scrippie.sh
> [root at devmx01 ~]# sh scrippie.sh
>
> ...working...
>
> ERROR: unhandled exception occurred:
> Traceback (most recent call last):
>    File "/usr/bin/rhn-ssl-tool", line 58, in ?
>      sys.exit(mod.main() or 0)
>    File "/usr/share/rhn/certs/rhn_ssl_tool.py", line 1221, in main
>      ret = _main() or 0
>    File "/usr/share/rhn/certs/rhn_ssl_tool.py", line 1181, in _main
>      genServerRpm(DEFS, options.verbose)
>    File "/usr/share/rhn/certs/rhn_ssl_tool.py", line 1029, in genServerRpm
>      raise Exception("No jabber/jabberd user on system")
> Exception: No jabber/jabberd user on system
>
> Certificate RPM regeneration failed:
>
> Can anyone tell what I am doing wrong?

Well, nothing really. Your problem here is that you are upgrading jabberd 2.0
to jabberd 2.2.8.

Given that you have deleted jabberd user already, what you gotta do now is:

# getent group jabber || groupadd -r jabber
# getent passwd jabber || \
   useradd -r -g jabber -d /var/lib/jabberd -s /sbin/nologin \
   -c "Jabber Server" jabber
# sh scrippie.sh

Now do what scrippie.sh tells you to do and then start with the 0.5 -> 0.6
upgrade again, from the very beginning, no steps skipped.

-Milan