Phil Ringnalda (:philor) Reporter
	Description • 9 years ago

Stopped taking jobs yesterday, multiple reboots haven't helped.

	Alin Selagea [:aselagea]
	Comment 1 • 9 years ago

Disabled in slavealloc, rebooted and then re-enabled it. At the moment, it seems that the slave managed to connect to the master (buildbot-master112.bb.releng.scl3.mozilla.com):

2015-08-12 05:06:22-0700 [Broker,client] Connected to buildbot-master112.bb.releng.scl3.mozilla.com:9201; slave is ready

Also, according to netstat output from the master, the connection with the slave is established:

[root@buildbot-master112.bb.releng.scl3.mozilla.com master]# netstat -a | grep 't-w732-ix-055'
tcp        0      0 buildbot-master:wap-wsp-wtp t-w732-ix-055.wintest:49270 ESTABLISHED 

We shall wait to see if it starts taking jobs.

	Alin Selagea [:aselagea]
	Comment 2 • 9 years ago

Started taking jobs.

	Phil Ringnalda (:philor) Reporter
	Comment 3 • 9 years ago

Stopped taking jobs yesterday, multiple reboots haven't helped. Disabled, rebooted, enabled, rebooted.

I'm rather horrified that we're going to have to do that for this slave once a week, but, if the trains run on time, the trains run on time, and it's already doing a job.

	Release Engineering SlaveAPI Service
	Comment 4 • 6 years ago

Attempting SSH reboot...Failed.
Attempting IPMI reboot...Failed.
Filed IT bug for reboot (bug 1446996)

	Zsolt Fay [:zfay]
	Comment 5 • 6 years ago

Machine is back and taking jobs properly.