Heh... always a viable workaround. From: [email protected] [mailto:[email protected]] On Behalf Of Jeffrey Watts Sent: Wednesday, February 03, 2010 1:23 PM To: [email protected] Subject: Re: [Spacewalk-list] rhn_check
osad's been known to be a bit fragile. From what I've read there are more than a few folks that set up a cronjob to restart it regularly. Jeffrey. On Wed, Feb 3, 2010 at 3:17 PM, Kennedy, Ryan <[email protected]<mailto:[email protected]>> wrote: Interesting... after changing the IP address and restarting the network init.d script to make the changes take effect, it appears that osad stopped getting jabber messages. I suspected this due to the fact that I had to run rhn_check on the client to get the requested hardware list refresh to happen. I then initiated a reboot from Spacewalk that wasn't happening either. After about 5 minutes I decided to check osad out. It was running so I went ahead and restarted it. Within 2 seconds of restarting I got a message about the system going down for a reboot. I guess maybe osad should have a hard dependency on networking and restart when it restarts. DISCLAIMER: Information contained in this message may be privileged and confidential. If the reader of this message is not the intended recipient, be notified that any dissemination, distribution or copying of this communication is strictly prohibited. If this communication is received in error, please notify the sender immediately by replying to the message and deleting from your computer. Thank you
_______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
