OpenVZ Forum


Home » General » Support » [solved] arpsend issue - URGENT
[solved] arpsend issue - URGENT [message #32497] Tue, 12 August 2008 20:17 Go to previous message
Skylar is currently offline  Skylar
Messages: 5
Registered: August 2008
Junior Member
Quote:

[root@lithium ~]# vzctl restart 1520
Restarting VE
Stopping VE ...
VE was stopped
VE is unmounted
Starting VE ...
VE is mounted
Adding IP address(es): 69.162.73.103 69.162.73.105 69.162.73.106 69.162.73.107 69.162.73.108 69.162.73.104
arpsend: 69.162.73.103 is detected on another computer : 00:14:1c:1d:67:80
vps-net_add WARNING: arpsend -c 1 -w 1 -D -e 69.162.73.103 eth1 FAILED
arpsend: 69.162.73.105 is detected on another computer : 00:14:1c:1d:67:80
vps-net_add WARNING: arpsend -c 1 -w 1 -D -e 69.162.73.105 eth1 FAILED
arpsend: 69.162.73.106 is detected on another computer : 00:14:1c:1d:67:80
vps-net_add WARNING: arpsend -c 1 -w 1 -D -e 69.162.73.106 eth1 FAILED
arpsend: 69.162.73.107 is detected on another computer : 00:14:1c:1d:67:80
vps-net_add WARNING: arpsend -c 1 -w 1 -D -e 69.162.73.107 eth1 FAILED
arpsend: 69.162.73.108 is detected on another computer : 00:14:1c:1d:67:80
vps-net_add WARNING: arpsend -c 1 -w 1 -D -e 69.162.73.108 eth1 FAILED
arpsend: 69.162.73.104 is detected on another computer : 00:14:1c:1d:67:80
vps-net_add WARNING: arpsend -c 1 -w 1 -D -e 69.162.73.104 eth1 FAILED
Setting CPU limit: 65
Setting CPU units: 1000
Configure meminfo: 393216
Set hostname: server.xlhost.ws
File resolv.conf was modified
Setting quota ugidlimit: 1000
VE start in progress...


After I do this and try to get into the system, I no longer can as it gives me a fork: out of memory error, and HyperVM shows that the server is in an offline without-memory state.

I had the DC change eth0 and eth1 around, as I was getting an "arpsend WARNING" issue instead of the new "vps-net_add WARNING"

This only happens on my newest machine; all of the other 3 I can make a VPS with the exact same IPs and they work 100% fine; I can reboot without seeing this error

I need this fixed ASAP


Edit: Fairly new system, Centos 5.2 64bit; not sure on the OpenVZ version though, no clue how to check >.<

Edit again: If I remove the IPs from the specified VPS, reboot the VPS; THEN add the IPs then the server works just fine and the IPs work; the VPS only won't work when I try to reboot it.

[Updated on: Tue, 12 August 2008 21:22] by Moderator

Report message to a moderator

 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: reboot inside vps
Next Topic: VE Fails to start with dmesg error "err=-11". 64bit el5 patch.
Goto Forum:
  


Current Time: Wed Jul 24 13:22:36 GMT 2024

Total time taken to generate the page: 0.04338 seconds