Closed Bug 792693 (tegra-336) Opened 12 years ago Closed 11 years ago

tegra-336 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])

Lets reimage and swap sdcard... it has never taken a production job :/
swapped sdcard and tegra is also pingable --- tegra-336.build.mtv1.mozilla.com ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 21.549/21.549/21.549/0.000 ms
$ ./check.sh -t tegra-336 2012-10-04 09:34:57,425 Tegra ID M Tegra CP Slave :: Msg 2012-10-04 09:35:01,445 tegra-336 p INACTIVE active OFFLINE :: SUTAgent not present;error.flg [Remote Device Error: unable to write to sdcard] $ telnet tegra-336 20701 Trying 10.250.51.176... telnet: connect to address 10.250.51.176: Connection refused
tried a pdu reboot, don't know what else to do.
Assignee: nobody → bugspam.Callek
That appears to have been what to do - it took a couple of hours before it took a job, but since then it's been running as well as a tegra in the 300s can be expected to run.
Assignee: bugspam.Callek → nobody
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
No jobs taken on this device for >= 7 weeks
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(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
Back from recovery
Status: REOPENED → RESOLVED
Closed: 12 years ago12 years ago
Resolution: --- → FIXED
9 days, 5:07:04 since last job
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
back in production
Status: REOPENED → RESOLVED
Closed: 12 years ago12 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
won't reliably stay up --> decomm
Status: RESOLVED → REOPENED
Depends on: tegra-decomm
Resolution: FIXED → ---
decommed
Status: REOPENED → RESOLVED
Closed: 12 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.