OpenVZ Forum: Support » VE: XXX: failed to start with err=-11

Home » General » Support » VE: XXX: failed to start with err=-11

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

VE: XXX: failed to start with err=-11 [message #25601]

Wed, 02 January 2008 23:18

patrikweb
Messages: 5
Registered: January 2008

Junior Member

I get VE: XXX: failed to start with err=-11 when try start VE, if i stop another VE its started.

Have OpenVZ limit to max running VE?

Report message to a moderator

Re: VE: XXX: failed to start with err=-11 [message #25607 is a reply to message #25601]

Thu, 03 January 2008 07:55

vaverin
Messages: 708
Registered: September 2005

Senior Member

openVZ has not such limits, but system can lacks some resources.
could you please check failcounters in /proc/user_beancounters?

Report message to a moderator

Re: VE: XXX: failed to start with err=-11 [message #25609 is a reply to message #25607]

Thu, 03 January 2008 10:26

patrikweb
Messages: 5
Registered: January 2008

Junior Member

Have no failcounters to 0: and VE i try to start don't shows in user_beancounters

Report message to a moderator

Re: VE: XXX: failed to start with err=-11 [message #25715 is a reply to message #25609]

Tue, 08 January 2008 07:07

vaverin
Messages: 708
Registered: September 2005

Senior Member

Do you probably have some messages in /var/log/vzctl.log ?
You can get more informatuion if You set LOG_LEVEL=10 in global configuration file (/etc/sysconfig/vz)? and repeat the experiment.

Report message to a moderator

Re: VE: XXX: failed to start with err=-11 [message #25727 is a reply to message #25601]

Tue, 08 January 2008 10:25

yettyn
Messages: 31
Registered: January 2008
Location: Jihlava, CZ

Member

I had this issue as well after creating my own ve-vps.conf-sample with vzsplit, replacing ve-vps.basic.conf-sample. It turned out vz set all to low and wrong values for quota and inodes, so in some cases I couldn't even create a VE as just the template caused the quota hardlimit to trigger Smile

I think you can test this simple by setting DISK_QUOTA=no, if it works then you have found your problem Wink

/Joakim

Kernel 2.6.32-125.3
vzctl 4.9.4
Gentoo Linux x64

Report message to a moderator

Re: VE: XXX: failed to start with err=-11 [message #25783 is a reply to message #25727]

Tue, 08 January 2008 23:21

patrikweb
Messages: 5
Registered: January 2008

Junior Member

I have now set DISK_QUOTA=no and test DISK_QUOTA=no

If DISK_QUOTA=on

vzctl : VE 205 : Starting VE ...
vzctl : VE 205 : Running: /usr/sbin/vzquota show 205
vzctl : VE 205 : Running: /usr/sbin/vzquota on 205 -r 0 -b 1048676 -B 1153534 -i 200100 -I 220100 -e 0 -n 0 -s 0

vzctl : VE 205 : Mounting root: /var/lib/vz/root/205 /var/lib/vz/private/205

vzctl : VE 205 : VE is mounted
vzctl : VE 205 : Set iptables mask 0x000017bf
vzctl : VE 205 : Set features mask 0000000000000000/0000000000000000
vzctl : VE 205 : VE start failed
vzctl : VE 205 : Running: /usr/sbin/vzquota stat 205 -f
vzctl : VE 205 : Running: vzquota setlimit 205 -b 1048576 -B 1153434 -i 200000 -I 220000 -e 0 -n 0

vzctl : VE 205 : Running: /usr/sbin/vzquota stat 205 -f
vzctl : VE 205 : Running: /usr/sbin/vzquota off 205
vzctl : VE 205 : VE is unmounted

If DISK_QUOTA=off

vzctl : VE 205 : Starting VE ...
vzctl : VE 205 : Mounting root: /var/lib/vz/root/205 /var/lib/vz/private/205

vzctl : VE 205 : VE is mounted
vzctl : VE 205 : Set iptables mask 0x000017bf
vzctl : VE 205 : Set features mask 0000000000000000/0000000000000000
vzctl : VE 205 : VE start failed
vzctl : VE 205 : Running: /usr/sbin/vzquota stat 205 -f
vzctl : VE 205 : VE is unmounted

Report message to a moderator

Re: VE: XXX: failed to start with err=-11 [message #25884 is a reply to message #25727]

Thu, 10 January 2008 10:13

yettyn
Messages: 31
Registered: January 2008
Location: Jihlava, CZ

Member

yettyn wrote on Tue, 08 January 2008 11:25

I think you can test this simple by setting DISK_QUOTA=no, if it works then you have found your problem Wink

/Joakim

Correcting myself as this has started again, same pattern but I get err=-17 and now nothing seem to help, even if I switch off disk quota and give plenty of resourses... still can run max 1 VE Sad

/Joakim

Kernel 2.6.32-125.3
vzctl 4.9.4
Gentoo Linux x64

Report message to a moderator

Re: VE: XXX: failed to start with err=-11 [message #25932 is a reply to message #25884]

Fri, 11 January 2008 12:57

dev
Messages: 1693
Registered: September 2005
Location: Moscow

Senior Member

is it possible to get an access to check?
-17 means EEXISTS, so something wrong since kernel
thinks that some object already exists.
Maybe something messed with IDs (VEID, etc.)

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

Report message to a moderator

Re: VE: XXX: failed to start with err=-11 [message #25933 is a reply to message #25932]

Fri, 11 January 2008 13:02

patrikweb
Messages: 5
Registered: January 2008

Junior Member

dev wrote on Fri, 11 January 2008 07:57

is it possible to get an access to check?
-17 means EEXISTS, so something wrong since kernel
thinks that some object already exists.
Maybe something messed with IDs (VEID, etc.)

What -11 means?

Report message to a moderator

Re: VE: XXX: failed to start with err=-11 [message #25934 is a reply to message #25933]

Fri, 11 January 2008 13:05

dev
Messages: 1693
Registered: September 2005
Location: Moscow

Senior Member

#define EAGAIN 11 /* Try again */

almost similar in your context.

AFAICS from our your posts you use 2.6.22, correct?
and have oopses/call traces. may worth filling in bug.

Report message to a moderator

Re: VE: XXX: failed to start with err=-11 [message #25935 is a reply to message #25932]

Fri, 11 January 2008 13:09

yettyn
Messages: 31
Registered: January 2008
Location: Jihlava, CZ

Member

dev wrote on Fri, 11 January 2008 13:57

is it possible to get an access to check?
-17 means EEXISTS, so something wrong since kernel
thinks that some object already exists.
Maybe something messed with IDs (VEID, etc.)

You mean ssh access? sure, need to make some arrangements then though as I have the firewall configured to only let through sshd connects from my static IP. If you have a static ip or at least range that would make it easier. we can arrange that through privatemessage I guess.

Also look in my main thread about this ( http://forum.openvz.org/index.php?t=msg&th=5125&star t=0&) as I don't want to hijack this one Wink

/Joakim

Kernel 2.6.32-125.3
vzctl 4.9.4
Gentoo Linux x64

Report message to a moderator

Re: VE: XXX: failed to start with err=-11 [message #25936 is a reply to message #25934]

Fri, 11 January 2008 13:16

yettyn
Messages: 31
Registered: January 2008
Location: Jihlava, CZ

Member

dev wrote on Fri, 11 January 2008 14:05

#define EAGAIN 11 /* Try again */

almost similar in your context.

AFAICS from our your posts you use 2.6.22, correct?
and have oopses/call traces. may worth filling in bug.

I have 2.6.22 yes, don't know about patrickweb. I have tried to use 2.6.18 but cannot boot as it refuses to see my sata disk as sda, whatever config I try, just hda and 33Mhz bus speed Sad

which mean I have to change my fstab to mount hda and if fail mean I cannot boot into other kernel I have for backup - so no choice really.

As 2.6.22 is frosen I don't know if it's any use to file a bug on it - I would rather like to go for testing 2.6.24 then.

Kernel 2.6.32-125.3
vzctl 4.9.4
Gentoo Linux x64

Report message to a moderator

Re: VE: XXX: failed to start with err=-11 [message #26049 is a reply to message #25936]

Mon, 14 January 2008 22:31

patrikweb
Messages: 5
Registered: January 2008

Junior Member

yettyn wrote on Fri, 11 January 2008 08:16

dev wrote on Fri, 11 January 2008 14:05

#define EAGAIN 11 /* Try again */

almost similar in your context.

AFAICS from our your posts you use 2.6.22, correct?
and have oopses/call traces. may worth filling in bug.

I have 2.6.22 yes, don't know about patrickweb. I have tried to use 2.6.18 but cannot boot as it refuses to see my sata disk as sda, whatever config I try, just hda and 33Mhz bus speed Sad