Closed
Bug 778814
(tegra-040)
Opened 12 years ago
Closed 10 years ago
tegra-040 problem tracking
Categories
(Infrastructure & Operations Graveyard :: CIDuty, task, P3)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: coop, Unassigned)
References
()
Details
(Whiteboard: [buildduty][buildslaves][capacity])
No description provided.
Updated•12 years ago
|
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Comment 1•12 years ago
|
||
Last job 31 days, 6:46:38 ago Had error.flg [Remote Device Error: Unable to properly remove /mnt/sdcard/tests] Did a remote sdcard format -- todo -- look back in on it.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 2•12 years ago
|
||
that fixed it...
Status: REOPENED → RESOLVED
Closed: 12 years ago → 12 years ago
Resolution: --- → FIXED
Comment 3•12 years ago
|
||
Throwing error.flg [Remote Device Error: Unable to properly remove /mnt/sdcard/tests] again. I'm trying a remote format.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 4•12 years ago
|
||
Back in production....for now.
Status: REOPENED → RESOLVED
Closed: 12 years ago → 12 years ago
Resolution: --- → FIXED
Comment 5•12 years ago
|
||
Manually reformatted its sdcard today, pdu rebooted, and cleared the error flag. It's back in production and running builds.
Comment 6•12 years ago
|
||
was cycling with 2012-12-04 04:12:01,092 INFO MainProcess: buildslave start returned 1 again. After a connection-lost to bm20. I ./stop_cp and ./start_cp cycled it.
Comment 7•12 years ago
|
||
Back to being dead, please swap SDCard and reimage.
Updated•12 years ago
|
Status: REOPENED → RESOLVED
Closed: 12 years ago → 12 years ago
Resolution: --- → FIXED
Comment 8•11 years ago
|
||
needed to be rebooted -> checking that it comes up again
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 9•11 years ago
|
||
and we have it back 01/31/2013 05:01:21: INFO: Tegra ID M Tegra CP Slave :: Msg 2013-01-31 05:01:21,464 Tegra ID M Tegra CP Slave :: Msg 01/31/2013 05:01:27: INFO: tegra-040 p online active active :: 2013-01-31 05:01:27,566 tegra-040 p online active active ::
Status: REOPENED → RESOLVED
Closed: 12 years ago → 11 years ago
Resolution: --- → FIXED
Comment 10•11 years ago
|
||
also rebooted again and its back bash-3.2$ ps auxw | grep "tegra-040" cltbld 24367 0.0 0.1 2447536 2828 ?? S 3:50AM 0:00.03 /opt/local/Library/Frameworks/Python.framework/Versions/2.6/Resources/Python.app/Contents/MacOS/Python clientproxy.py -b --device=tegra-040 cltbld 24366 0.0 0.1 2457276 3332 ?? S 3:50AM 0:00.02 /opt/local/Library/Frameworks/Python.framework/Versions/2.6/Resources/Python.app/Contents/MacOS/Python clientproxy.py -b --device=tegra-040 cltbld 24492 0.0 0.3 2464032 11624 ?? S 3:54AM 0:01.30 /opt/local/Library/Frameworks/Python.framework/Versions/2.6/Resources/Python.app/Contents/MacOS/Python /opt/local/Library/Frameworks/Python.framework/Versions/2.6/bin/twistd --no_save --rundir=/builds/tegra-040 --pidfile=/builds/tegra-040/twistd.pid --python=/builds/tegra-040/buildbot.tac bash-3.2$ ./check.sh -t tegra-040 02/01/2013 03:54:58: INFO: Tegra ID M Tegra CP Slave :: Msg 2013-02-01 03:54:58,725 Tegra ID M Tegra CP Slave :: Msg 02/01/2013 03:55:04: INFO: tegra-040 p online active active :: 2013-02-01 03:55:04,771 tegra-040 p online active active :: bash-3.2$
Updated•11 years ago
|
Assignee | ||
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
Comment 11•11 years ago
|
||
Monday, September 30, 2013 7:37:21 PM
Comment 12•11 years ago
|
||
replaced SD and flashed/reimaged, however it seems this tegra is overheating and there's a slight burning smell. if it fails again, we should decommission it.
Comment 13•11 years ago
|
||
sdcard replaced and reimaged/flashed.
Comment 14•10 years ago
|
||
handled in last recovery on Dec 16.
Status: REOPENED → RESOLVED
Closed: 11 years ago → 10 years ago
Resolution: --- → FIXED
Comment 15•10 years ago
|
||
2014-01-16 10:10:16 tegra-040 p OFFLINE active OFFLINE :: PING tegra-040.tegra.releng.scl3.mozilla.com (10.26.85.27) 56(84) bytes of data. From foopy112.tegra.releng.scl3.mozilla.com (10.26.84.12) icmp_seq=2 Destination Host Unreachable;error.flg [Automation Error: Unable to ping device after 5 attempts] pdu reboot didn't help
Comment 16•10 years ago
|
||
SD card reimaged/flashed.
Comment 17•10 years ago
|
||
Still failing to mount an sdcard
Comment 18•10 years ago
|
||
Attempting SSH reboot...Failed. Attempting PDU reboot...Failed. Filed IT bug for reboot (bug 966371)
Reporter | ||
Comment 19•10 years ago
|
||
error.flg is set to: Automation Error: Unable to connect to device after 5 attempts
Depends on: 977305
Comment 20•10 years ago
|
||
SD card flashed and tegra reimaged. if it fails again we can replace the SD card. [vle@admin1a.private.scl3 ~]$ telnet tegra-040.tegra.releng.scl3.mozilla.com 20701 Trying 10.26.85.27... Connected to tegra-040.tegra.releng.scl3.mozilla.com. Escape character is '^]'. $>
Comment 21•10 years ago
|
||
Taking jobs again
Status: REOPENED → RESOLVED
Closed: 10 years ago → 10 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Product: Release Engineering → Infrastructure & Operations
Updated•4 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
•