[Spacewalk-list] error jabber after upgrade 0.5 => 0.6

Joshua Roys joshua.roys at gtri.gatech.edu
Thu Sep 10 19:45:56 UTC 2009


On 09/10/2009 03:30 PM, Michiel van Es wrote:
> [root at devmx01 ~]# sm -D
> Thu Sep 10 21:22:51 2009 [notice] starting up
> Thu Sep 10 21:22:51 2009 [notice] id: devmx01.buro.info.nl
> Thu Sep 10 21:22:51 2009 [info] process id is 15647, written to
> /var/lib/jabberd/pid/sm.pid
> Thu Sep 10 21:22:51 2009 storage.c:94 adding arbitrary types to driver 'db'
> Thu Sep 10 21:22:51 2009 storage.c:117 driver not loaded, trying to init
> Thu Sep 10 21:22:51 2009 [info] loading 'db' storage module
> Thu Sep 10 21:22:51 2009 storage.c:139 preloaded module 'db' (not
> initialized yet)
> Thu Sep 10 21:22:51 2009 storage.c:158 calling driver initializer
>
> [root at devmx01 ~]# c2s -D
> Thu Sep 10 21:23:03 2009 [notice] starting up
> Thu Sep 10 21:23:03 2009 [info] process id is 15701, written to
> /var/lib/jabberd/pid/c2s.pid
> Thu Sep 10 21:23:03 2009 [notice] modules search path: /usr/lib/jabberd/
> Thu Sep 10 21:23:03 2009 [info] loading 'db' authreg module
> Thu Sep 10 21:23:03 2009 authreg.c:73 preloaded module 'db' (not
> initialized yet)
>

Michiel,

What version of jabberd do you have?
- should be 2.2.8 or better
Are you x86 or x86_64?
- if you're x86_64, module search path needs to be /usr/lib64/jabberd
-- c2s.xml, <authreg> <path> ... </path>
-- sm.xml, <storage> <path> ... </path>
Do c2s or sm give any other output?  It looks like they are crashing? 
Are they still running after the above?
Can they read/write the db location specified in their configs?
- mine is /var/lib/jabberd/db
- try: sudo -u jabber stat /var/lib/jabberd/db/*
-- c2s.xml, <db> <path> ... </path>
-- sm.xml, <db> <path> ... </path>

Good luck,

Joshua Roys




More information about the Spacewalk-list mailing list