Closed
Bug 947549
Opened 11 years ago
Closed 11 years ago
bugzilla1.community.scl3 needs to be reimaged
Categories
(mozilla.org Graveyard :: Server Operations, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: justdave, Assigned: afernandez)
References
Details
This machine is in inventory at: https://inventory.mozilla.org/en-US/systems/show/1729/ The hard drive failed and was replaced with a blank drive, we need the machine re-imaged with a clean system load. Previously had RHEL5 on it, should be fine to use RHEL6 this time. We have backups that we can deal with restoring after the machine is back on the network. Thanks!
Comment 1•11 years ago
|
||
ping? How long before this happens? We want to release Bugzilla 4.4.2, but all our test installations are unavailable for already 10 days now.
Reporter | ||
Updated•11 years ago
|
Severity: normal → major
Updated•11 years ago
|
Assignee: server-ops → eziegenhorn
Reporter | ||
Comment 2•11 years ago
|
||
ping? We have a release of Bugzilla waiting to go out the door which is pending being able to run tests on it before we release. This is our test machine.
Assignee: eziegenhorn → server-ops
Assignee | ||
Comment 4•11 years ago
|
||
Server currently being kickstarted, should be online within 1 hour or so.
Status: NEW → ASSIGNED
Assignee | ||
Comment 5•11 years ago
|
||
host is online with our current root ssh key-ring (please delete once configure for community use). Currently IP is configured on eth0 and bonding was not configured as seems these machines are configured differently from our typical set-ups.
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 6•11 years ago
|
||
I can't reach this on the network, did it come back up after kickstarting? Is it back on the community network?
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 7•11 years ago
|
||
The server had an error on eth0 "Reset adapter unexpectedly" and "e1000e ... eth0: Timesync Tx Control register not set as expected". I reboot it and now it's reachable on the network.
Comment 8•11 years ago
|
||
The server went offline again, once without any console errors and once again with the same error as the previous comment.
Reporter | ||
Comment 9•11 years ago
|
||
Adding pcie_aspm=off to the kernel params in Grub appears to have fixed this. Both bugzilla1 and bugzilla3 are up and seem to be stable now. And for the record, the serial console on these boxes is on ttyS2. (Every doc I could find anywhere suggested ttyS0 or ttyS1, didn't know a box could have a ttyS2 :)
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → FIXED
Updated•9 years ago
|
Product: mozilla.org → mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•