Closed Bug 557145 Opened 16 years ago Closed 16 years ago

cb-xserve04 can't see cvs.mozilla.org

Categories

(Infrastructure & Operations :: RelOps: General, task)

Product:
Infrastructure & Operations
Component:
RelOps: General
Platform:
All
macOS
Type:
task
Priority:
Not set
Severity:
major

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: alqahira, Assigned: phong)

References

Details

After rebooting cb-x4 this weekend, it suddenly stopped being able to connect to cvs.mozilla.org, turning builds red: http://tinderbox.mozilla.org/showlog.cgi?log=Camino/1270413600.1270414221.4427.gz I tried pinging cvs.mozilla.org with no luck (not even the "not allowed to ping" message I get elsewhere). I then rebooted again. Finally, I checked to make sure the DNS servers were still the ones specified in bug 546182, changed one that wasn't, and rebooted again. The box now seems to have "no" network connectivity; I can't ping anything or visit sites on the internet like http://www.apple.com/ caminobld@cb-xserve04 bash$ cat /etc/resolv.conf search build.mozilla.org mozilla.com mozilla.org nameserver 64.100.127.12 nameserver 64.235.255.10 (I'll also note that after this last reboot, it took loginwindow ~3min to log in over VNC; I've never seen it take so long, but I think the length of time for the box to respond with the Password: prompt for ssh logins has been increasing over time, too :( ) Can IT please have a look at the box and advise? Thanks.
Over to Phong/Justin
Assignee: server-ops → phong
Any update here? It's been three and a half days with no word.
I'm going to MPT tomorrow morning. I will check on it when I get there. Can you send me the username and password for this server?
Flags: colo-trip+
Done.
got it in an email.
switched to NIC 2 and it seems to be working fine now. there might be a problem with the NIC.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
(In reply to comment #6) > switched to NIC 2 and it seems to be working fine now. Thanks, Phong. I have two green builds from the box now, and getting the ssh "Password:" prompt was almost instantaneous again :-) > there might be a problem with the NIC. What sort of follow-up do we need on this?
Status: RESOLVED → VERIFIED
Component: Server Operations: RelEng → RelOps
Product: mozilla.org → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.