[Spacewalk-list] question about upgrade 0.4 - 0.5 : Oracle schema upgrade failure

Milan Zazrivec mzazrivec at redhat.com
Tue May 12 13:11:48 UTC 2009


On Tuesday 12 May 2009 14:51:25 Michiel van Es wrote:
> Milan Zazrivec wrote:
> > On Tuesday 12 May 2009 14:23:31 Michiel van Es wrote:
> >> That did the trick! :)
> >> Thanks!
> >>
> >> I have only an error with jabber..I know there is a bug with Jabberd 2.2
> >> but I still got the 2.0 version:
> >>
> >>
> >> [root at devmx01 ~]# rpm -qa | grep jabber
> >> jabberd-2.0s10-3.42.el5
> >> jabberpy-0.5-0.17.el5
> >> jabberd-selinux-1.4.0-6.el5
> >>
> >>
> >>
> >> May 12 14:20:07 devmx01 jabberd/c2s[1335]: starting up
> >> May 12 14:20:07 devmx01 jabberd/c2s[1335]: couldn't open
> >> /var/lib/jabberd/pid/c2s.pid for writing: No such file or directory
> >> May 12 14:20:07 devmx01 jabberd/c2s[1335]: db: couldn't open
> >> environment: No such file or directory
> >> May 12 14:20:07 devmx01 jabberd/c2s[1335]: failed to initialise auth
> >> module 'db'
> >> May 12 14:20:07 devmx01 jabberd/sm[1333]: starting up
> >> May 12 14:20:07 devmx01 jabberd/sm[1333]: id: devmx01.buro.info.nl
> >> May 12 14:20:07 devmx01 jabberd/sm[1333]: couldn't open
> >> /var/lib/jabberd/pid/sm.pid for writing: No such file or directory
> >> May 12 14:20:07 devmx01 jabberd/sm[1333]: db: couldn't open environment:
> >> No such file or directory
> >> May 12 14:20:07 devmx01 jabberd/sm[1333]: initialisation of storage
> >> driver 'db' failed
> >> May 12 14:20:07 devmx01 jabberd/sm[1333]: failed to initialise one or
> >> more storage drivers, aborting
> >> May 12 14:20:07 devmx01 jabberd/router[1331]: starting up
> >> May 12 14:20:07 devmx01 jabberd/router[1331]: process id is 1331,
> >> written to /var/run/jabberd/router.pid
> >> May 12 14:20:07 devmx01 jabberd/resolver[1332]: starting up
> >> May 12 14:20:07 devmx01 jabberd/router[1331]: loaded user table (1
> >> users) May 12 14:20:07 devmx01 jabberd/router[1331]: [0.0.0.0,
> >> port=5347] listening for incoming connections
> >> May 12 14:20:07 devmx01 jabberd/resolver[1332]: process id is 1332,
> >> written to /var/run/jabberd/resolver.pid
> >> May 12 14:20:07 devmx01 jabberd/router[1331]: shutting down
> >> May 12 14:20:07 devmx01 jabberd/resolver[1332]: attempting connection to
> >> router at 127.0.0.1, port=5347
> >> May 12 14:20:07 devmx01 jabberd/resolver[1332]: shutting down
> >> May 12 14:20:07 devmx01 jabberd/s2s[1334]: starting up (interval=3,
> >> queue=60, keepalive=0, idle=86400)
> >> May 12 14:20:07 devmx01 jabberd/s2s[1334]: couldn't open
> >> /var/lib/jabberd/pid/s2s.pid for writing: No such file or directory
> >> May 12 14:20:07 devmx01 jabberd/s2s[1334]: attempting connection to
> >> router at 127.0.0.1, port=5347
> >> May 12 14:20:07 devmx01 jabberd/s2s[1334]: shutting down
> >>
> >>
> >> What can be wrong?
> >
> > The config files for jabberd are wrong. For this to work you need
> > to use jabberd configuration files from Spacewalk 0.4 (or earlier).
>
> But I didn't upgrade jabberd? (see my version above) :'-(
> Do I have to check all configfiles manually?

You may not have upgraded jabberd, but the config files that come
with spacewalk-config were updated anyway. If you want to use
jabberd v2.0, you need to use older config files (and update the location
of ssl certificate -- server.pem in those).

-Milan




More information about the Spacewalk-list mailing list