Closed
Bug 1249868
Opened 10 years ago
Closed 10 years ago
crashplan2.private.tor1.mozilla.com doesn't come back up
Categories
(Infrastructure & Operations :: MOC: Problems, task)
Infrastructure & Operations
MOC: Problems
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: Usul, Assigned: pir)
Details
https://inventory.mozilla.org/en-US/systems/show/4872/
I've patched the machine but it doesn't come back up on reboot.
| Reporter | ||
Comment 1•10 years ago
|
||
Can't seeh to the oob nor ipmitool to it :
[lhirlimann@admin1a.private.tor1 ~]$ ipmitool -H 10.242.6.177 -U BBBBB -P CCCCC sensor
Error: Unable to establish LAN session
| Reporter | ||
Comment 2•10 years ago
|
||
Sat 05:35:06 PST [5036] crashplan2.private.tor1.mozilla.com (10.242.75.101) is UP :PING OK - Packet loss = 0%, RTA = 90.13 ms
but still can't connect to it.
| Assignee | ||
Comment 3•10 years ago
|
||
jlin took a look and reported this on the console:
e1000e 0000:03:00.0: eth0 reset adapter unexpectedly / Timesync Tx Control register not set as expected
and network was going down regularly even after reboots.
Googling for that led me to:
https://bugs.centos.org/view.php?id=6810
I tried this, quickly after a reboot:
sudo sed -i.pir 's]^\(.*kernel /vml.*\)$]\1 pcie_aspm=off]' /boot/grub/grub.conf
and rebooted again. It seems stable for now, jlin is monitoring.
it's been responding to pings and I've been logged in via ssh for about 20 min - should be fine now. Thanks Pir and Usul!
Comment 6•10 years ago
|
||
(In reply to Peter Radcliffe [:pir] from comment #4)
> :digi have you seen this before?
I have never seen this before.
Flags: needinfo?(bhourigan)
https://bugs.centos.org/view.php?id=6810#c19026 - also suggests turning the "Active State Power Management" bios option to "enabled".
if the network on this server drops off again, I could investigate that on the next reboot.
Comment 8•10 years ago
|
||
Still looks good. Reopen if this happens again.
Assignee: nobody → pradcliffe+bugzilla
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•