[Spacewalk-list] osa-dispatcher performance

[Stuart Green]

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/935e9672/attachment.htm>