Yeah, I don't think it's normal. I should be seeing a date/time. And I noticed that when this happens the jobs sometimes don't get picked up. Which of course should not happen.
But with that I do have good news. I figured out the problem. And it came from a posting back in 2011 that gave me the idea. It appears that my issue was with DNS. Since we use a split DNS, I failed to configure the search order to include the other domain. So while the server I was having issues with worked just fine when connected directly to spacewalk, there was the issue when connected thru the proxy. Once I configured DNS properly on the proxy, the issue went away and for the last hour I have been able to successfully send an OSA ping and get a date/time back. So with that said...Is you have an issue where OSA ping fails and you see "online but unknown" and using a proxy, make sure you have DNS properly setup on the proxy. Thanks Glen Collins ----- Original Message ----- Yea that's normal. It means that its picked up jobs through OSAD but has not been pinged since the last time its been declared offline. This is the nature of OSAD its design is that it doesn't chat (IRC) with a host unless there is something it needs the host to do. Hat said it maybe worth while to write an RFE (Request For Enhancement ) ticket for it. Either a nightly ping or at the very least if the time is unknown and it successfully completes a job then have it set the online since time. -- Sent from my HP Pre3 On Nov 18, 2014 2:18 PM, Glen Collins <[email protected]> wrote: Hello all. I'm wondering if there is a way to force an OSA ping from the command line. Ever since I put a proxy in, the system status is not displayed. Says, online but unknown. I checked all the usual things in osa-dispatcher logs, jabber, osad and such and there are no errors that I can see. I'm not sure yet if they will check in on a regular basis but I'm comfortable with sending a ping every once and a while to get around any issues. I noticed back in 2011 someone sent in a patch which added to the api to include a sendOsaPing and getOsaPing, but it looks like it was never adopted. It was located under the system api. A forced ping from the GUI get the status but I want something that can be done without user intervention. Any ideas? I've run out of them. Thanks Glen Collins _______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
_______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
