Bug#495667: VEs started during the boot can't use network sometimes
Hi Ola, After some testing I can confirm that setting /proc/sys/net/ipv4/conf/eth0/proxy_arp to 1 in /etc/sysctl.conf works for me. Frank On Tue, Nov 18, 2008 at 9:40 PM, Ola Lundqvist [EMAIL PROTECTED] wrote: Hi Frank I have got a workaround for the problem you have. We even have a patch. Could you test if the workaround below works for you? On Tue, Nov 18, 2008 at 07:36:42PM +0300, Kir Kolyshkin wrote: I have created openvz bug http://bugzilla.openvz.org/show_bug.cgi?id=1037 now. Ola, thanks! Looks like we already have a (long standing) bug for this: http://bugzilla.openvz.org/show_bug.cgi?id=556 I am working to have a proper solution. Possible workarounds are: 1. Not to use DHCP for eth0. 2. Set echo 1 /proc/sys/net/ipv4/conf/eth0/proxy_arp (or the same via /etc/sysctl.conf) Best regards, // Ola -- - Ola Lundqvist --- / [EMAIL PROTECTED] Annebergsslingan 37 \ | [EMAIL PROTECTED] 654 65 KARLSTAD | | http://inguza.com/ +46 (0)70-332 1551 | \ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / --- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#495667: VEs started during the boot can't use network sometimes
Thanks. Good to know! // Ola On Fri, Dec 05, 2008 at 06:54:08PM +0100, Frank Bauer wrote: Hi Ola, After some testing I can confirm that setting /proc/sys/net/ipv4/conf/eth0/proxy_arp to 1 in /etc/sysctl.conf works for me. Frank On Tue, Nov 18, 2008 at 9:40 PM, Ola Lundqvist [EMAIL PROTECTED] wrote: Hi Frank I have got a workaround for the problem you have. We even have a patch. Could you test if the workaround below works for you? On Tue, Nov 18, 2008 at 07:36:42PM +0300, Kir Kolyshkin wrote: I have created openvz bug http://bugzilla.openvz.org/show_bug.cgi?id=1037 now. Ola, thanks! Looks like we already have a (long standing) bug for this: http://bugzilla.openvz.org/show_bug.cgi?id=556 I am working to have a proper solution. Possible workarounds are: 1. Not to use DHCP for eth0. 2. Set echo 1 /proc/sys/net/ipv4/conf/eth0/proxy_arp (or the same via /etc/sysctl.conf) Best regards, // Ola -- - Ola Lundqvist --- / [EMAIL PROTECTED] Annebergsslingan 37 \ | [EMAIL PROTECTED] 654 65 KARLSTAD | | http://inguza.com/ +46 (0)70-332 1551 | \ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / --- -- - Ola Lundqvist --- / [EMAIL PROTECTED] Annebergsslingan 37 \ | [EMAIL PROTECTED] 654 65 KARLSTAD | | http://inguza.com/ +46 (0)70-332 1551 | \ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / --- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#495667: VEs started during the boot can't use network sometimes
I have created openvz bug http://bugzilla.openvz.org/show_bug.cgi?id=1037 now. Ola, thanks! Looks like we already have a (long standing) bug for this: http://bugzilla.openvz.org/show_bug.cgi?id=556 I am working to have a proper solution. Possible workarounds are: 1. Not to use DHCP for eth0. 2. Set echo 1 /proc/sys/net/ipv4/conf/eth0/proxy_arp (or the same via /etc/sysctl.conf) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#495667: VEs started during the boot can't use network sometimes
Hi Frank I have got a workaround for the problem you have. We even have a patch. Could you test if the workaround below works for you? On Tue, Nov 18, 2008 at 07:36:42PM +0300, Kir Kolyshkin wrote: I have created openvz bug http://bugzilla.openvz.org/show_bug.cgi?id=1037 now. Ola, thanks! Looks like we already have a (long standing) bug for this: http://bugzilla.openvz.org/show_bug.cgi?id=556 I am working to have a proper solution. Possible workarounds are: 1. Not to use DHCP for eth0. 2. Set echo 1 /proc/sys/net/ipv4/conf/eth0/proxy_arp (or the same via /etc/sysctl.conf) Best regards, // Ola -- - Ola Lundqvist --- / [EMAIL PROTECTED] Annebergsslingan 37 \ | [EMAIL PROTECTED] 654 65 KARLSTAD | | http://inguza.com/ +46 (0)70-332 1551 | \ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / --- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#495667: VEs started during the boot can't use network sometimes
Hi I have created openvz bug http://bugzilla.openvz.org/show_bug.cgi?id=1037 now. // Ola On Tue, Aug 19, 2008 at 04:58:43PM +0200, Frank Bauer wrote: Package: vzctl Hi, I'm running stock i386 lenny with current -openvz kernel from unstable. Everything runs fine, except the VEs that are started during the boot. Sometimes they can't use the network, as if ip_forwarding is not active, Which is not the case, I have the following in /etc/sysctl.conf: net.ipv4.ip_forward=1 I can fix this by restarting the VEs - after that the networking works ok. I believe this might be a race condition like starting OpenVZ before the ip_forwarding feature is set, because it only happens with VEs stared during the boot: 1) When I start VE manually (i.e. some time after the boot), networking works. 2) When I restart VE, networking works. 3) When I let the rc script to start VE, I have like 50% chance networking will not work. Kind Regards Frank -- - Ola Lundqvist --- / [EMAIL PROTECTED] Annebergsslingan 37 \ | [EMAIL PROTECTED] 654 65 KARLSTAD | | http://inguza.com/ +46 (0)70-332 1551 | \ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / --- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#495667: VEs started during the boot can't use network sometimes
On Tue, Aug 19, 2008 at 7:20 PM, Ola Lundqvist [EMAIL PROTECTED] wrote: On Tue, Aug 19, 2008 at 04:58:43PM +0200, Frank Bauer wrote: Sometimes they can't use the network, as if ip_forwarding is not active, Which is not the case, I have the following in /etc/sysctl.conf: net.ipv4.ip_forward=1 Can you check if this is active as well after the restart? Yes, it is active. But I found out it has nothing to do with my problem. I can fix this by restarting the VEs - after that the networking works ok. I believe this might be a race condition like starting OpenVZ before the ip_forwarding feature is set, because it only happens with VEs stared during the boot: I do not think so, as it should affect others as well, but it could of course be the case. If it is a race condition then it is likely to be a problem in the network script. The reason is that there is a pre-condition for vzctl start. # required-start: $network $remote_fs $local_fs sshd # required-stop: I've been gathering tangible data during the past week (hence the delay) and the result seems clear: OpenVZ guests have problem with networking if they are started before the host gets IP address via DHCP. In most cases, the address is assigned before VEs start, so the networking in VEs work: kernel: [ 19.394677] skge eth0: enabling interface dhclient: Listening on LPF/eth0/00:14:85:39:ec:b8 dhclient: Sending on LPF/eth0/00:14:85:39:ec:b8 dhclient: Sending on Socket/fallback kernel: [ 21.080002] skge eth0: Link is up at 100 Mbps, full duplex, flow control both kernel: [ 22.153482] NET: Registered protocol family 10 kernel: [ 22.457495] ip_tables: (C) 2000-2006 Netfilter Core Team dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8 dhclient: DHCPOFFER from 192.168.3.1 dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67 dhclient: DHCPACK from 192.168.3.1 dhclient: bound to 192.168.3.75 -- renewal in 42254 seconds. kernel: [ 23.828058] warning: `vzctl' uses 32-bit capabilities (legacy support in use) kernel: [ 23.851517] CT: 100: started avahi-daemon[2570]: Found user 'avahi' (UID 104) and group 'avahi' (GID 111). Sometimes the DHCP client / server is a bit slower and VEs start before the host is assigned the IP address - networking in VEs does not work: kernel: [ 18.154081] skge eth0: enabling interface dhclient: Listening on LPF/eth0/00:14:85:39:ec:b8 dhclient: Sending on LPF/eth0/00:14:85:39:ec:b8 dhclient: Sending on Socket/fallback kernel: [ 19.847303] skge eth0: Link is up at 100 Mbps, full duplex, flow control both kernel: [ 21.395844] NET: Registered protocol family 10 kernel: [ 21.708122] ip_tables: (C) 2000-2006 Netfilter Core Team kernel: [ 23.008013] warning: `vzctl' uses 32-bit capabilities (legacy support in use) kernel: [ 23.069600] CT: 100: started dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4 dhclient: DHCPOFFER from 192.168.3.1 dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67 dhclient: DHCPACK from 192.168.3.1 dhclient: bound to 192.168.3.75 -- renewal in 32585 seconds. avahi-daemon[2858]: Found user 'avahi' (UID 104) and group 'avahi' (GID 111). Kind Regards, Frank -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#495667: VEs started during the boot can't use network sometimes
Hi Frank I think the DHCP is the problem here. I assume that the networking script actually terminate before the IP address has been fetched. In order to solve this we need to have some extra syncronisation between the dhcp and the virtual host. I would not recommend to use DHCP in combinations with virtual servers as if the IP address change it will most likely not be handled properly. My suggestion is that you either add a long sleep in the init script or help me to write a syncronisation thing. I'm not fully sure how this should be implemented in order to cover all this kind of problems. It needs to be configurable and rather flexible. However maybe this should be documented in the README file. Best regards, // Ola On Fri, Aug 29, 2008 at 06:21:31PM +0200, Frank Bauer wrote: On Tue, Aug 19, 2008 at 7:20 PM, Ola Lundqvist [EMAIL PROTECTED] wrote: On Tue, Aug 19, 2008 at 04:58:43PM +0200, Frank Bauer wrote: Sometimes they can't use the network, as if ip_forwarding is not active, Which is not the case, I have the following in /etc/sysctl.conf: net.ipv4.ip_forward=1 Can you check if this is active as well after the restart? Yes, it is active. But I found out it has nothing to do with my problem. I can fix this by restarting the VEs - after that the networking works ok. I believe this might be a race condition like starting OpenVZ before the ip_forwarding feature is set, because it only happens with VEs stared during the boot: I do not think so, as it should affect others as well, but it could of course be the case. If it is a race condition then it is likely to be a problem in the network script. The reason is that there is a pre-condition for vzctl start. # required-start: $network $remote_fs $local_fs sshd # required-stop: I've been gathering tangible data during the past week (hence the delay) and the result seems clear: OpenVZ guests have problem with networking if they are started before the host gets IP address via DHCP. In most cases, the address is assigned before VEs start, so the networking in VEs work: kernel: [ 19.394677] skge eth0: enabling interface dhclient: Listening on LPF/eth0/00:14:85:39:ec:b8 dhclient: Sending on LPF/eth0/00:14:85:39:ec:b8 dhclient: Sending on Socket/fallback kernel: [ 21.080002] skge eth0: Link is up at 100 Mbps, full duplex, flow control both kernel: [ 22.153482] NET: Registered protocol family 10 kernel: [ 22.457495] ip_tables: (C) 2000-2006 Netfilter Core Team dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8 dhclient: DHCPOFFER from 192.168.3.1 dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67 dhclient: DHCPACK from 192.168.3.1 dhclient: bound to 192.168.3.75 -- renewal in 42254 seconds. kernel: [ 23.828058] warning: `vzctl' uses 32-bit capabilities (legacy support in use) kernel: [ 23.851517] CT: 100: started avahi-daemon[2570]: Found user 'avahi' (UID 104) and group 'avahi' (GID 111). Sometimes the DHCP client / server is a bit slower and VEs start before the host is assigned the IP address - networking in VEs does not work: kernel: [ 18.154081] skge eth0: enabling interface dhclient: Listening on LPF/eth0/00:14:85:39:ec:b8 dhclient: Sending on LPF/eth0/00:14:85:39:ec:b8 dhclient: Sending on Socket/fallback kernel: [ 19.847303] skge eth0: Link is up at 100 Mbps, full duplex, flow control both kernel: [ 21.395844] NET: Registered protocol family 10 kernel: [ 21.708122] ip_tables: (C) 2000-2006 Netfilter Core Team kernel: [ 23.008013] warning: `vzctl' uses 32-bit capabilities (legacy support in use) kernel: [ 23.069600] CT: 100: started dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4 dhclient: DHCPOFFER from 192.168.3.1 dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67 dhclient: DHCPACK from 192.168.3.1 dhclient: bound to 192.168.3.75 -- renewal in 32585 seconds. avahi-daemon[2858]: Found user 'avahi' (UID 104) and group 'avahi' (GID 111). Kind Regards, Frank -- --- Inguza Technology AB --- MSc in Information Technology / [EMAIL PROTECTED]Annebergsslingan 37\ | [EMAIL PROTECTED] 654 65 KARLSTAD| | http://inguza.com/Mobile: +46 (0)70-332 1551 | \ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / --- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#495667: VEs started during the boot can't use network sometimes
Package: vzctl Hi, I'm running stock i386 lenny with current -openvz kernel from unstable. Everything runs fine, except the VEs that are started during the boot. Sometimes they can't use the network, as if ip_forwarding is not active, Which is not the case, I have the following in /etc/sysctl.conf: net.ipv4.ip_forward=1 I can fix this by restarting the VEs - after that the networking works ok. I believe this might be a race condition like starting OpenVZ before the ip_forwarding feature is set, because it only happens with VEs stared during the boot: 1) When I start VE manually (i.e. some time after the boot), networking works. 2) When I restart VE, networking works. 3) When I let the rc script to start VE, I have like 50% chance networking will not work. Kind Regards Frank -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#495667: VEs started during the boot can't use network sometimes
Hi Frank On Tue, Aug 19, 2008 at 04:58:43PM +0200, Frank Bauer wrote: Package: vzctl Hi, I'm running stock i386 lenny with current -openvz kernel from unstable. Everything runs fine, except the VEs that are started during the boot. Sometimes they can't use the network, as if ip_forwarding is not active, Which is not the case, I have the following in /etc/sysctl.conf: net.ipv4.ip_forward=1 Can you check if this is active as well after the restart? I can fix this by restarting the VEs - after that the networking works ok. I believe this might be a race condition like starting OpenVZ before the ip_forwarding feature is set, because it only happens with VEs stared during the boot: I do not think so, as it should affect others as well, but it could of course be the case. If it is a race condition then it is likely to be a problem in the network script. The reason is that there is a pre-condition for vzctl start. # required-start: $network $remote_fs $local_fs sshd # required-stop: Can you verify this by adding a long sleep in the beginning of the vzctl init script? 1) When I start VE manually (i.e. some time after the boot), networking works. 2) When I restart VE, networking works. 3) When I let the rc script to start VE, I have like 50% chance networking will not work. Best regards, // Ola Kind Regards Frank -- - Ola Lundqvist --- / [EMAIL PROTECTED] Annebergsslingan 37 \ | [EMAIL PROTECTED] 654 65 KARLSTAD | | http://inguza.com/ +46 (0)70-332 1551 | \ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / --- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
