OpenVZ Forum


Home » General » Support » Cannot start VE: waiting for lo to become free
Cannot start VE: waiting for lo to become free [message #42441] Mon, 18 April 2011 15:09 Go to next message
rvanlooijen is currently offline  rvanlooijen
Messages: 4
Registered: October 2010
Junior Member
Hi all,

we've been running OpenVZ containers on numerous hosts in combination with DRBD for some time now, but run into an issue while trying to an auto-failover setup to work. When I (manually or from hearbeat) try to start a clean VE, the systems starts logging:

Message from syslogd@**** at Apr 18 17:01:01 ...
kernel:[ 1171.526494] unregister_netdevice: waiting for lo to become free. Usage count = 2

The message just keeps appearing and the VE never starts. I cannot even kill vzctl anymore. We haven't seen this in our other setups, can this be caused by heartbeat?

As long as I do not start the VE (onboot=no), heartbeat + drbd + openvz functions perfectly.

Some more info:

Linux ******** 2.6.26-2-openvz-amd64 #1 SMP Tue Jan 25 06:04:33 UTC 2011 x86_64 GNU/Linux

vzctl Version: 3.0.22-14

I'll paste my relevant config files below as well. If you need more info, please do ask.

Kind regards,

Richard van Looijen


drbd.conf
global {
usage-count no;
}

common {
syncer {
rate 100M;
}
}

resource r0 {
protocol C;

handlers {
pri-on-incon-degr "echo o > /proc/sysrq-trigger ; halt -f";
pri-lost-after-sb "echo o > /proc/sysrq-trigger ; halt -f";
local-io-error "echo o > /proc/sysrq-trigger ; halt -f";
outdate-peer "/usr/lib/heartbeat/drbd-peer-outdater -t 5";
pri-lost "echo pri-lost. Have a look at the log files. | mail -s 'DRBD Alert' root";
split-brain "echo split-brain. drbdadm -- --discard-my-data connect $DRBD_RESOURCE ? | mail -s 'DRBD Alert' root";
}

startup {
wfc-timeout 0;
degr-wfc-timeout 60;
# become-primary-on both;
}

disk {
on-io-error detach;
}

net {
# allow-two-primaries;
cram-hmac-alg "sha1";
shared-secret "*****";
after-sb-0pri discard-younger-primary;
after-sb-1pri discard-secondary;
after-sb-2pri disconnect;
rr-conflict call-pri-lost;
}

syncer {
rate 100M;
al-extents 257;
}

on **** {
device /dev/drbd0;
disk /dev/md3;
address 10.0.0.1:7788;
flexible-meta-disk internal;
}

on **** {
device /dev/drbd0;
disk /dev/md3;
address 10.0.0.2:7788;
meta-disk internal;
}
}


ha.cf
# Heartbeat logging configuration
logfacility daemon

# Heartbeat cluster members
node ****
node ****

# Heartbeat communication timing
keepalive 1
warntime 10
deadtime 30
initdead 60

# Heartbeat communication paths
udpport 694
ucast eth0 10.0.0.1
ucast eth0 10.0.0.2

# Don't fail back automatically
auto_failback off

# Monitoring of network connection to default gateway
ping 10.0.0.1
respawn hacluster /usr/lib64/heartbeat/ipfail

haresources
**** drbddisk::r0 Filesystem::/dev/drbd0::/vz::ext3 vz MailTo::****

[Updated on: Mon, 18 April 2011 15:12]

Report message to a moderator

Re: Cannot start VE: waiting for lo to become free [message #42453 is a reply to message #42441] Tue, 19 April 2011 09:39 Go to previous message
rvanlooijen is currently offline  rvanlooijen
Messages: 4
Registered: October 2010
Junior Member
As it turns out, the issue must have been with the VE. The strange part is that this was a cleanly created VE from a template we've used before.
Previous Topic: Unable to open pty: No such file or directory
Next Topic: /etc/resolv.conf reverts on reboot
Goto Forum:
  


Current Time: Thu Oct 09 05:31:36 GMT 2025

Total time taken to generate the page: 0.07514 seconds