On 11/11/2015 15:06, Neil Watson wrote: > So, osa-dispatcher, jabberd, and osad (on the client) all seem to be > running, but package updates scheduled from the web do not seem to be > going out. I scheduled on for as soon as possible and 20 minutes later > it is still not done. > > On the host status the OSA status give me mixed signals: > > OSA Status: offline as of unknown > Last pinged: 11/11/15 9:42:43 AM EST > Ping System > > There are no errors in the osad or osa-dispatcher logs. There are no > firewalls and selinux is disabled on both hosts. How can I troubleshoot > this problem? > Hi Neil,
I've seen similar when dealing with clients that registered using the "wrong" name initially (although that was caused by a different circumstance than yours) if you increase the debug logging of osa-dispatcher (osa-dispatcher.debug option in rhn.conf) and restart you may be able to see the JID to which the dispatcher is trying to send messages. If this JID is wrong, osad clients won't be able to pick the messages up. If that's the case, deleting the system from spacewalk should remove the jid and a subsequent registration should restore it with the correct name. I haven't come across a satisfactory way of achieving this for a large number of clients though, without re-registration against spacewalk. Regards, Olly _______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
