On Tue, Mar 20, 2012 at 08:38:58AM +0100, Pierre Casenove wrote: > Hello list, > > I ran into the following issue: > - due to scheduled downtime on spacewalk server, jabberd process was > not running. > - On the clients logs, here is what I see: > # cat /var/log/osad > 2012-03-16 15:04:09 jabber_lib.main: Unable to connect to jabber > servers, sleeping 119 seconds > 2012-03-16 15:06:08 jabber_lib.main: Unable to connect to jabber > servers, sleeping 70 seconds > 2012-03-16 15:07:18 jabber_lib.main: Unable to connect to jabber > servers, sleeping 106 seconds > 2012-03-16 15:09:04 jabber_lib.main: Unable to connect to jabber > servers, sleeping 113 seconds > > An after that, no more logs on the client. OSAD process is running, > but the client is shown as offline in spacewalk. I restart osad, and > it works well. > I didn't change anything in osad.conf file > My guess is the osad, after 4 conenctions retries, gave up connecting. > > Is it a normal behavior? Or should I put more verbose logging on the > clients to see what happens exactly?
Yes, we would like to see more verbose log output. Thank you, -- Jan Pazdziora Principal Software Engineer, Satellite Engineering, Red Hat _______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
