Check for errors in the /var/log/rhn/rhn_server_xmlrpc.log logfile. The client's OSAD credentials may not be good anymore. You can try this:
On the client system, run: # service osad stop ; rm -f /etc/sysconfig/rhn/osad-auth.conf ; service osad start Worst case scenario, you need to rebuild the jabberd database on the Spacewalk server. This can be safely done by doing the following on the Spacewalk server: # service jabberd stop ; rm -Rf /var/lib/jabberd/db/* ; service jabberd start The following document covers a lot of the common OSAD\Jabber issues https://fedorahosted.org/spacewalk/wiki/JabberAndOSAD On Sat, Jan 17, 2015 at 8:53 PM, Dewangga Bachrul Alam < dewangg...@xtremenitro.org> wrote: > Hi, > > I got random error from osa dispatcher like > http://fpaste.org/171000/54936114/raw/, that error appears when I > restart osad client. > > I restart the osad because of stuck scheduled process. I have 4 > scheduled process, 3 done, 1 pending. I tried to restart osad client, > and that error appears. > > I tried to look the osad status on spacewalk server, osad status said > it's online and can be pinged. > > Till now, scheduled process not complete and timeout. > > Any hints to solve the issue? > > Spacewalk Server : > Spacewalk v2.2 > CentOS 6.6 > > Client : > CentOS 6.6 > > _______________________________________________ > 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
