Closed
Bug 829055
(tegra-335)
Opened 12 years ago
Closed 10 years ago
tegra-335 problem tracking
Categories
(Infrastructure & Operations Graveyard :: CIDuty, task, P3)
Infrastructure & Operations Graveyard
CIDuty
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: bhearsum, Unassigned)
References
()
Details
(Whiteboard: [buildduty][buildslaves][capacity])
10:45 < nagios-releng> Thu 07:45:48 PST [496] tegra-335.build.mtv1.mozilla.com:tegra agent check is CRITICAL: Connection refused
trying a pdu reboot
Comment 2•12 years ago
|
||
(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
Comment 3•12 years ago
|
||
Back from recovery
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Comment 4•12 years ago
|
||
I think the SD card is fried.
https://bugzilla.mozilla.org/show_bug.cgi?id=832424#c1
Can I assume that the next step is to file a tegra-recovery bug and re-open this one?
Comment 5•12 years ago
|
||
I cannot write anymore to the SD card.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 7•12 years ago
|
||
It is taking jobs now!
Status: REOPENED → RESOLVED
Closed: 12 years ago → 12 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Assignee | ||
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
Reporter | ||
Updated•11 years ago
|
Comment 8•11 years ago
|
||
sd card formatted, tegra flashed and reimaged.
[vle@admin1a.private.scl3 ~]$ fping tegra-335.tegra.releng.scl3.mozilla.com
tegra-335.tegra.releng.scl3.mozilla.com is alive
Updated•11 years ago
|
Assignee: armenzg → nobody
Comment 9•11 years ago
|
||
Power cycled, waited a day.
error.flg: Automation Error: Unable to connect to device after 5 attempts
Pings but can't connect via telnet.
Comment 10•11 years ago
|
||
running very green bar one robocop RETRY.
it seems like robocop in m-c and m-i often has a RETRY so I am marking this as resolved under the assumption this is normal.
Status: REOPENED → RESOLVED
Closed: 12 years ago → 11 years ago
Resolution: --- → FIXED
Comment 11•10 years ago
|
||
Being decomm'd along with foopy31
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 12•10 years ago
|
||
Decomm'd along with foopy31 in Bug 859196
Status: REOPENED → RESOLVED
Closed: 11 years ago → 10 years ago
Resolution: --- → WONTFIX
Updated•7 years ago
|
Product: Release Engineering → Infrastructure & Operations
Updated•5 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•