Re: VE Fails to start with dmesg error "err=-11". 64bit el5 patch. [message #32499 is a reply to message #32496] |
Tue, 12 August 2008 20:26 |
rickb
Messages: 368 Registered: October 2006
|
Senior Member |
|
|
Hi, I doubled all ulimit values, I see the same problem.
[root@kool bc]# ulimit -a
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 237216
max locked memory (kbytes, -l) 64
max memory size (kbytes, -m) unlimited
open files (-n) 2048
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 1619200
real-time priority (-r) 0
stack size (kbytes, -s) 20480
cpu time (seconds, -t) unlimited
max user processes (-u) 237216
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
[root@kool bc]# vzctl start 9893392 --force
Starting VE ...
VE is mounted
VE start failed
VE is unmounted
[root@kool bc]#
[root@kool bc]# dmesg | grep 9893392| tail -10
CT: 9893392: stopped
CT: 9893392: failed to start with err=-11
CT: 9893392: stopped
CT: 9893392: failed to start with err=-11
CT: 9893392: stopped
CT: 9893392: failed to start with err=-11
[root@kool bc]#
I am going to downgrade the kernel tonight as I found another bug in this one, the read/write accounting in /proc/bc/<veid>/ioacct is nonexistent.
[root@kool bc]# egrep 'read|write' */ioacct | grep vfs -v | head -10
0/ioacct: read 0
0/ioacct: write 0
402099/ioacct: read 0
402099/ioacct: write 0
6813/ioacct: read 0
6813/ioacct: write 0
889205/ioacct: read 0
889205/ioacct: write 0
889431/ioacct: read 0
889431/ioacct: write 0
This is with patch patch-92.1.1.el5.028stab057.2-combined, I am going to downgrade to patch-53.1.19.el5.028stab053.14-combined tonight and I will report back if either of these problems are solved by this.
Rick
-------------
Common Terms I post with: http://wiki.openvz.org/Category:Definitions
UBC. Learn it, love it, live it: http://wiki.openvz.org/Proc/user_beancounters
[Updated on: Tue, 12 August 2008 20:29] Report message to a moderator
|
|
|