bld-centos6-hp-006.build.scl1.mozilla.com multiple issues per nagios (disk errors ~8hr before unpingable): IDE S.M.A.R.T - /dev/sda -- 2d 2h 34m 18s PING -- 1d 16h 45m 16s buildbot -- 1d 16h 43m 7s disk - / -- 1d 16h 40m 38s
Back in production.
infinite retry due to no space left on disk.
Stuck git lock, burning b2g jobs, disabled.
Back into production now bug 1005185 is fixed.
Out of space. Disabled.
It failed in a vagrant build, trying to set up the mock environment, which is prior to clearing out new space in the mozharness script. I've removed a rel-m-beta-fennec_source-00000 dir and re-enabled.
Happened to log onto this by accident today, this was in the motd: NOTE: puppet environment pinned to 'sbruno' NOTE: puppet server pinned to 'releng-puppet2.srv.releng.scl3.mozilla.com' Can be ondone now ?
The box was still pinned to my puppet env as I have been using it for some tests, but it has been enabled in slavealloc and added to the prod pool. This caused some repack failures on Firefox 32.0b8 build1 last night. I disabled it on slavealloc, and I am now cleaning it up.
Last comment said you were doing stuff with it, status?
Oh, sorry for this, I kept using this box for some time now... It definitely needs to be reimaged. How do I connect to the management web interface and start the java KVM console to follow the procedure described in https://mana.mozilla.org/wiki/display/DC/How+To+Reimage+Releng+iX+and+HP+Linux+Machines ?
You'd load https://b-linux64-hp-0025-mgmt.build.mozilla.org in your browser, p/w in the usual store. But first you'll have to defeat firefox not wanting to let you open the page.
(In reply to Nick Thomas [:nthomas] from comment #12) > You'd load https://b-linux64-hp-0025-mgmt.build.mozilla.org in your browser, > p/w in the usual store. But first you'll have to defeat firefox not wanting > to let you open the page. I just use Safari or Chrome. I'm kicked off a re-image here and re-enabled the slave in slavealloc.
Please do not re-enable this slave. We are retiring linux hardware build slaves in bug 1106922.