Hi, You will have to dig through jabberd logs and/or strace process to pinpoint the issue. Basically, the communication should look this way :
Client ==TCP/5222==> Proxy (Jabberd/c2s) =(socket?)=> Proxy (jabberd/s2s) ==TCP/5269=> Central Spacewalk (jabberd/s2s) => osad Did you open both 5222 for client to proxy and 5269 for proxy to spacewalk communications in your firewalls ? Regards, Maxime Veroone -----Message d'origine----- De : spacewalk-list-boun...@redhat.com [mailto:spacewalk-list-boun...@redhat.com] De la part de Wojtak, Greg Envoyé : mercredi 9 décembre 2015 16:28 À : spacewalk-list@redhat.com Objet : [Spacewalk-list] osad behind a proxy Ive been going through and giving some love to my spacewalk infrastructure and realized that scheduling actions on systems behind proxy are not getting picked up by osad. Actions scheduled to run on the proxy itself run fine, but it seems like maybe jabberd is not 100% configured correctly on my proxy or something so that messages are not being passed back and forth from the clients behind the proxy to the spacewalk server? Any idea on how to troubleshoot? Im not terribly familiar with the architecture of xmpp in this manner, so Im kind of at a loss. Im also assuming its something with jabber and not something else, so theres that too. TIA, Greg _______________________________________________ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list _______________________________________________ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
