Comment 17 for bug 802850
Revision history for this message
| Mike Willbanks (mike-digitalstruct) wrote | #17 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Had another one spin out of control this morning on our test environment....
Looks like we had the following:
4 - stale workers... no connections
4 - active workers (queues seemed to be locked)
Connection thread seemed to be fine but the gearmand process seems to have continued but was high jacking the CPU. One of the workers was taking approximately 30% of the cpu. a restart of the gearmand process seems to resolve this when it happens.