Closed
Bug 770458
Opened 13 years ago
Closed 13 years ago
sea-vm-linux64-1 was rebooted but now encounters "some other host already uses that IP address"
Categories
(Infrastructure & Operations :: Virtualization, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: ewong, Unassigned)
References
Details
Had some problems connecting to sea-vm-linux64-1 from the sea-master1 on
scl3. Since it's part of a SCL3 ESX Cluster, I have no idea which vm it
is. Ashish rebooted the vm for us, but now we encountered a "some other
host already uses that IP address" error.
Can someone have a look at it and get the ip straightened out?
Thanks
Comment 1•13 years ago
|
||
I don't see *any* host at that IP right now, so I can't do much to figure out which is squatting there:
? (63.245.223.96) at <incomplete> on eth0
I think I need some more data - where did that error occur? If it can't assign an IP, how'd you get into the host to see the error?
Comment 2•13 years ago
|
||
(In reply to Dustin J. Mitchell [:dustin] from comment #1)
> I think I need some more data - where did that error occur? If it can't
> assign an IP, how'd you get into the host to see the error?
I had consoled in via vcentre and saw the message during bootup.
Comment 3•13 years ago
|
||
This had
NAME=eth0
instead of
DEVICE=eth0
in the ifcfg-eth0 script. So it passed an empty string to a bunch of commands, they failed, and it made incorrect assumptions. Fixed now.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: mozilla.org → Infrastructure & Operations
You need to log in
before you can comment on or make changes to this bug.
Description
•