Nicki, Don't despair. You'll get it. And, you learned a few things along the way.
Dimitri -----Original Message----- From: spacewalk-list-boun...@redhat.com [mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Nicki Clear Sent: Friday, May 20, 2016 9:07 AM To: spacewalk-list@redhat.com Cc: spacewalk-list-boun...@redhat.com Subject: Re: [Spacewalk-list] osad not picking up actions Thanks everyone... I tried everything but reregistering the machines... Since it would be about 70 or so machines, I'm preferring that to be a last resort... and it is still not working. I had to regenerate my ssl certificate a few weeks back and I checked the cn is not the fqdn... I'm wondering if that may be it, I can't update it right now, but I will update it and push it to the machines and restart osad and see how it goes. Thanks, Nicki From: Franky Van Liedekerke <liede...@telenet.be> To: spacewalk-list@redhat.com, Date: 05/19/2016 07:12 PM Subject: Re: [Spacewalk-list] osad not picking up actions Sent by: spacewalk-list-boun...@redhat.com On Thu, 19 May 2016 16:01:08 -0400 Nicki Clear <ncl...@oh.hra.com> wrote: <<snip> > eventually it will fail with > > 2016-05-19 15:54:54 jabber_lib.process: 180 Error caught: > Traceback (most recent call last): > File "/usr/share/rhn/osad/jabber_lib.py", line 120, in main > self.process_forever(c) > File "/usr/share/rhn/osad/jabber_lib.py", line 178, in > process_forever self.process_once(client) > File "/usr/share/rhn/osad/osad.py", line 249, in process_once > client.process(timeout=180) > File "/usr/share/rhn/osad/jabber_lib.py", line 1040, in process > data = self._read(self.BLOCK_SIZE) > SSLError: ('OpenSSL error; will retry', "(-1, 'Unexpected EOF')") > > 2016-05-19 15:54:54 jabber_lib.main: Sleeping 115 seconds Maybe this will help you: http://h20564.www2.hpe.com/hpsc/doc/public/display?docId=mmr_kc-0122182 In short, make sure <idle>0</idle> is in /etc/jabberd/c2s.xml The redhat solution mentioned at https://access.redhat.com/solutions/64908 explains it further: " The setting was causing the client connection to the jabber service to be terminated if there was no data sent over the connection after 200 seconds. The client would reconnect after about 1 or 2 minutes though. Basically, if the value is non-zero then the jabber c2s service uses this value as a connection timeout and will terminate the connection if there is no data sent over the connection before the timeout expires. The osad process will (try to) re-connect to the jabber service after about 1 or 2 minutes. And again, if there is no further data sent over the connection then jabber will close the connection. " And further down: " The SSLError traceback is just a result of the jabber service on the satellite closing the connection because of the use of a non-zero setting in the /etc/jabberd/c2s.xml file. The traceback is normal behaviour if osad is run in the foreground and doesn't appear if osad is run in the background. " Franky _______________________________________________ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been scanned by Proofpoint PPS and F-Secure for the presence of computer viruses. _______________________________________________ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list _______________________________________________ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
