Closed
Bug 775496
Opened 12 years ago
Closed 12 years ago
investigate issues with talos-r3-fed64-006 and talos-r3-fed64-030
Categories
(Infrastructure & Operations :: DCOps, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: arich, Assigned: van)
References
Details
(Whiteboard: scl1)
Van tried rebooting these machines and neither came back properly. Please investigate further and reimage if needed.
Reporter | ||
Updated•12 years ago
|
Assignee: jwatkins → server-ops
colo-trip: --- → scl1
Component: Server Operations: RelEng → Server Operations: DCOps
QA Contact: arich → dmoore
Assignee | ||
Updated•12 years ago
|
Whiteboard: scl1
Assignee | ||
Comment 1•12 years ago
|
||
The switch ports on these 2 machines are bad. I will be setting a spare ex2200 and rerun their uplinks.
van
Assignee | ||
Comment 2•12 years ago
|
||
I installed a spare switch (switch2.r101-10.scl1) and reran the network connections for these hosts. Inventory has been updated. Please let me know if issues persist.
[root@admin1 ~]# fping talos-r3-fed64-006.build.scl1.mozilla.com
talos-r3-fed64-006.build.scl1.mozilla.com is alive
[root@admin1 ~]# fping talos-r3-fed64-030.build.scl1.mozilla.com
talos-r3-fed64-030.build.scl1.mozilla.com is alive
Regards,
Van
Assignee | ||
Updated•12 years ago
|
Assignee: server-ops → vle
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Product: mozilla.org → Infrastructure & Operations
You need to log in
before you can comment on or make changes to this bug.
Description
•