I turned on some debugging and the clients are communicating just fine with the proxy. It looks like the proxy to spacewalk server is where the breakdown is occurring. I'm seeing the following repeated over and over in the proxy's /var/lib/jabberd/log/s2s.log (ip addresses and host names scrubbed in the interest of security):
Fri Aug 5 14:22:13 2011 [notice] [8] [1.2.3.4, port=5269] outgoing connection for 'spacewalk' Fri Aug 5 14:22:13 2011 [notice] [8] [1.2.3.4, port=5269] sending dialback auth request for route 'proxy/spacewalk' Fri Aug 5 14:23:13 2011 [notice] [8] [1.2.3.4, port=5269] error: Stream error (dialback timed out) Fri Aug 5 14:23:13 2011 [notice] [8] [1.2.3.4, port=5269] disconnect, packets: 0 I'm not real strong on how jabber communicates, but I did verify that I could get to spacewalk from proxy and to proxy from spacewalk on port 5269. In fact, my firewall rules have ports 80, 443, and 5269 open from proxy to spacewalk. I believe 5269 is the only port open from spacewalk to proxy. We are not running local firewalls (ie iptables) on the hosts. They are separated by a network firewall into a management environment and a DMZ. Any ideas based on the above error? From: Jeremy Davis <[email protected]<mailto:[email protected]>> Reply-To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Date: Fri, 5 Aug 2011 11:51:29 -0400 To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: Re: [Spacewalk-list] OSAD - Clients not receiving actions Thank you all for the replies. Unfortunately, I have already added the firewall options to resolve that issue. A little more information I think might be needed. When osad goes down I am still able to ping the system via the web UI and the client returns as online. When I restart the service I get two failed services (c2s and s2s). Seems like DB corruption with the Jabber service. Greg, In order to get the proxy client operation to work with OSA you would need to point the client to the proxy server and provide the client with the SSL cert that is generated when you configure a proxy server. Once you have these two items you will also need some ports opened. 5222 for client to server and 5269 for application server to proxy server. Once you have all of these setup restart the services as outlined below and you should be able to get the services up. If you have problems with this please restart the osad service with debugging turned on to 9 and submit the logs within a new email and I would be more than glad to assist. Thanks, Jeremy On Fri, Aug 5, 2011 at 6:54 AM, Wojtak, Greg <[email protected]<mailto:[email protected]>> wrote: If you're able to get the OSA clients working with proxy at all, you're better off than I am. I (and I think one or two other people on this list) all have the issue where it has never worked; only if the clients communicate directly with the spacewalk server does OSA seem to work for me. I'm going to try the steps you outlined below and see if I can use that as a starting point to get the proxy communications to the server working properly. Greg From: Jeremy Davis <[email protected]<mailto:[email protected]><mailto:[email protected]<mailto:[email protected]>>> Reply-To: "[email protected]<mailto:[email protected]><mailto:[email protected]<mailto:[email protected]>>" <[email protected]<mailto:[email protected]><mailto:[email protected]<mailto:[email protected]>>> Date: Thu, 4 Aug 2011 18:51:34 -0400 To: "[email protected]<mailto:[email protected]><mailto:[email protected]<mailto:[email protected]>>" <[email protected]<mailto:[email protected]><mailto:[email protected]<mailto:[email protected]>>> Subject: Re: [Spacewalk-list] OSAD - Clients not receiving actions List, Anyone have any ideas as to what is causing this issue? Any assistance you could provide would be greatly appreciated. Thanks, Jeremy On Wed, Aug 3, 2011 at 3:10 PM, Jeremy Davis <[email protected]<mailto:[email protected]><mailto:[email protected]<mailto:[email protected]>>> wrote: List, I have a Spacewalk 1.4 installation and have about 2000+ servers connected to proxy servers. At intermittent times I am unable to send remote commands to clients via the osad service. When this happens the only way to get this feature to work again is to perform the following steps on in order. Step 1: On Spacewalk Application server. service jabberd stop service osa-dispatcher stop rm -f /var/lib/jabberd/db/* service jabberd start sleep 5 service osa-dispatcher start Step 2: Wait until Proxy server reconnect to Spacewalk Application server. Step 3: On Spacewalk Proxy servers. service jabberd stop rm -f /var/lib/jabberd/db/* service jabberd start After I perform these steps the client will be able to receive actions until the next time it goes down. Unfortunately, I am unable to find any logs to determine what is going on. Any assistance you could provide in this would be greatly appreciated. Thanks, Jeremy _______________________________________________ Spacewalk-list mailing list [email protected]<mailto:[email protected]> https://www.redhat.com/mailman/listinfo/spacewalk-list -- Thank you, Jeremy Davis, GCIH _______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
