bugzilla1.community.scl3 needs to be reimaged

RESOLVED FIXED

Status

mozilla.org Graveyard
Server Operations
--
major
RESOLVED FIXED
4 years ago
3 years ago

People

(Reporter: justdave, Assigned: Aj)

Tracking

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

4 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.
Severity: normal → major

Updated

4 years ago
Assignee: server-ops → eziegenhorn
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 3

4 years ago
This will be up today.
Assignee: server-ops → afernandez
(Assignee)

Comment 4

4 years ago
Server currently being kickstarted, should be online within 1 hour or so.
Status: NEW → ASSIGNED
(Assignee)

Comment 5

4 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
Last Resolved: 4 years ago
Resolution: --- → FIXED
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 → ---
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.
The server went offline again, once without any console errors and once again with the same error as the previous comment.
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
Last Resolved: 4 years ago4 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.