Comment 5 for bug 1353891
Revision history for this message
| Antoine "hashar" Musso (hashar) wrote | #5 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
I had the issue when creating a new job via the web interface. Apparently the Zuul gearman server stopped responding (forked process is still running but TCP connections to it timeout). Jenkins ends up using a bunch of CPU waiting for the port and does not process anything else.
Work around:
* disable the Gearman connection
* save config
The Zuul gearman server is happy again as shown with a workers command:
13 208.80.154.135 - :
14 208.80.154.135 Zuul Merger : merger:merge merger:update
82 208.80.154.135 Zuul RPC Listener : zuul:get_
110 208.80.154.135 - :
16 127.0.0.1 - :
.
The status command still report all the jobs albeit with 0 workers available.
* reenable gearman connection
* save config
The workers are repopulated and status shows jobs have workers available.
Maybe that is a bug in the python gear module.