[Spacewalk-list] jabberd and c2s dying every couple of days
Jan Pazdziora
jpazdziora at redhat.com
Mon May 16 11:30:56 UTC 2011
On Fri, May 13, 2011 at 08:29:31AM -0400, Hagberg, Keith wrote:
> Running spacewalk 1.3 and having a problem where the c2s service is sowing %100 CPU utilization when using the top command. Overall CPU is running at about 6%. When this happens jabberd just stops working. Bouncing jabberd fixes the issue for a few days. I currently have about 1200 servers registered in spacewalk. Am I hitting a default limit of 1024 clients and should increasing the maximum number of file descriptors in the c2s.xml file correct this?
>
It definitely shouldn't hurt to have the number of descriptors match
the number of systems that are managed via osad.
--
Jan Pazdziora
Principal Software Engineer, Satellite Engineering, Red Hat
More information about the Spacewalk-list
mailing list