Last Job 2 days, 15:09:45 ago

error.flg [Remote Device Error: unable to write to sdcard] Time for an sdcard replacement.

Ran ./stop_cp.sh

Should be back.

No jobs taken on this device for >= 7 weeks

(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

needed a clientproxy off/on cycle.

Hasn't run a job in 10 days, 20:43:51

pdu reboot didn't work

recovery didn't help, dunno what to do 2013-04-05 06:10:13 tegra-064 p online active OFFLINE :: error.flg [Automation Error: Unable to connect to device after 5 attempts]

It suddenly came back to life on May 10th, but it might as well have not bothered - 16 jobs since then is virtually nothing, 8 of them green is an abysmal percentage.

I'm going to resolve this, since a manual PDU reboot brought it back to running buildbot. Not quite expecting it to stay happy though

can't reliably keep this device up --> decomm

decommed