Closed
Bug 732229
Opened 14 years ago
Closed 11 years ago
self-serve agent crashing out
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: nthomas, Unassigned)
Details
(Keywords: buildapi)
This happened once yesterday and again today:
Traceback (most recent call last):
File "buildapi/buildapi/scripts/selfserve-agent.py", line 562, in <module>
consumer.wait()
File "/builds/buildbot/selfserve-agent/lib/python2.6/site-packages/carrot/messaging.py", line 446, in wait
it.next()
File "/builds/buildbot/selfserve-agent/lib/python2.6/site-packages/carrot/backends/pyamqplib.py", line 300, in consume
self.channel.wait()
File "/builds/buildbot/selfserve-agent/lib/python2.6/site-packages/amqplib/client_0_8/abstract_channel.py", line 89, in wait
self.channel_id, allowed_methods)
File "/builds/buildbot/selfserve-agent/lib/python2.6/site-packages/amqplib/client_0_8/connection.py", line 218, in _wait_method
self.wait()
File "/builds/buildbot/selfserve-agent/lib/python2.6/site-packages/amqplib/client_0_8/abstract_channel.py", line 105, in wait
return amqp_method(self, args)
File "/builds/buildbot/selfserve-agent/lib/python2.6/site-packages/amqplib/client_0_8/connection.py", line 367, in _close
raise AMQPConnectionException(reply_code, reply_text, (class_id, method_id))
amqplib.client_0_8.exceptions.AMQPConnectionException: (320, u"CONNECTION_FORCED - broker forced connection closure with reason 'shutdown'", (0, 0), '')
leading to
buildbot-master10.build.sjc1:self service agent is CRITICAL: PROCS CRITICAL: 0 processes with args selfserve-agent.py
| Reporter | ||
Comment 1•14 years ago
|
||
On restart it seems to pick up messages and process them OK.
| Reporter | ||
Updated•14 years ago
|
Component: Release Engineering: Automation → Release Engineering: Developer Tools
QA Contact: catlee → lsblakk
| Assignee | ||
Updated•13 years ago
|
Product: mozilla.org → Release Engineering
Comment 2•11 years ago
|
||
Probably won't be fixing this because self serve is going to be deprecated after all scheduling moves to Taskcluster.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
| Assignee | ||
Updated•9 years ago
|
Component: Tools → General
You need to log in
before you can comment on or make changes to this bug.
Description
•