<div dir="ltr"><div><div>After further deep-dive, I found the real culprit - It's OSA-DISPATCHER, It's getting killed @ <br><br><b>2017/12/12 13:55:31 -00:00 30167 <a href="http://0.0.0.0">0.0.0.0</a>: rhnSQL/driver_postgresql._execute_wrapper('Executing SQL: "select * from rhnPushClient where jabber_id = %(p1)s" with bind params: {p1: osad-bfc5e370da@spacewalk.*/osad}',</b></div><div><b><br></b></div><div><b><br></b></div><div><b><br></b></div><div><b><br></b></div><div><b><a href="https://www.redhat.com/archives/spacewalk-list/2016-August/msg00091.html">https://www.redhat.com/archives/spacewalk-list/2016-August/msg00091.html</a><br></b></div><div><b><br></b></div>Came across some articles which i'm not sure are the real answers - <b>Any support notes someone can point me to other than above 1 -</b><br><br></div>Thanks<br><div><div><b></b></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Dec 12, 2017 at 5:24 PM, Vipul Sharma (DevOps) <span dir="ltr"><<a href="mailto:sharma.vipul@in.g4s.com" target="_blank">sharma.vipul@in.g4s.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div><div><div><div><div><div><div><div>Hi Team,<br><br></div>I'm facing a strange issues with OSAD client & this has been a real pain for me from past 1 month.<br><br></div>Apparently - After successfully performing everything and creating customs scripts for Spacewalk - I'm unable to figure out issues when - OSAD is connected with OSA-DISPATCHER through JABBERD.<br><br>******************************<wbr>*********************<br><b><br></b></div><b>JABBERD LOGS :-</b><br><br>Dec 12 11:25:26 spacewalk jabberd/c2s[23435]: [28] requesting session: jid=osad-750697814a@spacewalk/<wbr>osad<br>Dec 12 11:25:26 spacewalk jabberd/sm[23432]: session started: jid=osad-750697814a@spacewalk/<wbr>osad<br>Dec 12 11:25:27 spacewalk jabberd/c2s[23435]: [29] [::ffff:-.-.-.-.-, port=56668] connect<br>Dec 12 11:25:27 spacewalk jabberd/c2s[23435]: [29] created user: user=osad-6b7a6b838f; realm=<br>Dec 12 11:25:27 spacewalk jabberd/c2s[23435]: [29] registration succeeded, requesting user creation: jid=osad-6b7a6b838f@spacewalk<br>Dec 12 11:25:27 spacewalk jabberd/sm[23432]: created user: jid=osad-6b7a6b838f@spacewalk<br>Dec 12 11:25:27 spacewalk jabberd/c2s[23435]: [29] traditional.digest authentication succeeded: osad-6b7a6b838f@/osad ::ffff:-.-.-.-. TLS<br>Dec 12 11:25:27 spacewalk jabberd/c2s[23435]: [29] requesting session: jid=osad-6b7a6b838f@spacewalk/<wbr>osad<br>Dec 12 11:25:27 spacewalk jabberd/sm[23432]: session started: jid=osad-6b7a6b838f@spacewalk/<wbr>osad<br><b><br></b></div><b>Client was able to connect & authenticate with JABBERD</b><br><br></div><b>Now, let's take a look at OSAD LOGS -</b><br><br>[root@****~]# systemctl start osad<br>[root@****~]# tailf /var/log/osad<br>2017-12-12 11:31:03 jabber_lib._presence_callback: osad-a071c93d5d@spacewalk/osad rhn-dispatcher-sat@spacewalk/<wbr>superclient None<br>2017-12-12 11:31:03 jabber_lib._presence_callback: Node is available rhn-dispatcher-sat@spacewalk/<wbr>superclient None<br>2017-12-12 11:31:03 jabber_lib.subscribe_to_<wbr>presence: Subscribed to {'rhn-dispatcher-sat@spacewalk<wbr>': {'jid': 'rhn-dispatcher-sat@spacewalk'<wbr>, 'subscription': u'to'}}<br>2017-12-12 11:31:03 jabber_lib.subscribe_to_<wbr>presence: Subscribed both {}<br>2017-12-12 11:31:03 jabber_lib.subscribe_to_<wbr>presence: Subscribed none {'rhn-dispatcher-sat@spacewalk<wbr>': {'ask': u'subscribe', 'jid': 'rhn-dispatcher-sat@spacewalk'<wbr>, 'subscription': u'none'}}<br>2017-12-12 11:31:03 jabber_lib.subscribe_to_<wbr>presence: Subscribed from {}<br>2017-12-12 11:31:03 jabber_lib.subscribe_to_<wbr>presence: Subscribed to<br>2017-12-12 11:31:12 osad_client.unstick_contacts: Re-sending presence subscription request <presence to='rhn-dispatcher-sat@<wbr>spacewalk' type='subscribe' id='presence-5268cc-27' /><br>2017-12-12 11:31:12 jabber_lib.process: 180<br>2017-12-12 11:31:12 jabber_lib._roster_callback: Updating the roster <iq to='osad-a071c93d5d@spacewalk/<wbr>osad' type='set' id='<wbr>uua0u5otca7uewvq9pfr4hjuze0mra<wbr>vm55mzbbtn'><query xmlns = 'jabber:iq:roster' ><item ask='subscribe' jid='rhn-dispatcher-sat@<wbr>spacewalk' subscription='none' /></query></iq><br><br></div><b>It was able to get connected -</b><br><b><br></b></div><b>Now, Let's check OSA-DISPATCHER LOGS - After OSA-DISPATCHER restart -</b><br><br>2017/12/12 11:23:57 -00:00 23458 <a href="http://0.0.0.0" target="_blank">0.0.0.0</a>: osad/jabber_lib.__init__<br>2017/12/12 11:23:57 -00:00 23458 <a href="http://0.0.0.0" target="_blank">0.0.0.0</a>: osad/jabber_lib.setup_<wbr>connection('Connected to jabber server', '<a href="http://spacewalk.javelin.g4s.com" target="_blank">spacewalk.javelin.g4s.com</a>')<br>2017/12/12 11:23:57 -00:00 23458 <a href="http://0.0.0.0" target="_blank">0.0.0.0</a>: osad/osa_dispatcher.fix_<wbr>connection('Upstream notification server started on port', 1290)<br>2017/12/12 11:23:57 -00:00 23458 <a href="http://0.0.0.0" target="_blank">0.0.0.0</a>: osad/jabber_lib.process_<wbr>forever<br><br>******************************<wbr>*************<br><br></div>Network Connectivity -<br><br></div><b>From Client -</b><br><br>[root@**** ~]# netstat -an | grep 5222<br><b>tcp 5036 0 *.*.*.*:44092 *.*.*.*:5222 ESTABLISHED<br><br></b></div><b>On Spacewalk Server -<br><br>[root@spacewalk jabberd]# </b>netstat -an | grep *.*.*.*.<b><br>tcp6 0 0 </b><b><b>*.*.*.*</b>:5222 </b><b><b> *.*.*.*</b>:44092 ESTABLISHED<br></b></div><div><b><br></b></div><div><br></div><div>But, if we look at the GUI for Spacewalk - It's still offline<br></div><div><br></div><div><img src="cid:ii_1604a90905ef636f" alt="Inline image 1" width="471" height="211"><br></div><div><b></b></div><div><div><b></b><div><div><br><br><div><div><br><br><div><div><br></div><div><br></div><div>I need big time help from all the community to resolve this - I have followed most of the steps listed on the Spacewalk channel, Still unable to find the root cause -</div><div><br></div><div>A similar issue is opened on this thread -</div><div><br></div><div><a href="https://www.redhat.com/archives/spacewalk-list/2017-July/msg00050.html" target="_blank">https://www.redhat.com/<wbr>archives/spacewalk-list/2017-<wbr>July/msg00050.html</a></div><div><br></div><div><br></div><div>Thanks</div><div>Vipul Sharma</div><div>DevOps Advocate<br></div><div><br></div><div><br></div></div></div></div></div></div></div></div></div> </blockquote></div><br></div> <br> <div><font size="1"><font face="Verdana" color="green" style="line-height:21px;background-color:rgb(255,255,255)"><br></font></font></div><font size="1"><font face="Verdana" color="green" style="line-height:21px;background-color:rgb(255,255,255)">Please consider the environment before printing this email.</font><font face="Verdana" color="gray" style="line-height:21px;background-color:rgb(255,255,255)"><br>******************************<wbr>******************************<wbr>*********<br>This communication may contain information which is confidential, personal and/or privileged. It is for the exclusive use of the intended recipient(s).<br>If you are not the intended recipient(s), please note that any distribution, forwarding, copying or use of this communication or the information in it is strictly prohibited. If you have received it in error please contact the sender immediately by return e-mail. Please then delete the e-mail and any copies of it and do not use or disclose its contents to any person.<br>Any personal views expressed in this e-mail are those of the individual sender and the company does not endorse or accept responsibility for them. Prior to taking any action based upon this e-mail message, you should seek appropriate confirmation of its authenticity.<br>This message has been checked for viruses on behalf of the company.<br>******************************<wbr>******************************<wbr>*********</font><font face="Verdana" color="gray" style="line-height:21px;background-color:rgb(255,255,255)"><br><br></font></font>