OpenVZ Forum


Home » General » Support » Problem with starting Debian* and Ubuntu* network => vzctl 3.0.26
Problem with starting Debian* and Ubuntu* network => vzctl 3.0.26 [message #42100] Mon, 28 February 2011 19:12 Go to next message
hack is currently offline  hack
Messages: 6
Registered: February 2011
Location: hjfg
Junior Member
Hi, i download 
debian-6.0-i386-minimal.tar.gz (signature) 	2011-02-18 01:54:43 	74 Mb and amd64

and after start container looks like network not up correctly, can not ping in/out.

/var/log/vzctl.log:
2011-02-28T20:00:08+0100 vzctl : CT 146 : Creating container private area (debian-6.0-amd64-minimal)
2011-02-28T20:00:12+0100 vzctl : CT 146 : Performing postcreate actions
2011-02-28T20:00:12+0100 vzctl : CT 146 : Container private area was created
2011-02-28T20:00:12+0100 vzctl : CT 146 : Restarting container
2011-02-28T20:00:12+0100 vzctl : CT 146 : Starting container ...
2011-02-28T20:00:12+0100 vzctl : CT 146 : Container is mounted
2011-02-28T20:00:12+0100 vzctl : CT 146 : Setting CPU units: 1000
2011-02-28T20:00:12+0100 vzctl : CT 146 : Container start in progress...
2011-02-28T20:00:13+0100 vzctl : CT 146 : Adding IP address(es): 178.33.130.-
2011-02-28T20:00:13+0100 vzctl : CT 146 : Saved parameters for CT 146
2011-02-28T20:00:13+0100 vzctl : CT 146 : Set hostname: 3test.pl
2011-02-28T20:00:13+0100 vzctl : CT 146 : File resolv.conf was modified
2011-02-28T20:00:13+0100 vzctl : CT 146 : Saved parameters for CT 146
2011-02-28T20:00:13+0100 vzctl : CT 146 : UB limits were set successfully
2011-02-28T20:00:13+0100 vzctl : CT 146 : Saved parameters for CT 146
2011-02-28T20:00:13+0100 vzctl : CT 146 : UB limits were set successfully
2011-02-28T20:00:13+0100 vzctl : CT 146 : Saved parameters for CT 146
2011-02-28T20:00:13+0100 vzctl : CT 146 : Saved parameters for CT 146
2011-02-28T20:00:13+0100 vzctl : CT 146 : Saved parameters for CT 146
2011-02-28T20:00:13+0100 vzctl : CT 146 : Unable to turn on second-level disk quota on a running container
2011-02-28T20:00:13+0100 vzctl : CT 146 : WARNING: Some of the parameters could not be applied to a running container.
	Please consider using --setmode option
2011-02-28T20:00:13+0100 vzctl : CT 146 : Setting quota ugidlimit: 10000
2011-02-28T20:00:13+0100 vzctl : CT 146 : Unable to apply new quota values: ugid quota not initialized
2011-02-28T20:00:13+0100 vzctl : CT 146 : Saved parameters for CT 146
2011-02-28T20:00:13+0100 vzctl : CT 146 : UB limits were set successfully
2011-02-28T20:00:13+0100 vzctl : CT 146 : Setting CPU limit: 55
2011-02-28T20:00:13+0100 vzctl : CT 146 : Setting CPU units: 1000
2011-02-28T20:00:13+0100 vzctl : CT 146 : Setting CPUs: 1
2011-02-28T20:00:13+0100 vzctl : CT 146 : Saved parameters for CT 146
2011-02-28T20:00:13+0100 vzctl : CT 146 : Restarting container
2011-02-28T20:00:13+0100 vzctl : CT 146 : Stopping container ...
2011-02-28T20:00:18+0100 vzctl : CT 146 : Container was stopped
2011-02-28T20:00:18+0100 vzctl : CT 146 : Container is unmounted
2011-02-28T20:00:18+0100 vzctl : CT 146 : Starting container ...
2011-02-28T20:00:18+0100 vzctl : CT 146 : Container is mounted
2011-02-28T20:00:18+0100 vzctl : CT 146 : Adding IP address(es): 178.33.130.-
2011-02-28T20:00:18+0100 vzctl : CT 146 : Setting CPU limit: 55
2011-02-28T20:00:18+0100 vzctl : CT 146 : Setting CPU units: 1000
2011-02-28T20:00:18+0100 vzctl : CT 146 : Setting CPUs: 1
2011-02-28T20:00:18+0100 vzctl : CT 146 : Set hostname: 3test.pl
2011-02-28T20:00:18+0100 vzctl : CT 146 : File resolv.conf was modified
2011-02-28T20:00:18+0100 vzctl : CT 146 : Setting quota ugidlimit: 10000
2011-02-28T20:00:18+0100 vzctl : CT 146 : Container start in progress...
2011-02-28T20:00:18+0100 vzctl : CT 146 : Adding IP address(es): 2001:41d0:2:865c::d4d0:7eda
2011-02-28T20:00:18+0100 vzctl : CT 146 : Saved parameters for CT 146
2011-02-28T20:00:18+0100 vzctl : CT 146 : Adding IP address(es): 2001:41d0:2:865c::d7f0:7b9c
2011-02-28T20:00:18+0100 vzctl : CT 146 : Saved parameters for CT 146
2011-02-28T20:00:18+0100 vzctl : CT 146 : Adding IP address(es): 2001:41d0:2:865c::6f1f:2a8
2011-02-28T20:00:19+0100 vzctl : CT 146 : Saved parameters for CT 146
2011-02-28T20:00:19+0100 vzctl : CT 146 : Adding IP address(es): 2001:41d0:2:865c::73ef:93b
2011-02-28T20:00:19+0100 vzctl : CT 146 : Saved parameters for CT 146
2011-02-28T20:00:19+0100 vzctl : CT 146 : Adding IP address(es): 2001:41d0:2:865c::da82:e96b
2011-02-28T20:00:19+0100 vzctl : CT 146 : Saved parameters for CT 146
2011-02-28T20:00:19+0100 vzctl : CT 146 : Adding IP address(es): 2001:41d0:2:865c::ed80:cbc1
2011-02-28T20:00:19+0100 vzctl : CT 146 : Saved parameters for CT 146
2011-02-28T20:00:19+0100 vzctl : CT 146 : Adding IP address(es): 2001:41d0:2:865c::28b3:8902
2011-02-28T20:00:19+0100 vzctl : CT 146 : Saved parameters for CT 146
2011-02-28T20:00:19+0100 vzctl : CT 146 : Adding IP address(es): 2001:41d0:2:865c::e69d:a19
2011-02-28T20:00:19+0100 vzctl : CT 146 : Saved parameters for CT 146
2011-02-28T20:01:13+0100 vzeventd : Child 6939 failed with exit code 79

kernel:
2.6.18-194.26.1.el5.028stab079.2

vzctl: vzctl version 3.0.26
[/code]
Im using SolusVM. Have someone this issue too? How can i fix thi?
Thanks for any replays.

[Updated on: Tue, 01 March 2011 11:53]

Report message to a moderator

Re: Problem with starting Debian 6 (2011-02-18) [message #42101 is a reply to message #42100] Mon, 28 February 2011 19:26 Go to previous messageGo to next message
curx
Messages: 739
Registered: February 2006
Location: Nürnberg, Germany
Senior Member
Hi,

please give some infos:

* test the ping via IPv4, IPv6 or both ?
* can you ping the ct from hostnode IPv4 / IPv6 ?
* any ip(6)tables rules active ?

in this debian 6.0 container:

# ip -4 a l ; ip -4 r l ; ip -6 a ; ip -6 r l in ct
# /etc/init.d/networking restart ... ok, errors ?
# cat /etc/network/interfaces

Bye,
Thorsten

Report message to a moderator

Re: Problem with starting Debian 6 (2011-02-18) [message #42103 is a reply to message #42101] Mon, 28 February 2011 21:52 Go to previous messageGo to next message
hack is currently offline  hack
Messages: 6
Registered: February 2011
Location: hjfg
Junior Member
[root@vps ~]# vzctl enter 144
entered into CT 144
root@1:/# ping google.com
ping: unknown host google.com


root@1:/# ifconfig
lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

venet0    Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
       [b]inet6 addr: 2001:41d0:2:865c::9b23:ae15/0 Scope:Global[/b]
          UP BROADCAST POINTOPOINT RUNNING NOARP  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

venet0:0  Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          inet addr:178.33.130.-  P-t-P:178.33.130.-  Bcast:0.0.0.0  Mask:255.255.255.255
          UP BROADCAST POINTOPOINT RUNNING NOARP  MTU:1500  Metric:1


root@1:/# /etc/init.d/networking start
Configuring network interfaces...SIOCSIFADDR: File exists
Failed to bring up venet0.
done.


root@1:/# ping google.com
PING google.com (74.125.230.81) 56(84) bytes of data.
64 bytes from 74.125.230.81: icmp_req=1 ttl=55 time=6.30 ms
64 bytes from 74.125.230.81: icmp_req=2 ttl=55 time=5.53 ms
64 bytes from 74.125.230.81: icmp_req=3 ttl=55 time=4.75 ms
64 bytes from 74.125.230.81: icmp_req=4 ttl=55 time=4.97 ms
64 bytes from 74.125.230.81: icmp_req=5 ttl=55 time=4.60 ms

--- google.com ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 3999ms
rtt min/avg/max/mdev = 4.602/5.233/6.303/0.621 ms



root@1:/# ifconfig
lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

venet0    Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
       [b]inet6 addr: 2001:41d0:2:865c::d5f6:d3f/0 Scope:Global
          inet6 addr: 2001:41d0:2:865c::5d86:3576/0 Scope:Global
          inet6 addr: 2001:41d0:2:865c::cbf4:fb92/0 Scope:Global
          inet6 addr: 2001:41d0:2:865c::9b23:ae15/0 Scope:Global
          inet6 addr: 2001:41d0:2:865c::d24f:cdfe/0 Scope:Global
          inet6 addr: 2001:41d0:2:865c::68ea:a63/0 Scope:Global
          inet6 addr: 2001:41d0:2:865c::3857:d93b/0 Scope:Global
          inet6 addr: 2001:41d0:2:865c::9829:1d5f/0 Scope:Global[/b]
          UP BROADCAST POINTOPOINT RUNNING NOARP  MTU:1500  Metric:1
          RX packets:11 errors:0 dropped:0 overruns:0 frame:0
          TX packets:11 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1216 (1.1 KiB)  TX bytes:836 (836.0 B)

venet0:0  Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          inet addr:178.33.130.-  P-t-P:178.33.130.-  Bcast:0.0.0.0  Mask:255.255.255.255
          UP BROADCAST POINTOPOINT RUNNING NOARP  MTU:1500  Metric:1


After start networking is ok, but after reboot container problem is back. SolusVM template is adding 8 ipv6 addresses for each container, but u can see on first 'ifconfig' is only 1 IPv6 added, and after start networking all 8.

* test the ping via IPv4, IPv6 or both ? - no replay
* can you ping the ct from hostnode IPv4 / IPv6 ? - no replay
* any ip(6)tables rules active ? - no additional rules


Before fix (start networking):

root@1:/# ping google.com
ping: unknown host google.com

root@1:/# ip -4 a l
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
    inet 127.0.0.1/8 scope host lo
3: venet0: <BROADCAST,POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN
    inet 178.33.130.226/32 scope global venet0:0
root@1:/# ip -4 r l
root@1:/# ip -6 a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
root@1:/# ip -6 r l



root@1:/# cat /etc/network/interfaces
# This configuration file is auto-generated.
# WARNING: Do not edit this file, your changes will be lost.
# Please create/edit /etc/network/interfaces.head and /etc/network/interfaces.tail instead,
# their contents will be inserted at the beginning and at the end
# of this file, respectively.
#
# NOTE: it is NOT guaranteed that the contents of /etc/network/interfaces.tail
# will be at the very end of this file.

# Auto generated lo interface
auto lo
iface lo inet loopback

# Auto generated venet0 interface
auto venet0
iface venet0 inet manual
        up ifconfig venet0 up
        up route add default dev venet0
        down route del default dev venet0
        down ifconfig venet0 down


iface venet0 inet6 manual
        up ifconfig venet0 add 2001:41d0:2:865c::3857:d93b/0
        down ifconfig venet0 del 2001:41d0:2:865c::3857:d93b/0
        up ifconfig venet0 add 2001:41d0:2:865c::cbf4:fb92/0
        down ifconfig venet0 del 2001:41d0:2:865c::cbf4:fb92/0
        up ifconfig venet0 add 2001:41d0:2:865c::d5f6:d3f/0
        down ifconfig venet0 del 2001:41d0:2:865c::d5f6:d3f/0
        up ifconfig venet0 add 2001:41d0:2:865c::68ea:a63/0
        down ifconfig venet0 del 2001:41d0:2:865c::68ea:a63/0
        up ifconfig venet0 add 2001:41d0:2:865c::d24f:cdfe/0
        down ifconfig venet0 del 2001:41d0:2:865c::d24f:cdfe/0
        up ifconfig venet0 add 2001:41d0:2:865c::9829:1d5f/0
        down ifconfig venet0 del 2001:41d0:2:865c::9829:1d5f/0
        up ifconfig venet0 add 2001:41d0:2:865c::5d86:3576/0
        down ifconfig venet0 del 2001:41d0:2:865c::5d86:3576/0
        up ifconfig venet0 add 2001:41d0:2:865c::9b23:ae15/0
        down ifconfig venet0 del 2001:41d0:2:865c::9b23:ae15/0

auto venet0:0
iface venet0:0 inet static
        address 178.33.130.226
        netmask 255.255.255.255

root@1:/#

[Updated on: Mon, 28 February 2011 22:10]

Report message to a moderator

Re: Problem with starting Debian 6 (2011-02-18) [message #42104 is a reply to message #42100] Mon, 28 February 2011 22:03 Go to previous messageGo to next message
KriS83 is currently offline  KriS83
Messages: 12
Registered: October 2005
Junior Member
Hi,

I had the same issue today.
I backported the files from /etc/vz/dists/scripts/debian* from vzctl 3.0.25.2 and everything worked fine again.

The problem is, that you have no route set within the container.

Check it with "route -n"

Regards,
KriS

Report message to a moderator

Re: Problem with starting Debian 6 (2011-02-18) [message #42105 is a reply to message #42104] Mon, 28 February 2011 22:14 Go to previous messageGo to next message
hack is currently offline  hack
Messages: 6
Registered: February 2011
Location: hjfg
Junior Member
U right Kris.

root@1:/# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
root@1:/#


After replacing /etc/vz/scripts/debian* from 3.0.26 to 3.0.25.2 IPv4 work great, but IPv6 network is down. No IPv6 on 'ifconfig' Sad

[Updated on: Mon, 28 February 2011 22:27]

Report message to a moderator

Re: Problem with starting Debian 6 (2011-02-18) [message #42106 is a reply to message #42100] Mon, 28 February 2011 22:29 Go to previous messageGo to next message
KriS83 is currently offline  KriS83
Messages: 12
Registered: October 2005
Junior Member
Hi,

just try the following, maybe it will help:

Open /etc/network/interfaces inside your CT and replace:

# Auto generated venet0 interface
auto venet0
iface venet0 inet manual
        up ifconfig venet0 up
        up route add default dev venet0
        down route del default dev venet0
        down ifconfig venet0 down


with the "old"
# Auto generated venet0 interface
auto venet0
iface venet0 inet static
	address 127.0.0.1
	netmask 255.255.255.255
	broadcast 0.0.0.0
	up route add default dev venet0


Then just try restarting your network:

# /etc/init.d/networking restart

Check if that works?

Thanks
KriS

Edit: Sorry don't use IPv6 yet, so can't help with that one.

[Updated on: Mon, 28 February 2011 22:30]

Report message to a moderator

Re: Problem with starting Debian 6 (2011-02-18) [message #42107 is a reply to message #42106] Mon, 28 February 2011 22:41 Go to previous messageGo to next message
hack is currently offline  hack
Messages: 6
Registered: February 2011
Location: hjfg
Junior Member
So, the problem is not with Debian 6, but vzctl 3.0.26 (i updated today). I building ct with Debian 5 and Ubuntu 10.10 and I have the same issue... I will do more tests...

[Updated on: Mon, 28 February 2011 22:47]

Report message to a moderator

Re: Problem with starting Debian 6 (2011-02-18) [message #42108 is a reply to message #42100] Mon, 28 February 2011 22:45 Go to previous messageGo to next message
KriS83 is currently offline  KriS83
Messages: 12
Registered: October 2005
Junior Member
Hi,

yes as I said I had the same issue.
I had setup a fresh node and started migrating CTs.
On the new node the CTs were suddely no longer available.

Backporting the mentioned files had helped me, as I didn't have a lot of time to actually debug the issue I was satisfied with the solution for today Smile

I also will be setting up another node again tomorrow and start investigating.

Regards
KriS

Report message to a moderator

Re: Problem with starting Debian 6 (2011-02-18) [message #42113 is a reply to message #42108] Tue, 01 March 2011 11:46 Go to previous messageGo to next message
curx
Messages: 739
Registered: February 2006
Location: Nürnberg, Germany
Senior Member
http://bugzilla.openvz.org/show_bug.cgi?id=1792

Report message to a moderator

Re: Problem with starting Debian* and Ubuntu* network => vzctl 3.0.26 [message #42118 is a reply to message #42100] Wed, 02 March 2011 01:51 Go to previous message
kir is currently offline  kir
Messages: 1645
Registered: August 2005
Location: Moscow, Russia
Senior Member
Fixed in vzctl 3.0.26.1

http://wiki.openvz.org/Download/vzctl/3.0.26.1
http://openvz.org/pipermail/announce/2011-March/000193.html

Kir Kolyshkin
http://static.openvz.org/userbars/openvz-developer.png

Report message to a moderator

Previous Topic: How to mount second drive
Next Topic: network troubles
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Fri Dec 01 19:21:21 GMT 2023

Total time taken to generate the page: 0.05519 seconds
Powered by FUDforum Powered by Virtuozzo Containers