[Spacewalk-list] Starting osa-dispatcher hangs

[Will Cladek]

Okay, so here's what I've got.  jabberd starts okay:

Initializing jabberd processes ...
Starting router:                                           [  OK  ]
Starting sm:                                               [  OK  ]
Starting c2s:                                              [  OK  ]
Starting s2s:                                              [  OK  ]

However, immediately after I check its status and see this:

router (pid 8167) is running...
sm dead but subsys locked
c2s dead but subsys locked
s2s dead but subsys locked

Not sure if those "dead but subsys locked" are normal.

Running osa-dispatcher from the command line gives me:

Spacewalk 8391 2013/11/13 14:44:12 -04:00: ('Traceback (most recent call last):\n  File "/usr/share/rhn/osad/jabber_lib.py", line 252, in setup_connection\n    c = self._get_jabber_client(js)\n  File "/usr/share/rhn/osad/jabber_lib.py", line 309, in _get_jabber_client\n    c.connect()\n  File "/usr/share/rhn/osad/jabber_lib.py", line 567, in connect\n    jabber.Client.connect(self)\n  File "/usr/lib/python2.4/site-packages/jabber/xmlstream.py", line 488, in connect\n    raise socket.error("Unable to connect to the host and port specified")\nerror: Unable to connect to the host and port specified\n',)

And the relevant piece of osa-dispatcher.log appears to be:

2013/11/13 14:44:12 -04:00 8391 0.0.0.0: osad/jabber_lib.connect('Attempting to connect',)
2013/11/13 14:44:12 -04:00 8391 0.0.0.0: osad/jabber_lib.print_message('socket error',)
2013/11/13 14:44:12 -04:00 8391 0.0.0.0: osad/jabber_lib.print_message('Could not connect to jabber server', '[hostname]')
2013/11/13 14:44:12 -04:00 8391 0.0.0.0: osad/jabber_lib.setup_connection('ERROR', 'Traceback (most recent call last):\n  File "/usr/share/rhn/osad/jabber_lib.py", line 252, in setup_connection\n    c = self._get_jabber_client(js)\n  File "/usr/share/rhn/osad/jabber_lib.py", line 309, in _get_jabber_client\n    c.connect()\n  File "/usr/share/rhn/osad/jabber_lib.py", line 567, in connect\n    jabber.Client.connect(self)\n  File "/usr/lib/python2.4/site-packages/jabber/xmlstream.py", line 488, in connect\n    raise socket.error("Unable to connect to the host and port specified")\nerror: Unable to connect to the host and port specified\n')
2013/11/13 14:44:12 -04:00 8391 0.0.0.0: osad/jabber_lib.setup_connection('Could not connect to any jabber server',)
2013/11/13 14:44:12 -04:00 8391 0.0.0.0: osad/jabber_lib.main('Unable to connect to jabber servers, sleeping 10 seconds',)

In some older thread I read that I should try emptying out /var/lib/jabberd/db, but that directory was already empty.

Is there some obvious problem with my jabberd here?

Thanks,

Will

On 11/13/2013 2:04 PM, Justin Edmands wrote:
> On Wed, Nov 13, 2013 at 1:27 PM, Will Cladek <will.cladek at nrl.navy.mil <mailto:will.cladek at nrl.navy.mil>> wrote:
>
>     I just upgraded my Spacewalk from 1.8 to 1.9 and then 2.0.  In both the 1.9 and 2.0 updates, starting the spacewalk-server just hangs on osa-dispatcher (actual server name masked):
>
>     Starting spacewalk services...
>     Initializing jabberd processes ...
>     Starting router:                                           [  OK  ]
>     Starting sm:                                               [  OK  ]
>     Starting c2s:                                              [  OK  ]
>     Starting s2s:                                              [  OK  ]
>     Starting tomcat5:                                          [  OK  ]
>     Waiting for tomcat to be ready ...
>     Starting httpd: httpd: Could not reliably determine the server's fully qualified domain name, using [xxx] for ServerName
>                                                                 [  OK  ]
>     Starting osa-dispatcher:
>
>
>     At this point I can at least interact with the web interface and get updates, but it never completes this startup process.  I set osa-dispatcher.debug in rhn.conf, but osa-dispatcher.log shows nothing, nor do the other logs show anything relevant.  Any suggestions as to why osa-dispatcher won't start?
>
>     _________________________________________________
>     Spacewalk-list mailing list
>     Spacewalk-list at redhat.com <mailto:Spacewalk-list at redhat.com>
>     https://www.redhat.com/__mailman/listinfo/spacewalk-__list <https://www.redhat.com/mailman/listinfo/spacewalk-list>
>
>
>
> Maybe run the osa-dispatcher command instead :
>
> osa-dispatcher --help
> Usage: osa-dispatcher [options]
>
> Options:
>    -v, --verbose             Increase verbosity
>    -N, --nodetach         Suppress backgrounding and detachment of the process
>    --pid-file=PID_FILE   Write to this PID file
>    --logfile=LOGFILE    Write log information to this file
>    -h, --help                 show this help message and exit
>
>
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list
>