Hi folks,
We had a power outage recently which caused our servers to go down 
On rebooting one of our VZ hosts we found that certain containers couldn't be contacted from the network. We can ping the host but not certain containers, and traceroute to the containers stops at the host.
I've checked everything I can think of but without success - I'm hoping someone here can point me in the right direction!
The 'non-contactable' container is meant to use br0 on the host
br0 Link encap:Ethernet HWaddr 00:1B:24:E0:2C:85
inet addr:xxx.xxx.228.254 Bcast:xxx.xxx.228.255 Mask:255.255.255.0
inet6 addr: fe80::21b:24ff:fee0:2c85/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:223594 errors:0 dropped:0 overruns:0 frame:0
TX packets:22508 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:18510460 (17.6 MiB) TX bytes:4597926 (4.3 MiB)
the conf file of the non-contactable container ends with
VE_ROOT="/data/vz/root/$VEID"
VE_PRIVATE="/data/vz/private/$VEID"
OSTEMPLATE="arch-14-07-08"
ORIGIN_SAMPLE="ldapslave"
IP_ADDRESS="xxx.xxx.228.7"
HOSTNAME="dmzldapslave"
NAMESERVER="xxx.xxx.228.14 xxx.xxx.228.2"
SEARCHDOMAIN="xyz.ac.uk"
What is very strange is that other containers on the same host with almost identical configurations work!! For example here's the same part of a working conf for a dns server on the same host
VE_ROOT="/data/vz/root/$VEID"
VE_PRIVATE="/data/vz/private/$VEID"
OSTEMPLATE="arch-14-07-08"
ORIGIN_SAMPLE="externaldns"
IP_ADDRESS="xxx.xxx.228.2"
HOSTNAME="externaldns"
NAMESERVER="xxx.xxx.228.2"
SEARCHDOMAIN="xyz.ac.uk"
I can't figure out why one container works correctly with br0 whilst another with similar configuration doesn't!!! All suggestions gratefully accepted.
TIA
Huw
OpenVZ Forum
Members
Search
Help
Register
Login
Home
