What version of Spacewalk are you running? You likely need to reset the osad credentials on the clients. This typically only occurs when the jabber database has been corrupted.
On the clients, run the below commands: rm -f /etc/sysconfig/rhn/osad-auth.conf ; service osad restart You may find the below links helpful https://fedorahosted.org/spacewalk/wiki/OsadHowTo https://fedorahosted.org/spacewalk/wiki/JabberAndOSAD On Aug 30, 2016 4:43 PM, "Konstantin Raskoshnyi" <konra...@gmail.com> wrote: > Something strange with some of my osad clients ~1/3 > > They don't pickup any jobs from osa-dispatcher, no any errors during > starting the service, > > also if I restart osad on sp I see logs: > > Aug 30 14:32:20 spacewalk15 jabberd/c2s[51907]: [142] > [::ffff:172.90.7.220, port=43046] disconnect > jid=osad-e43e326...@spacewalk15.ooma.internal/osad, > packets: 29, bytes: 3738 > Aug 30 14:32:20 spacewalk15 jabberd/sm[51904]: session ended: > jid=osad-e43e326...@spacewalk15.ooma.internal/osad > Aug 30 14:32:20 spacewalk15 jabberd/sm[51904]: user unloaded > jid=osad-e43e326...@spacewalk15.ooma.internal > Aug 30 14:32:20 spacewalk15 jabberd/c2s[51907]: [142] traditional.digest > authentication succeeded: osad-e43e3265db@/osad ::ffff:172.90.7.220:43454 > TLS > Aug 30 14:32:20 spacewalk15 jabberd/c2s[51907]: [142] requesting session: > jid=osad-e43e326...@spacewalk15.ooma.internal/osad > Aug 30 14:32:20 spacewalk15 jabberd/sm[51904]: session started: > jid=osad-e43e326...@spacewalk15.ooma.internal/osad > > So looks like everything should be fine > > _______________________________________________ > Spacewalk-list mailing list > Spacewalk-list@redhat.com > https://www.redhat.com/mailman/listinfo/spacewalk-list >
_______________________________________________ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
