Hi Guys,
When in Cloudmin and I select one of my down Physical XEN Hosts from the drop down then click the Start Up System, I receive the following message:
Starting up 10.1.10.15 ..
.. started but a problem was detected : System did not respond to ping after 60 seconds. Perhaps wake-on-LAN is not supported by the BIOS or a network card?
I have verified that WOL = G (Magic Packet) and am able to from the same host that is my master cloudmin server run wol macaddress and the system starts right up.
The server is a quad opteron and takes a minute or two to boot, is the 60 second startup timeout configurable.
I actually tracked down where this is happening and found that if I removed the -i $ip from the line in real-type-lib.pl things worked great.
#New working
my $out = &backquote_logged("$cmd ".quotemeta($m).
" 2>&1 </dev/null");
#Orig not working
#my $out = &backquote_logged("$cmd -i $ip ".quotemeta($m).
# " 2>&1 </dev/null");
Not sure why this would be an issue with Centos, I verified this manually too. At least this is an issue with the NICs in several of my servers :
lspci :
03:06.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet (rev 10)
ethtool peth0
Settings for peth0:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Advertised auto-negotiation: Yes
Speed: 1000Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 1
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: g
Wake-on: g
Current message level: 0x000000ff (255)
Link detected: yes
cat /etc/redhat-release
CentOS release 5.6 (Final)
uname -a
Linux gx5.xtsuniverse.local 2.6.18-238.19.1.el5xen #1 SMP Fri Jul 15 08:16:59 EDT 2011 x86_64 x86_64 x86_64 GNU/Linux
Have you experienced this with centos 5.6 XEN hosts?
~Jeremy
Comments
Submitted by JamieCameron on Tue, 09/20/2011 - 23:12 Comment #1
I haven't run into this issue, but I suspect that it depends on your network and BIOS settings. In the next Cloudmin release (5.9) I will have it send the WOL packet with and without the system's IP, to cover both cases.
Also, I will make the ping timeout configurable, instead of always being 60 seconds.
Submitted by xtremeservices on Wed, 09/21/2011 - 00:14 Comment #2
Great thx!
~Jeremy
Submitted by Issues on Wed, 10/05/2011 - 01:22 Comment #3
Automatically closed -- issue fixed for 2 weeks with no activity.