[Spacewalk-list] osa-dispatcher performance

[Stuart Green]

Sorry for the multiple emails, but just noticed the below server side..  
Now I don't get this as the cert does exist on the client machine and 
/etc/sysconfig/rhn/up2date points to it, I'll admit I pasted it into an 
empty file with vi from Notepad++ , but I did the unix conversion first 
and have double checked there are no control characters with "cat -v" on 
the file...  Anyway if this was the problem why would it eventually 
work!  ~sigh

2014-04-23 10:45:22 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 1044, in process
     data = self._read(self.BLOCK_SIZE)
SSLError: ('OpenSSL error; will retry', "(-1, 'Unexpected EOF')")

2014-04-23 10:45:22 jabber_lib.main: Sleeping 95 seconds


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 1044, in process
     data = self._read(self.BLOCK_SIZE)
SSLError: ('OpenSSL error; will retry', "(-1, 'Unexpected EOF')")

2014-04-23 10:52:57 jabber_lib.main: Sleeping 78 seconds




> I've just changed my timezone from EDT to United Kingdom now on the 
> spacewalk server.  Hopefully this might resolve the problem as there's 
> a lot of time dependency involved.
>
> AFAIK I think I've seen the list talking about an EDT issue with 2.1, 
> although I couldn't say for sure what it was set to before I did the 
> 2.0 > 2.1 upgrade.
>
> Fingers crossed!
>
>
>> Hello list,
>>
>> No doubt a topic of this nature has been discussed before, but could 
>> anyone point me in the direction as to why osa-dispatcher > up2date 
>> patch deployment could be so slooow?
>>
>> 10 hours seems a bit excessive...
>>
>> Details: 	This action will be executed after 04/17/14 5:24:00 AM EDT.
>>
>> This action's status is: Completed.
>> The client picked up this action on 04/17/14 3:51:58 PM EDT.
>> The client completed this action on 04/17/14 3:53:58 PM EDT.
>> Client execution returned "Update Succeeded" (code 0)
>> Packages Scheduled:
>>
>>   * cpuspeed-1.2.1-11.el5_10:1.x86_64
>>
>> Time: 	04/17/14 5:24:09 AM EDT
>>
>>
>>
>> I really need to be able to deploy patches within a 1hr window on our 
>> productions servers or I miss our maintenance window. Any pointers 
>> would be much appreciated.
>>
>> Spacewalk 2.1 Deploying to Centos 5/6 servers.
>>
>> Cheers,
>> Stuart
>>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20140423/5f6a877f/attachment.htm>