Closed Bug 1193412 (t-yosemite-r5-0063) Opened 10 years ago Closed 10 years ago

t-yosemite-r5-0063 problem tracking

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task, P3)

x86_64
macOS

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: philor, Unassigned)

Details

(Whiteboard: [buildduty][buildslaves][capacity])

Stopped taking jobs yesterday, multiple reboots haven't helped.
Looked over the logs from t-yosemite-r5-0063.test.releng.scl3.mozilla.com. As it can be noticed, there are several connection losses followed by re-connections on August 10. Following the last one, the connection was not re-established. 2015-08-10 09:22:28-0700 [Broker,client] Lost connection to buildbot-master107.bb.releng.scl3.mozilla.com:9201 2015-08-10 09:25:02-0700 [-] Connecting to buildbot-master107.bb.releng.scl3.mozilla.com:9201 2015-08-10 09:25:04-0700 [Broker,client] Connected to buildbot-master107.bb.releng.scl3.mozilla.com:9201; slave is ready 2015-08-10 09:36:55-0700 [Broker,client] Lost connection to buildbot-master107.bb.releng.scl3.mozilla.com:9201 2015-08-10 09:39:26-0700 [-] Connecting to buildbot-master107.bb.releng.scl3.mozilla.com:9201 2015-08-10 09:39:30-0700 [Broker,client] Connected to buildbot-master107.bb.releng.scl3.mozilla.com:9201; slave is ready 2015-08-10 15:17:10-0700 [Broker,client] Lost connection to buildbot-master107.bb.releng.scl3.mozilla.com:9201 Also took a look on the buildbot master (buildbot-master107.bb.releng.scl3.mozilla.com). It seems that the slave was detached around the time when the last connection loss occurred. 2015-08-10 15:17:10-0700 [Broker,72561,10.26.56.58] BuildSlave.detached(t-yosemite-r5-0063)
Disabled the slave in slavealloc, restarted it and enabled it again. After that, I noticed that the connection to the master was re-established: 2015-08-12 02:17:17-0700 [-] Connecting to buildbot-master107.bb.releng.scl3.mozilla.com:9201 2015-08-12 02:17:18-0700 [Broker,client] Connected to buildbot-master107.bb.releng.scl3.mozilla.com:9201; slave is ready According to the netstat on the buildbot master we can see that the slave is connected: [root@buildbot-master107.bb.releng.scl3.mozilla.com master]# netstat -a | grep 't-yosemite-r5-0063' tcp 0 0 buildbot-master:wap-wsp-wtp t-yosemite-r5-0063.te:49294 ESTABLISHED Waiting to see if it starts taking jobs...
Started taking jobs.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Product: Release Engineering → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.