[Spacewalk-list] [External Sender] Re: Problems with OSAD not picking up remote commands

Mon Sep 30 22:24:16 UTC 2019

Thank you Robert.  I’m not familiar with the jabber cert nor how to
remediate.  Can you provide further guidance on this?

*Larry E. Clegg*

Systems Engineer (SaaS Platform Operations) | *Kyriba*

[Cell Phone] +1 858-357-5579

[Address] 9620 Towne Centre Drive | Suite 250 | San Diego, California |
92121

www.kyriba.com | Facebook <https://www.facebook.com/KyribaCorp> | Twitter
<https://twitter.com/kyribacorp> | LinkedIn
<http://www.linkedin.com/company/kyriba-corporation> | Blog
<http://www.kyriba.com/blog>

*From:* spacewalk-list-bounces at redhat.com [mailto:
spacewalk-list-bounces at redhat.com] *On Behalf Of *Robert Paschedag
*Sent:* Monday, September 30, 2019 2:08 PM
*To:* spacewalk-list at redhat.com
*Subject:* [External Sender] Re: [Spacewalk-list] Problems with OSAD not
picking up remote commands

Looks like simply you're jabber certificate is broken.

Robert

⁣sent from my mobile device

-------- Originale Nachricht --------
Von: Larry Clegg <lclegg at kyriba.com>
Gesendet: Mon Sep 30 22:33:08 GMT+02:00 2019
An: spacewalk-list at redhat.com
Betreff: Re: [Spacewalk-list] Problems with OSAD not picking up remote
commands

More research on this issue….I’m finding that on all of my SW 2.9 nodes
running on Centos7 are failing with Jabberd.

● jabberd.service - Jabber Server

Loaded: loaded (/usr/lib/systemd/system/jabberd.service; enabled; vendor
preset: disabled)

Active: active (exited) since Thu 2019-09-12 20:16:19 UTC; 2 weeks 4
days ago

Process: 19180 ExecStart=/bin/true (code=exited, status=0/SUCCESS)

Main PID: 19180 (code=exited, status=0/SUCCESS)

CGroup: /system.slice/jabberd.service

Checking the /var/log/rhn/osa-dispatcher.log I see this:

2019/09/30 20:32:22 -00:00 14849 0.0.0.0
<http://0.0.0.0>
osad/jabber_lib.main('ERROR',
'Error caught:')

2019/09/30 20:32:22 -00:00 14849 0.0.0.0
<http://0.0.0.0>
osad/jabber_lib.main('ERROR',
'Traceback (most recent call last):¥n File
"/usr/lib/python2.7/site-packages/osad/jabber_lib.py", line 126, in
main¥n self.process_forever(c)¥n File
"/usr/lib/python2.7/site-packages/osad/jabber_lib.py", line 187, in
process_forever¥n self.process_once(client)¥n File
"/usr/lib/python2.7/site-packages/osad/osa_dispatcher.py", line 182, in
process_once¥n client.retrieve_roster()¥n File
"/usr/lib/python2.7/site-packages/osad/jabber_lib.py", line 757, in
retrieve_roster¥n stanza = self.get_one_stanza()¥n File
"/usr/lib/python2.7/site-packages/osad/jabber_lib.py", line 829, in
get_one_stanza¥n self.process(timeout=tm)¥n File
"/usr/lib/python2.7/site-packages/osad/jabber_lib.py", line 1100, in
process¥n raise_with_tb(SSLError("OpenSSL error; will retry", str(e)),
sys.exc_info()[2])¥n File
"/usr/lib/python2.7/site-packages/osad/jabber_lib.py", line 1095, in
process¥n data = self._read(self.BLOCK_SIZE)¥nSSLError: (¥'OpenSSL
error; will retry¥', "(-1, ¥'Unexpected EOF¥')")¥n')

*Larry E. Clegg*

Systems Engineer (SaaS Platform Operations) | *Kyriba*

[Cell Phone] +1 858-357-5579

[Address] 9620 Towne Centre Drive | Suite 250 | San Diego, California |
92121

www.kyriba.com
<http://www.kyriba.com>
| Facebook <https://www.facebook.com/KyribaCorp
<https://www.facebook.com/KyribaCorp>>
| Twitter
<https://twitter.com/kyribacorp
<https://twitter.com/kyribacorp>>
| LinkedIn
<http://www.linkedin.com/company/kyriba-corporation
<http://www.linkedin.com/company/kyriba-corporation>>
| Blog
<http://www.kyriba.com/blog
<http://www.kyriba.com/blog>
>

*From:* Larry Clegg [mailto:lclegg at kyriba.com <lclegg at kyriba.com>]
*Sent:* Monday, September 30, 2019 11:42 AM
*To:* 'spacewalk-list at redhat.com' <spacewalk-list at redhat.com>
*Subject:* Problems with OSAD not picking up remote commands

Greetings Spacers,

My environment:

SW Server: Centos 7 fully patched and Spacewalk 2.9

SW Client: Centos 6 fully patched and Spacewalk Client 2.9 including OSAD
osad-5.11.107-1.el6.noarch

Issue: From the SW server I select several systems and issue a remote
command. Normally OSAD will pick up the remote command within seconds.
Now it is not picking it up for many minutes….even after a normal system
check-in the remote command is still not picked up. I can login to the
client system and issue a rhn_check –vvvv and see it pick up the remote
command and return the output. Service osad is running; restarting makes
no difference.

On the SW server:

jabberpy-0.5-0.27.el7.noarch

spacewalk-setup-jabberd-2.9.2-1.el7.noarch

jabberd-2.6.1-1.el7.x86_64

osa-dispatcher-selinux-5.11.107-1.el7.noarch

python2-osa-common-5.11.107-1.el7.noarch

osa-dispatcher-5.11.107-1.el7.noarch

python2-osa-dispatcher-5.11.107-1.el7.noarch

Port 5222 is open with established connections. I find no errors in any
logs.

I’m at a loss as to where to look now….any guidance would be appreciated.

Regards,

*Larry E. Clegg*

Systems Engineer (SaaS Platform Operations) | *Kyriba*

[Cell Phone] +1 858-357-5579

[Address] 9620 Towne Centre Drive | Suite 250 | San Diego, California |
92121

www.kyriba.com
<http://www.kyriba.com>
| Facebook <https://www.facebook.com/KyribaCorp
<https://www.facebook.com/KyribaCorp>>
| Twitter
<https://twitter.com/kyribacorp
<https://twitter.com/kyribacorp>>
| LinkedIn
<http://www.linkedin.com/company/kyriba-corporation
<http://www.linkedin.com/company/kyriba-corporation>>
| Blog
<http://www.kyriba.com/blog
<http://www.kyriba.com/blog>
>

------------------------------------------------------------------------

_______________________________________________
Spacewalk-list mailing list
Spacewalk-list at redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list
<https://www.redhat.com/mailman/listinfo/spacewalk-list>

_______________________________________________
Spacewalk-list mailing list
Spacewalk-list at redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list
<https://www.redhat.com/mailman/listinfo/spacewalk-list>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20190930/c6967b91/attachment.htm>