OpenVZ Forum: Support » [solved] Containers not respoding to their ips

Home » General » Support » [solved] Containers not respoding to their ips (network restarted and now containers off)

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

[solved] Containers not respoding to their ips [message #37340]

Thu, 03 September 2009 17:20

dedicados
Messages: 46
Registered: February 2009
Location: Mexico

Member

hi guys, i have a problem, i add more ips to one of the servers, and when i create a new container with that ip, the ip still sending me to the main server.

then i do a network restart and all go off. containers still up and running but cant enter becase all ips still sending me to the main server.

how to fix that??

Quote:

[root@ns ~]# ifconfig
eth0 Link encap:Ethernet HWaddr 00:00:BC:1A:6E:2C
inet addr:2.3.1.8 Bcast:2.3.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:756821 errors:0 dropped:0 overruns:0 frame:0
TX packets:123780 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:54765859 (52.2 MiB) TX bytes:11514941 (10.9 MiB)
Interrupt:177

eth0:0 Link encap:Ethernet HWaddr 00:00:1A:1A:6E:2C
inet addr:6.1.1.8 Bcast:6.1.1.8 Mask:255.255.255.248
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:177
....
MORE
....

eth0:29 Link encap:Ethernet HWaddr 00:00:1A:1A:6E:2C
inet addr:4.3.1.1 Bcast:4.3.1.1 Mask:255.255.255.248
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:177

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:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:560 (560.0 b) TX bytes:560 (560.0 b)

venet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1
RX packets:573 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:37742 (36.8 KiB) TX bytes:0 (0.0 b)

PS change ips for security.

[Updated on: Fri, 04 September 2009 06:36]

Report message to a moderator

Re: Containers not respoding to their ips [message #37342 is a reply to message #37340]

Thu, 03 September 2009 20:12

dedicados
Messages: 46
Registered: February 2009
Location: Mexico

Member

[root@ns]# ifup venet0

Determining IP information for venet0... failed.
[root@ns]#

Report message to a moderator

Re: Containers not respoding to their ips [message #37343 is a reply to message #37340]

Thu, 03 September 2009 20:26

curx
Messages: 739
Registered: February 2006
Location: Nürnberg, Germany

Senior Member

reHi, (follow your pm)

are you trying to give your HardwareNode (ct0) via eth0:X "aliasing" a new ip and in the same way to your container ???
that doesnt work in venet0 , so disconfigure your eth0:29 ( in your example ) and add it only to your container :

# ifdown eth0:29

# vzctl stop <CTID with the IP of eth0:29>
(wait 5min or start manual the vpsnetclean script :
/usr/share/vzctl/scripts/vpsnetclean )

# vzctl start <CTID>
( so the routing and arp entries are setup )

Bye,
Thorsten

Report message to a moderator