| VE IP address stops working after several hours [message #33017] |
Wed, 17 September 2008 17:55  |
fatbrother
Messages: 12
Registered: September 2008
Location: Novosibirsk, Russia
|
Junior Member |
|
|
I have Debian Etch system with FZA OpenVZ kernel:
root@olympic:~# uname -a
Linux olympic 2.6.18-fza-028stab053.5-amd64 #1 SMP Sat Mar 1 19:50:43 UTC 2008 x86_64 GNU/Linux
root@olympic:~# vzctl --version
vzctl version 3.0.22-1dso1
HN connected to two VLANs:
eth0 Link encap:Ethernet HWaddr xxx
inet addr:10.4.0.97 Bcast:10.4.0.127 Mask:255.255.255.224
eth0.425 Link encap:Ethernet HWaddr xxx
inet addr:real_ip1 Bcast:real_ip_network Mask:255.255.255.240
Default router is eth0, source routing is set for real_ip_network to eth0.425.
VE4 has two IP addresses added by vzctl set 4 --ipadd. 10.4.0.104 and real_ip2
After I boot VE4 both IP addresses are accessible, so the routing and ARP proxy seem to be correct. But when VE4 runs for several hours, real_ip2 stops working. VE4 is still accessible via 10.4.0.104 and real_ip2 is pingable from HN, but not from outside.
When real_ip2 fails, record
real_ip2 * <from_interface> MP eth0.425
is present in ARP table, and HN real_ip1 is still accessible, but tcpdump shows that HN stops answering ARP requests for real_ip2.
VE4 restart or vzctl set 4 --ipdel real_ip2; vzctl set 4 --ipadd real_ip2; clear the condition: real_ip2 starts responding again, but after several hours it stops responding again, etc.
It runs for at least 3 hours, but no longer than 5 hours. Sorry, cannot get more precise estimate yet, and I'm not even sure that time is constant.
I found no specific external events and no log records that could be related to this. It just runs and then stops running for no visible reason.
[Updated on: Wed, 17 September 2008 20:27] Report message to a moderator |
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
