Closed Bug 828645 (tegra-344) Opened 12 years ago Closed 10 years ago

tegra-344 problem tracking

Categories

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

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: bhearsum, Unassigned)

References

()

Details

(Whiteboard: [buildduty][buildslaves][capacity])

15:55 < nagios-releng> Wed 12:55:46 PST [417] tegra-344.build.mtv1.mozilla.com:tegra agent check is CRITICAL: Connection refused (http://m.allizom.org/tegra+agent+check) trying a pdu reboot
didn't work, off to recovery.
Depends on: 825335
swapped sd card.
tegra was paging again, recovered 01/31/2013 05:28:55: INFO: Tegra ID M Tegra CP Slave :: Msg 2013-01-31 05:28:55,164 Tegra ID M Tegra CP Slave :: Msg 01/31/2013 05:29:01: INFO: tegra-344 p online active active :: 2013-01-31 05:29:01,189 tegra-344 p online active active ::
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Status: RESOLVED → REOPENED
Flags: needinfo?(bugspam.Callek)
Resolution: FIXED → ---
your wish is my command: (fabric)[jwood@cruncher.srv.releng.scl3 fabric]$ python manage_foopies.py -f devices.json -j15 -D tegra-344 stop [foopy31.build.mozilla.org] run: echo "disable please" > ./disabled.flg [OK] Stopped tegra-344
Flags: needinfo?(bugspam.Callek)
Thank you :-)
Sending this slave to recovery -->Automated message.
Depends on: 889567
Successfully recovered.
Status: REOPENED → RESOLVED
Closed: 12 years ago11 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
Depends on: foopy31
Being decomm'd along with foopy31
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Decomm'd along with foopy31 in Bug 859196
Status: REOPENED → RESOLVED
Closed: 11 years ago10 years ago
Resolution: --- → WONTFIX
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.