tegra-223 has been offline for 14 days according to last-build-per-slave.html.

tegra-223 needs to be reimaged - it is not staying up long enough to take a job. if this image doesn't fix it then it should be on the short list for a swap.

tegra-223 itself is running but clientproxy/buildbot are having trouble staying active

offline and did pdu reboot and its back bash-3.2$ ps auxw | grep "tegra-229" cltbld 66742 0.0 0.0 2447068 2792 ?? S 6:32AM 0:00.03 /opt/local/Library/Frameworks/Python.framework/Versions/2.6/Resources/Python.app/Contents/MacOS/Python clientproxy.py -b --device=tegra-229 cltbld 66741 0.0 0.0 2466024 3460 ?? S 6:32AM 0:00.03 /opt/local/Library/Frameworks/Python.framework/Versions/2.6/Resources/Python.app/Contents/MacOS/Python clientproxy.py -b --device=tegra-229 cltbld 66805 0.0 0.0 2434892 444 s001 S+ 6:34AM 0:00.00 grep tegra-229 cltbld 66802 0.0 0.1 2472732 11016 ?? S 6:34AM 0:00.72 /opt/local/Library/Frameworks/Python.framework/Versions/2.6/Resources/Python.app/Contents/MacOS/Python /opt/local/bin/twistd --no_save --rundir=/builds/tegra-229 --pidfile=/builds/tegra-229/twistd.pid --python=/builds/tegra-229/buildbot.tac bash-3.2$ ./check.sh -t tegra-229 02/01/2013 06:35:04: INFO: Tegra ID M Tegra CP Slave :: Msg 2013-02-01 06:35:04,085 Tegra ID M Tegra CP Slave :: Msg 02/01/2013 06:35:10: INFO: tegra-229 p online active active :: 2013-02-01 06:35:10,124 tegra-229 p online active active :: bash-3.2$

No jobs taken on this device for > a day (< a week) [c#3 accidentally did 229 not 223]

(mass change: filter on tegraCallek02reboot2013) I just rebooted this device, hoping that many of the ones I'm doing tonight come back automatically. I'll check back in tomorrow to see if it did, if it does not I'll triage next step manually on a per-device basis. --- Command I used (with a manual patch to the fabric script to allow this command) (fabric)[jwood@dev-master01 fabric]$ python manage_foopies.py -j15 -f devices.json `for i in 021 032 036 039 046 048 061 064 066 067 071 074 079 081 082 083 084 088 093 104 106 108 115 116 118 129 152 154 164 168 169 174 179 182 184 187 189 200 207 217 223 228 234 248 255 264 270 277 285 290 294 295 297 298 300 302 304 305 306 307 308 309 310 311 312 314 315 316 319 320 321 322 323 324 325 326 328 329 330 331 332 333 335 336 337 338 339 340 341 342 343 345 346 347 348 349 350 354 355 356 358 359 360 361 362 363 364 365 367 368 369; do echo '-D' tegra-$i; done` reboot_tegra The command does the reboot, one-at-a-time from the foopy the device is connected from. with one ssh connection per foopy

had to cycle clientproxy to bring this back

Last job Tuesday, August 27, 2013 6:09:49 PM

SD card has been replaced and reimaged/flashed.

Back in production

Power cycled, waited a day. error.flg: Remote Device Error: process from previous test run present Automation Error: Unable to properly cleanup foopy processes SD card reformat successful: $>exec newfs_msdos -F 32 /dev/block/vold/179:9 newfs_msdos: warning, /dev/block/vold/179:9 is not a character device newfs_msdos: Skipping mount checks /dev/block/vold/179:9: 31100416 sectors in 485944 FAT32 clusters (32768 bytes/cluster) bps=512 spc=64 res=32 nft=2 mid=0xf0 spt=16 hds=4 hid=0 bsec=31108096 bspf=3797 rdcl=2 infs=1 bkbs=2 return code [0] $>exec rebt $>^]

reformat did not fix issue. last job 03/14/2014 ./check.sh: 2014-04-09 13:49:27,813 tegra-223 p online active OFFLINE :: error.flg [Automation Error: Unable to properly cleanup foopy processes] watcher.log: 1997 04/09/2014 13:25:04: DEBUG: remotereftest: looking for /builds/tegra-223/remotereftest.pid 1998 04/09/2014 13:25:04: ERROR: remotereftest: unable to read /builds/tegra-223/remotereftest.pid 1999 04/09/2014 13:25:04: DEBUG: remotereftest.pid.xpcshell: looking for /builds/tegra-223/remotereftest.pid.xpcshell.pid 2000 04/09/2014 13:25:04: ERROR: remotereftest.pid.xpcshell: unable to read /builds/tegra-223/remotereftest.pid.xpcshell.pid 2001 04/09/2014 13:25:04: INFO: /builds/tegra-223/error.flg 2002 04/09/2014 13:25:34: INFO: /builds/tegra-223/error.flg 2003 04/09/2014 13:26:04: INFO: verifyDevice: failing to cleanup foopy 2004 Remote Device Error: process from previous test run present 2005 Automation Error: Unable to properly cleanup foopy processes not sure what to do here? Any ideas tegra master callek?

There were some old pid files in /builds/tegra-223 that were preventing this device from starting.

This tegra is hitting bug 1011788; re-image please - disabled for now.

formatted SD card, flashed and reimaged tegra. vle@vle-10516 ~ $ telnet tegra-223.tegra.releng.scl3.mozilla.com 20701 Trying 10.26.85.174... Connected to tegra-223.tegra.releng.scl3.mozilla.com. Escape character is '^]'. $>^] telnet> q