Very Strange. They Client came online automatically. Persisted after reboot as well.
OSA Status: online as of 3/3/15 5:01:26 AM EST Last pinged: 3/3/15 5:07:37 AM EST Ping System<https://md1prdlnxmgr01.jda.corp.local/rhn/systems/details/Overview.do?sid=1000010002&ping=1> From spacewalk server: 2015/03/02 11:48:39 -04:00 79937 0.0.0.0: osad/jabber_lib.__init__ 2015/03/02 11:48:39 -04:00 79937 0.0.0.0: osad/jabber_lib.setup_connection('Connected to jabber server', 'md1prdlnxmgr01.jda.corp.local') 2015/03/02 11:48:39 -04:00 79937 0.0.0.0: osad/osa_dispatcher.fix_connection('Upstream notification server started on port', 1290) 2015/03/02 11:48:39 -04:00 79937 0.0.0.0: osad/jabber_lib.process_forever 2015/03/02 11:48:57 -04:00 80559 0.0.0.0: osad/jabber_lib.__init__ 2015/03/02 11:48:57 -04:00 80559 0.0.0.0: osad/jabber_lib.setup_connection('Connected to jabber server', 'md1prdlnxmgr01.jda.corp.local') 2015/03/02 11:48:57 -04:00 80559 0.0.0.0: osad/osa_dispatcher.fix_connection('Upstream notification server started on port', 1290) 2015/03/02 11:48:57 -04:00 80559 0.0.0.0: osad/jabber_lib.process_forever 2015/03/02 11:50:29 -04:00 80559 0.0.0.0: osad/dispatcher_client._message_callback('Ping response',) 2015/03/03 04:59:39 -04:00 80559 0.0.0.0: osad/dispatcher_client._message_callback('Ping response',) I can see there is response from client. Looked like client took some time to respond . From: [email protected] [mailto:[email protected]] On Behalf Of Deepjoy Choudhury Sent: Monday, March 02, 2015 9:01 PM To: [email protected] Subject: Re: [Spacewalk-list] Subject: Client shows offline in Spacewalk GUI Hi Matthew, Thanks for your mail. Followed the mentioned steps. Although client shows connected, [root@linuxvm01 yum.repos.d]# osad -v 2015-03-02 10:19:00 jabber_lib.__init__: 2015-03-02 10:19:01 jabber_lib.setup_connection: Connected to jabber server md1prdlnxmgr01.jda.corp.local The verbose reveals below error. (last few lines) [root@linuxvm01 ~]# /usr/sbin/osad -N -v -v -v -v md1prdlnxmgr01.jda.corp.local' subscription='both' /></query></iq> 2015-03-02 10:24:23 jabber_lib.register_callback: <bound method Client._presence_callback of <osad.osad_client.Client instance at 0x1346ef0>> presence None None None None 2015-03-02 10:24:23 jabber_lib.register_callback: <bound method Client._message_callback of <osad.osad_client.Client instance at 0x1346ef0>> message None None None None 2015-03-02 10:24:24 jabber_lib.subscribe_to_presence: Subscribed to {} 2015-03-02 10:24:24 jabber_lib.subscribe_to_presence: Subscribed both {'[email protected]': {'jid': '[email protected]', 'subscription': u'both'}} 2015-03-02 10:24:24 jabber_lib.subscribe_to_presence: Subscribed none {} 2015-03-02 10:24:24 jabber_lib.subscribe_to_presence: Subscribed from {} 2015-03-02 10:24:24 jabber_lib.subscribe_to_presence: Already subscribed to the presence of node [email protected]<mailto:[email protected]> 2015-03-02 10:24:24 jabber_lib.send_presence: None None 2015-03-02 10:24:24 jabber_lib.process_forever: 2015-03-02 10:24:24 jabber_lib.process: 180 2015-03-02 10:24:25 jabber_lib._presence_callback: [email protected]/osad<mailto:[email protected]/osad> [email protected]/superclient<mailto:[email protected]/superclient> None 2015-03-02 10:24:25 jabber_lib._presence_callback: Node is available [email protected]/superclient<mailto:[email protected]/superclient> None 2015-03-02 10:24:25 jabber_lib.subscribe_to_presence: Subscribed to {} 2015-03-02 10:24:25 jabber_lib.subscribe_to_presence: Subscribed both {'[email protected]': {'jid': '[email protected]', 'subscription': u'both'}} 2015-03-02 10:24:25 jabber_lib.subscribe_to_presence: Subscribed none {} 2015-03-02 10:24:25 jabber_lib.subscribe_to_presence: Subscribed from {} 2015-03-02 10:24:25 jabber_lib.subscribe_to_presence: Already subscribed to the presence of node [email protected]<mailto:[email protected]> 2015-03-02 10:24:35 jabber_lib.process: 180 2015-03-02 10:26:03 jabber_lib.process: 180 Error caught: Traceback (most recent call last): File "/usr/share/rhn/osad/jabber_lib.py", line 121, in main self.process_forever(c) File "/usr/share/rhn/osad/jabber_lib.py", line 179, in process_forever self.process_once(client) File "/usr/share/rhn/osad/osad.py", line 250, in process_once client.process(timeout=180) File "/usr/share/rhn/osad/jabber_lib.py", line 1055, in process data = self._read(self.BLOCK_SIZE) SSLError: ('OpenSSL error; will retry', "(-1, 'Unexpected EOF')") 2015-03-02 10:26:03 jabber_lib.main: Sleeping 111 seconds From the Spacewalk server: root@md1prdlnxmgr01 ~]# tail -f /var/log/rhn/osa-dispatcher.log 2015/02/27 09:29:50 -04:00 13660 0.0.0.0: osad/jabber_lib.__init__ 2015/02/27 09:29:51 -04:00 13660 0.0.0.0: osad/jabber_lib.setup_connection('Connected to jabber server', 'md1prdlnxmgr01.jda.corp.local') 2015/02/27 09:29:51 -04:00 13660 0.0.0.0: osad/osa_dispatcher.fix_connection('Upstream notification server started on port', 1290) 2015/02/27 09:29:51 -04:00 13660 0.0.0.0: osad/jabber_lib.process_forever 2015/02/27 09:38:10 -04:00 4529 0.0.0.0: osad/jabber_lib.__init__ 2015/02/27 09:38:10 -04:00 4529 0.0.0.0: osad/jabber_lib.setup_connection('Connected to jabber server', 'md1prdlnxmgr01.jda.corp.local') 2015/02/27 09:38:10 -04:00 4529 0.0.0.0: osad/osa_dispatcher.fix_connection('Upstream notification server started on port', 1290) 2015/02/27 09:38:10 -04:00 4529 0.0.0.0: osad/jabber_lib.process_forever But there is a change in OSA status: OSA status: online as of unknown Earlier this was : Offline as of unknown From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Matthew Madey Sent: Monday, March 02, 2015 8:37 PM To: [email protected]<mailto:[email protected]> Subject: Re: [Spacewalk-list] Subject: Client shows offline in Spacewalk GUI Check the osa-dispatcher log on the Spacewalk server for more information: /var/log/rhn/osa-dispatcher.log Also, try this on the client: service osad stop ; rm -f /etc/sysconfig/rhn/osad-auth.conf ; service osad start On Mon, Mar 2, 2015 at 7:01 AM, Deepjoy Choudhury <[email protected]<mailto:[email protected]>> wrote: Any Suggestions Friends … Thanks & Regards From: Deepjoy Choudhury Sent: Saturday, February 28, 2015 5:25 PM To: [email protected]<mailto:[email protected]> Subject: Subject: Client shows offline in Spacewalk GUI Hi Team, I have installed spacewalk 2.2 and registered clients to it. After installing osad, the client shows offline/unknown in spacewalk. Firewall/selinux are disabled on both client and server. osad –v: Client: 2015-02-27 10:00:31 jabber_lib.__init__: 2015-02-27 10:00:31 jabber_lib.setup_connection: Connected to jabber server mxxx.xxx.corp.local Server: [root@mxxx ~]# service osa-dispatcher status osa-dispatcher (pid 4535) is running... [root@ mxxx ~]# service jabberd status router (pid 4373) is running... sm (pid 4380) is running... c2s (pid 4387) is running... s2s (pid 4394) is running... Can you please help _______________________________________________ Spacewalk-list mailing list [email protected]<mailto:[email protected]> https://www.redhat.com/mailman/listinfo/spacewalk-list
_______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
