831001 - (tegra-342) tegra-342 problem tracking

Status: RESOLVED FIXED

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

Description

[Armen [:armenzg]]

35 days, 18:01:17

Comment 1

[Aki Sasaki (not active)]

(In reply to Armen Zambrano G. [:armenzg] from comment #0)
> 35 days, 18:01:17

What does this mean?

Comment 2

[Armen [:armenzg]]

How many days it has not taken a job. Output from last job per slave.

Comment 3

[Aki Sasaki (not active)]

Better.

Comment 4

[Justin Wood (:Callek)]

No jobs taken on this device for > a day (< a week)

Comment 5

[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 6

[Justin Wood (:Callek)]

did a start/stop cp cycle

Comment 7

[Justin Wood (:Callek)]

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

Comment 8

[[e-mail] (:bhearsum)]

decommed