778804 - (tegra-270) tegra-270 problem tracking

Status: RESOLVED FIXED

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

Comment 1

[Justin Wood (:Callek)]

This was down for a month and a half as far as jobs are concerned, just logged into its foopy, had the buildslave returned 1 issue, and a 2-day old hung clientproxy (verify.py actually). so I killed verify.py and say the buildslave issue, then I cycled cp (stop/stop) and tailed twistd.log and it is now taking a job.

Not sure if it will persist, but I'll resolve for now.

Comment 2

[Phil Ringnalda (:philor)]

Made it through 8 jobs, then it's done a bit over 50 red with a sprinkling of purple. I'd say we were better off without it.

Comment 3

[Justin Wood (:Callek)]

Lets try a reimage then a change of sdcard

Comment 4

[[e-mail] (:bhearsum)]

Back in production.

Comment 5

[Phil Ringnalda (:philor)]

Made it 20 green-and-orange runs before breaking again, but the last 7 in a row have been red.

Comment 6

[[e-mail] (:bhearsum)]

ran stop_cp.sh on it.

Comment 7

[[e-mail] (:bhearsum)]

Not sure what to do next, Callek?

Comment 8

[Justin Wood (:Callek)]

Had a hung SUTAgent, PDU cycled and now SUTAgent isn't even starting [afaict]

Slating for reimage one last time before I call it dead as a doorknob.

Comment 9

[Kim Moir [:kmoir] ET]

This tegra seems to be working fine the last few days.

Comment 10

[Phil Ringnalda (:philor)]

https://secure.pub.build.mozilla.org/buildapi/recent/tegra-270 - six reds in a row.

Comment 11

[Phil Ringnalda (:philor)]

11.

Comment 12

[Justin Wood (:Callek)]

stop ran here

Comment 13

[Justin Wood (:Callek)]

IT handled this, start_cp run now

Comment 14

[Phil Ringnalda (:philor)]

10 red in a row, SD card, or the trash pile?

Comment 15

[Nick Thomas [:nthomas] (UTC+12)]

stop_cp run on foopy23.

Comment 16

[Phil Ringnalda (:philor)]

22 retries in a row.

Comment 17

[Phil Ringnalda (:philor)]

Based on its history, I'll be back within 50 jobs.

Comment 18

[Phil Ringnalda (:philor)]

https://tbpl.mozilla.org/php/getParsedLog.php?id=15902674&tree=Mozilla-Aurora should mark the start

Comment 19

[Phil Ringnalda (:philor)]

https://tbpl.mozilla.org/php/getParsedLog.php?id=15903073&tree=Mozilla-Aurora

Comment 20

[Phil Ringnalda (:philor)]

https://tbpl.mozilla.org/php/getParsedLog.php?id=15905301&tree=Mozilla-Aurora

Comment 21

[Phil Ringnalda (:philor)]

https://tbpl.mozilla.org/php/getParsedLog.php?id=15938407&tree=Mozilla-Beta

Comment 22

[[e-mail] (:bhearsum)]

This tegra seems to be running jobs fine, until Philor shows me how wrong I am.

Comment 23

[Phil Ringnalda (:philor)]

84% green, which is the sort of thing which is making me start to think that somehow the results of recovery are... less determinate than we would like. Sort of random, even.

Comment 24

[Justin Wood (:Callek)]

No jobs taken on this device for >= 7 weeks

Comment 25

[Justin Wood (:Callek)]

(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 26

[Justin Wood (:Callek)]

had to cycle clientproxy to bring this back

Comment 27

[[e-mail] (:bhearsum)]

10 days, 14:03:35 since last job

Comment 28

[[e-mail] (:bhearsum)]

Back in production.

Comment 29

[Justin Wood (:Callek)]

Sending this slave to recovery
-->Automated reopening of bug

Comment 30

[Van Le [:van]]

flashed and reimaged.

Comment 31

[[e-mail] (:bhearsum)]

ping and agent checks failing; pdu reboot didn't help

Comment 32

[[e-mail] (:bhearsum)]

back in production

Comment 33

[Justin Wood (:Callek)]

one last recovery attempt, if this fails out before mtv move date (Jan 11 I think) we can call it decomm-worthy

Comment 34

[Eric Ramirez [:Eric]]

SD card has been replaced and reimaged/flashed.

Comment 35

[[e-mail] (:bhearsum)]

Back in production

Comment 36

[Phil Ringnalda (:philor)]

Hasn't taken a job for two weeks.

Comment 37

[Phil Ringnalda (:philor)]

Disabled in slavealloc to stop the pointless stream of reboots.

Comment 38

[Van Le [:van]]

SD card formatted, tegra flashed and reimaged.

vle@vle-10516 ~ $ telnet tegra-270.tegra.releng.scl3.mozilla.com 20701
Trying 10.26.85.218...
Connected to tegra-270.tegra.releng.scl3.mozilla.com.
Escape character is '^]'.
$>^]
telnet> q

Comment 39

[Phil Ringnalda (:philor)]

Reenabled.