Based on my usage of osad/behind proxy server I do not need to restart the services daily. After the latest osa-dispatcher resolving a bug with the osa-dispatcher service I have been able to keep osad service up. I have about 20 proxy servers with 6500+ servers connected. The information on the wiki about adjusting timeout intervals are correct except for the idle. If you set the idle to 0 then you will not need to restart the osad services all the time. <div class="gmail_quote">On Tue, Jul 3, 2012 at 8:45 AM, Franky Van Liedekerke <<a href="mailto:liedekef@telenet.be" target="_blank">liedekef@telenet.be</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> On 2012-07-03 16:15, Wojtak, Greg (Superfly) wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Was there ever an update/resolution to getting spacewalk clients to check in properly with osad when they are behind a spacewalk proxy? Last I heard there was a problem with jabber that needed to be addressed and was kind of out of the hands of the spacewalk devs - has this been fixed? </blockquote> Seems to work just fine, taking the following into account: - the spacewalk server needs to be able to reverse lookup the ID mentioned in sm.xml of the proxy jabber - tcp port 5269 needs to be open in both directions (spacewalk server <=> proxy) - once the connection works (see the logs on the spacewalk server), stop the proxy and delete the jabber database there - now connect clients to the proxy, and watch out that they have the correct certificate - on the spacewalk server: stop, remove jabber db & start jabber once every day, see <a href="https://fedorahosted.org/spacewalk/wiki/JabberAndOSAD" target="_blank">https://fedorahosted.org/spacewalk/wiki/JabberAndOSAD</a> - on the clients: restart osad a couple of times a day, see <a href="https://fedorahosted.org/spacewalk/wiki/JabberAndOSAD" target="_blank">https://fedorahosted.org/spacewalk/wiki/JabberAndOSAD</a> We have a snippet that takes care of the client knowing the correct proxy name and certificate, but all the rest is manual :-) Hope this helps. Franky _______________________________________________ Spacewalk-list mailing list <a href="mailto:Spacewalk-list@redhat.com" target="_blank">Spacewalk-list@redhat.com</a> <a href="https://www.redhat.com/mailman/listinfo/spacewalk-list" target="_blank">https://www.redhat.com/mailman/listinfo/spacewalk-list</a> </blockquote></div>