Hello Greg, <div><br></div><div>In my situation I have a proxy server that is in a location that is not connected to our main DNS servers (in a separated network/environment). I had to update the DNS in that location to reflect the A record I have configured for my application server that is in a different network. Once I updated this information osad started working. I did have to restart the services on the proxy and client (remove the osad-auth.conf when you restart osad) to get it working. Adding a host entry to the proxy server for the application server didn't work it had to be an A record (seems to be SSL verification that was the cause). When I added this configuration the jabber logs showed the following which was different to what it was seeing during when it wasn't working.</div> <div><br></div><div><div>Sep 29 10:59:23 p1plswpxyars01 jabberd/s2s[11641]: <hostname application server removed for security> lookup for <hostname application server removed for security> returned 1 result (ttl 86400)</div> <div>Sep 29 10:59:23 p1plswpxyars01 jabberd/s2s[11641]: [8] [<IP of app server removed for security>, port=5269] outgoing connection for '<hostname application server removed for security>'</div><div>Sep 29 10:59:23 p1plswpxyars01 jabberd/s2s[11641]: [8] [<IP of app server removed for security>, port=5269] sending dialback auth request for route '<hostname proxy server removed for security>/<hostname application server removed for security>'</div> <div>Sep 29 10:59:23 p1plswpxyars01 jabberd/s2s[11641]: [9] [<IP of app server removed for security>, port=42619] incoming connection</div><div>Sep 29 10:59:23 p1plswpxyars01 jabberd/s2s[11641]: [9] [<IP of app server removed for security>, port=42619] incoming stream online (id )</div> <div>Sep 29 10:59:23 p1plswpxyars01 jabberd/s2s[11641]: [9] [<IP of app server removed for security>, port=42619] received dialback auth request for route '<hostname proxy server removed for security>/<hostname application server removed for security>'</div> <div>Sep 29 10:59:23 p1plswpxyars01 jabberd/s2s[11641]: [9] [<IP of app server removed for security>, port=42619] incoming route '<hostname proxy server removed for security>/<hostname application server removed for security>' is now valid</div> <div>Sep 29 10:59:23 p1plswpxyars01 jabberd/s2s[11641]: [9] [<IP of app server removed for security>, port=42619] checking dialback verification from <hostname application server removed for security>: sending valid</div> <div>Sep 29 10:59:24 p1plswpxyars01 jabberd/s2s[11641]: [8] [<IP of app server removed for security>, port=5269] outgoing route '<hostname proxy server removed for security>/<hostname application server removed for security>' is now valid</div> <div><br></div><br><div class="gmail_quote">2011/9/29 Wojtak, Greg <span dir="ltr"><<a href="mailto:GregWojtak@quickenloans.com">GregWojtak@quickenloans.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> It looks like I am getting a similar problem (now that I know what to look for in the logs):<br> <br> grep dns /var/log/messages<br> Sep 29 15:05:39 spacewalk jabberd/s2s[20819]: dns lookup for spacewalk-proxy failed<br> <br> I modified my resolv.conf's search option to include the domain that spacewalk-proxy is in and am able to resolve the shortname from command line with host or nslookup. I am still getting this error.<br> <br> I noticed in the jabberd documentation that there is a reference to /usr/bin/resolver and /etc/jabberd/resolver.xml. I don't have either of these files, nor does a yum provides /usr/bin/resolver return anything. Is this supposed to be there? I have the following line in my s2s.xml:<br> <br> <resolver>resolver</resolver><br> <br> Should that be changed to something else?<br> <br> Thanks!<br> <br> Greg<br> <div class="im"><br> From: Jeremy Davis <<a href="mailto:jdavis4102@gmail.com">jdavis4102@gmail.com</a><mailto:<a href="mailto:jdavis4102@gmail.com">jdavis4102@gmail.com</a>>><br> Reply-To: <<a href="mailto:spacewalk-list@redhat.com">spacewalk-list@redhat.com</a><mailto:<a href="mailto:spacewalk-list@redhat.com">spacewalk-list@redhat.com</a>>><br> Date: Thu, 29 Sep 2011 12:14:14 -0600<br> To: <<a href="mailto:spacewalk-list@redhat.com">spacewalk-list@redhat.com</a><mailto:<a href="mailto:spacewalk-list@redhat.com">spacewalk-list@redhat.com</a>>><br> Subject: Re: [Spacewalk-list] OSAD Problem with client/proxy<br> <br> </div><div class="im">Hello List/Mirek,<br> <br> Determined the solution to the issue I was having with that proxy server. It turns out it was a DNS issue. Updated DNS and everything is working as it should. Thank you for your help.<br> <br> </div><div class="im">On Fri, Sep 23, 2011 at 9:18 AM, Jeremy Davis <<a href="mailto:jdavis4102@gmail.com">jdavis4102@gmail.com</a><mailto:<a href="mailto:jdavis4102@gmail.com">jdavis4102@gmail.com</a>>> wrote:<br> I am able to get to the ports on the proxy from the client. I performed a tcpdump and the communication seems to be going just fine. No errors in /var/log/messages where the jabber logs are being sent. It appears to be working as it should but in the web ui it doesn't show online and the client will not pick up instant actions. I also performed an rhn_check -vv and no errors were displayed. Everything looks normal by what I can see but still have this issue.<br> <br> <br> </div>2011/9/23 Miroslav Suchı <<a href="mailto:msuchy@redhat.com">msuchy@redhat.com</a><mailto:<a href="mailto:msuchy@redhat.com">msuchy@redhat.com</a>>><br> <div class="im">On 09/22/2011 06:46 PM, Jeremy Davis wrote:<br> > Hello Mirek,<br> ><br> > Thank you for the reply. An rhn_check works fine. I do not see any<br> > issues there. Actions get picked up within an hour as set for the rhnsd<br> > service. It seems the issue is with the osad service. I turned up debug<br> > and restart the osad service and I see no errors. I see that it tries to<br> > register and actually does register as I see the registration on the<br> > proxy server. Now when I look in Spacewalk the osa status shows offline<br> > even after a ping. This is only happening on one proxy server ( I have<br> > about 14 proxy servers). All other proxy servers appear to be working<br> > fine. Any idea as to what could be the problem? I can also provide any<br> > logs that you may want to look at.<br> <br> Osad is not working. Can you telnet to jabberd port from that proxy. Is<br> that anything related in jabberd and osa/osad logs?<br> <br> <br> --<br> Miroslav Suchy<br> Red Hat Satellite Engineering<br> <br> _______________________________________________<br> Spacewalk-list mailing list<br> </div><a href="mailto:Spacewalk-list@redhat.com">Spacewalk-list@redhat.com</a><mailto:<a href="mailto:Spacewalk-list@redhat.com">Spacewalk-list@redhat.com</a>><br> <div class="im"><a href="https://www.redhat.com/mailman/listinfo/spacewalk-list" target="_blank">https://www.redhat.com/mailman/listinfo/spacewalk-list</a><br> <br> <br> <br> --<br> Kind regards,<br> Jeremy Davis, GCIH<br> <br> <br> <br> --<br> Kind regards,<br> Jeremy Davis, GCIH<br> </div>_______________________________________________ Spacewalk-list mailing list <a href="mailto:Spacewalk-list@redhat.com">Spacewalk-list@redhat.com</a><mailto:<a href="mailto:Spacewalk-list@redhat.com">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><br> <div><div></div><div class="h5"><br> _______________________________________________<br> Spacewalk-list mailing list<br> <a href="mailto:Spacewalk-list@redhat.com">Spacewalk-list@redhat.com</a><br> <a href="https://www.redhat.com/mailman/listinfo/spacewalk-list" target="_blank">https://www.redhat.com/mailman/listinfo/spacewalk-list</a><br> </div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Kind regards,<br>Jeremy Davis, GCIH<br> </div>