Hi,
same problem here, but we have:
client OSA Status is offline
OSA Ping System does not work
Scheduling any action does not trigger the client's osad to invoke rhn_check
I just have followed the same suggestions
<https://www.redhat.com/archives/spacewalk-list/2010-November/msg00181.html>like
Ron Helzer, but without luck ...
I have no errors in any log files:
jabber/sm create users and start sessions
jabber/c2s do registartions and authentications
jabber/s2s is connectd to the router at 127.0.0.1
osad/osa_dispatcher is connected to server
All was working well till upgrade, I really don't know what to do now ...
Regards,
Marco
i can't offer much help at the moment, i'm afraid, but can say that i
am seeing exactly the same behaviour.
we just upgraded to 1.2 a couple of days ago.
everything was working correctly in 1.1, but since the upgrade, the
osa-dispatcher fails to run correctly in the manner described below.
haven't had much time to delve into it just yet, but have tried the
suggestions mentioned.
any advice on what else may be worth tying would me much appreciated.
thanks,
richard
*From:* [email protected]
[mailto:[email protected]] *On Behalf Of *Ron Helzer
*Sent:* 09 December 2010 06:41
*To:* [email protected]
*Subject:* [Spacewalk-list] Need help to troubleshoot osa-dispatcher
problem.
After upgrading from Spacewalk 1.1 to 1.2; osa-dispatcher seems to
have quit working. I have exhausted my troubleshooting skills and
have been unable to determine the cause.
What works:
client OSA Status is online
OSA Ping System works
What doesn't work:
Scheduling any action does not trigger the client's osad to invoke
rhn_check
Package versions:
osa-dispatcher-5.9.44-1.el5
jabberd-2.2.11-2.el5
spacewalk-setup-jabberd-1.3.1-1.el5
I have followed the instructions at
https://www.redhat.com/archives/spacewalk-list/2010-November/msg00181.html
to update the jabberd configuration. Also tried some of the
suggestions offered in
https://www.redhat.com/archives/spacewalk-list/2010-November/msg00173.html
to no avail.
Results of `tail -f /var/log/rhn/osa-dispatcher.log | grep osa_dispatcher`
2010/12/09 01:28:17 -04:00 13878 0.0.0.0 <http://0.0.0.0>:
osad/osa_dispatcher.process_once
2010/12/09 01:28:17 -04:00 13878 0.0.0.0 <http://0.0.0.0>:
osad/osa_dispatcher.process_once('Clients to be pinged:', None)
2010/12/09 01:28:17 -04:00 13878 0.0.0.0 <http://0.0.0.0>:
osad/osa_dispatcher.process_once('before process',)
2010/12/09 01:28:17 -04:00 13878 0.0.0.0 <http://0.0.0.0>:
osad/osa_dispatcher.process_once('after process',)
2010/12/09 01:28:17 -04:00 13878 0.0.0.0 <http://0.0.0.0>:
osad/osa_dispatcher.process_once('Not notifying jabber nodes',)
It's as if osa-dispatcher just doesn't see that there's a pending
event it should notify osad of...
--
-----------------------------------
|Marco Giunta - SISSA Computer Staff|
|Via Bonomea, 265 |
|34136 - Trieste, Italy |
|Tel: +39-40-3787-503 |
|Fax: +39-040-3787-528 |
|e-mail: giunta AT sissa.it |
-----------------------------------
_______________________________________________
Spacewalk-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-list
