[Spacewalk-list] jabberd and c2s dying every couple of days

[Hagberg, Keith]

Anyone have and ideas here?

Keith

-----Original Message-----
From: spacewalk-list-bounces at redhat.com [mailto:spacewalk-list-bounces at redhat.com] On Behalf Of Hagberg, Keith
Sent: Monday, May 16, 2011 8:24 AM
To: spacewalk-list at redhat.com
Subject: Re: [Spacewalk-list] jabberd and c2s dying every couple of days

I bumped it up to 4096 and am still having the issue. 

Keith

-----Original Message-----
From: spacewalk-list-bounces at redhat.com [mailto:spacewalk-list-bounces at redhat.com] On Behalf Of Jan Pazdziora
Sent: Monday, May 16, 2011 7:31 AM
To: spacewalk-list at redhat.com
Subject: Re: [Spacewalk-list] jabberd and c2s dying every couple of days

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

_______________________________________________
Spacewalk-list mailing list
Spacewalk-list at redhat.com
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