Hello, Can someone please help me out in this ? Been waiting for a reply -
Thanks On Tue, Dec 12, 2017 at 9:14 PM, Vipul Sharma (DevOps) < [email protected]> wrote: > After further deep-dive, I found the real culprit - It's OSA-DISPATCHER, > It's getting killed @ > > *2017/12/12 13:55:31 -00:00 30167 0.0.0.0 <http://0.0.0.0>: > rhnSQL/driver_postgresql._execute_wrapper('Executing SQL: "select * from > rhnPushClient where jabber_id = %(p1)s" with bind params: {p1: > osad-bfc5e370da@spacewalk.*/osad}',* > > > > > > *https://www.redhat.com/archives/spacewalk-list/2016-August/msg00091.html > <https://www.redhat.com/archives/spacewalk-list/2016-August/msg00091.html>* > > Came across some articles which i'm not sure are the real answers - *Any > support notes someone can point me to other than above 1 -* > > Thanks > > On Tue, Dec 12, 2017 at 5:24 PM, Vipul Sharma (DevOps) < > [email protected]> wrote: > >> Hi Team, >> >> I'm facing a strange issues with OSAD client & this has been a real pain >> for me from past 1 month. >> >> 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. >> >> *************************************************** >> >> *JABBERD LOGS :-* >> >> Dec 12 11:25:26 spacewalk jabberd/c2s[23435]: [28] requesting session: >> jid=osad-750697814a@spacewalk/osad >> Dec 12 11:25:26 spacewalk jabberd/sm[23432]: session started: >> jid=osad-750697814a@spacewalk/osad >> Dec 12 11:25:27 spacewalk jabberd/c2s[23435]: [29] [::ffff:-.-.-.-.-, >> port=56668] connect >> Dec 12 11:25:27 spacewalk jabberd/c2s[23435]: [29] created user: >> user=osad-6b7a6b838f; realm= >> Dec 12 11:25:27 spacewalk jabberd/c2s[23435]: [29] registration >> succeeded, requesting user creation: jid=osad-6b7a6b838f@spacewalk >> Dec 12 11:25:27 spacewalk jabberd/sm[23432]: created user: >> jid=osad-6b7a6b838f@spacewalk >> Dec 12 11:25:27 spacewalk jabberd/c2s[23435]: [29] traditional.digest >> authentication succeeded: osad-6b7a6b838f@/osad ::ffff:-.-.-.-. TLS >> Dec 12 11:25:27 spacewalk jabberd/c2s[23435]: [29] requesting session: >> jid=osad-6b7a6b838f@spacewalk/osad >> Dec 12 11:25:27 spacewalk jabberd/sm[23432]: session started: >> jid=osad-6b7a6b838f@spacewalk/osad >> >> *Client was able to connect & authenticate with JABBERD* >> >> *Now, let's take a look at OSAD LOGS -* >> >> [root@****~]# systemctl start osad >> [root@****~]# tailf /var/log/osad >> 2017-12-12 11:31:03 jabber_lib._presence_callback: >> osad-a071c93d5d@spacewalk/osad rhn-dispatcher-sat@spacewalk/superclient >> None >> 2017-12-12 11:31:03 jabber_lib._presence_callback: Node is available >> rhn-dispatcher-sat@spacewalk/superclient None >> 2017-12-12 11:31:03 jabber_lib.subscribe_to_presence: Subscribed to >> {'rhn-dispatcher-sat@spacewalk': {'jid': 'rhn-dispatcher-sat@spacewalk', >> 'subscription': u'to'}} >> 2017-12-12 11:31:03 jabber_lib.subscribe_to_presence: Subscribed both {} >> 2017-12-12 11:31:03 jabber_lib.subscribe_to_presence: Subscribed none >> {'rhn-dispatcher-sat@spacewalk': {'ask': u'subscribe', 'jid': >> 'rhn-dispatcher-sat@spacewalk', 'subscription': u'none'}} >> 2017-12-12 11:31:03 jabber_lib.subscribe_to_presence: Subscribed from {} >> 2017-12-12 11:31:03 jabber_lib.subscribe_to_presence: Subscribed to >> 2017-12-12 11:31:12 osad_client.unstick_contacts: Re-sending presence >> subscription request <presence to='rhn-dispatcher-sat@spacewalk' >> type='subscribe' id='presence-5268cc-27' /> >> 2017-12-12 11:31:12 jabber_lib.process: 180 >> 2017-12-12 11:31:12 jabber_lib._roster_callback: Updating the roster <iq >> to='osad-a071c93d5d@spacewalk/osad' type='set' >> id='uua0u5otca7uewvq9pfr4hjuze0mravm55mzbbtn'><query xmlns = >> 'jabber:iq:roster' ><item ask='subscribe' jid='rhn-dispatcher-sat@spacewalk' >> subscription='none' /></query></iq> >> >> *It was able to get connected -* >> >> *Now, Let's check OSA-DISPATCHER LOGS - After OSA-DISPATCHER restart -* >> >> 2017/12/12 11:23:57 -00:00 23458 0.0.0.0: osad/jabber_lib.__init__ >> 2017/12/12 11:23:57 -00:00 23458 0.0.0.0: >> osad/jabber_lib.setup_connection('Connected >> to jabber server', 'spacewalk.javelin.g4s.com') >> 2017/12/12 11:23:57 -00:00 23458 0.0.0.0: >> osad/osa_dispatcher.fix_connection('Upstream >> notification server started on port', 1290) >> 2017/12/12 11:23:57 -00:00 23458 0.0.0.0: osad/jabber_lib.process_forever >> >> ******************************************* >> >> Network Connectivity - >> >> *From Client -* >> >> [root@**** ~]# netstat -an | grep 5222 >> >> >> *tcp 5036 0 *.*.*.*:44092 *.*.*.*:5222 ESTABLISHED* >> >> >> *On Spacewalk Server -[root@spacewalk jabberd]# *netstat -an | grep >> *.*.*.*. >> *tcp6 0 0 ***.*.*.*:5222 * >> * *.*.*.*:44092 ESTABLISHED* >> >> >> But, if we look at the GUI for Spacewalk - It's still offline >> >> [image: Inline image 1] >> >> >> >> >> >> >> 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 - >> >> A similar issue is opened on this thread - >> >> https://www.redhat.com/archives/spacewalk-list/2017-July/msg00050.html >> >> >> Thanks >> Vipul Sharma >> DevOps Advocate >> >> >> > -- Please consider the environment before printing this email. ********************************************************************* This communication may contain information which is confidential, personal and/or privileged. It is for the exclusive use of the intended recipient(s). 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. 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. This message has been checked for viruses on behalf of the company. *********************************************************************
_______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
