Closed
Bug 1398084
Opened 8 years ago
Closed 8 years ago
Generic worker exception kills all workers
Categories
(Taskcluster :: Workers, defect)
Taskcluster
Workers
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: franziskus, Unassigned)
Details
Our NSS Mac generic worker ran into an error with one job
2017/09/08 06:12:08 ERROR encountered: Task not successful due to following exception(s):
Exception 1)
(Permanent) HTTP response code 400
HTTP/1.1 400 Bad Request^M
Connection: close^M
Transfer-Encoding: chunked^M
Content-Type: application/xml^M
Date: Fri, 08 Sep 17 10:10:15 GMT^M
Following this error all other jobs were marked as failed.
Comment 1•8 years ago
|
||
Hi Franziskus,
Sorry to hear about this. Do you have more logs, and the taskId where this occurred?
Thanks,
Pete
Comment 2•8 years ago
|
||
It looks like this was due to "idleTimeoutSecs" generic-worker configuration property being set to 345600 instead of 0. I've updated the 10 worker generic-worker.config files for worker[0..9] to remove this property, so that the default value of 0 is used (which means worker runs forever).
I believe this should solve it.
It might not be a bad thing to reboot once a week or so though.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
| Assignee | ||
Updated•7 years ago
|
Component: Generic-Worker → Workers
You need to log in
before you can comment on or make changes to this bug.
Description
•