Closed Bug 838426 (tegra-346) Opened 11 years ago Closed 11 years ago

tegra-346 problem tracking

Categories

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

ARM
Android

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: Callek, Unassigned)

References

()

Details

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

No jobs taken on this device for > a week (< 3 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
Depends on: 838687
did a start/stop cp cycle
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
7 days without taking a job.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Depends on: 858134
recovery didn't help, dunno what to do
2013-04-05 06:05:47 tegra-346 p  INACTIVE   active  OFFLINE :: SUTAgent not present;
Depends on: 865749
Callek just stopped it, because it was still enabled and managed to come back to life in April, run with a horrible record and unimpressive number of jobs per day, until I just noticed it running on January 1, 1970. Surprisingly, our tests don't like to be run in 1970.
Sending this slave to recovery
-->Automated message.
Depends on: 889567
Depends on: 892096
sutagent won't stay up...
Product: mozilla.org → Release Engineering
16:46 < nagios-releng> Wed 13:46:36 PDT [4532] tegra-346.build.mtv1.mozilla.com:tegra agent check is 
                       CRITICAL: Connection refused (http://m.allizom.org/tegra+agent+check)

pdu reboot didn't help
Depends on: 912682
swapped sd card
recovery didn't help, dunno what to do
Currently reporting "Remote Device Error: unable to write to sdcard"
Depends on: 928492
Remote Device Error: unable to write to sdcard
Depends on: 934493
Fell out of production again.
Depends on: 937173
flashed and reimaged
can't reliably keep this device up --> decomm
Depends on: tegra-decomm
decommed
Status: REOPENED → RESOLVED
Closed: 11 years ago11 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.