|
|
| Re: Cannot allocate memory BUT failcnt is 0 for all resources [message #22213 is a reply to message #22211] |
Tue, 23 October 2007 15:04   |
khorenko
Messages: 533
Registered: January 2006
Location: Moscow, Russia
|
Senior Member |
|
|
Well, really a strange situation. Did you check the ulimits inside a problem VE?
Do you still have that VE? Can we somehow get a copy of it to dig the problem?
Thank you,
Konstantin.
If your problem is solved - please, report it!
It's even more important than reporting the problem itself...
|
|
|
|
| Re: Cannot allocate memory BUT failcnt is 0 for all resources [message #22216 is a reply to message #22213] |
Tue, 23 October 2007 15:30 |
benlm
Messages: 2
Registered: October 2007
|
Junior Member |
|
|
I've still got it around, and it's still showing symptoms.
[root@mysql4 /]# ulimit
unlimited
[root@mysql4 /]# ulimit -a
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
file size (blocks, -f) unlimited
pending signals (-i) 1024
max locked memory (kbytes, -l) unlimited
max memory size (kbytes, -m) unlimited
open files (-n) 1024
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
stack size (kbytes, -s) 10240
cpu time (seconds, -t) unlimited
max user processes (-u) 71680
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
[root@mysql4 /]#
Being the root user, any arbitrary limits set inside the VPS shouldn't affect me anyway right?
I've attached the relevant part of the config, as well as an updated beancounters paste (I've changed the config a bit since my first post).
If you can't think of anything else for me to check I'll remove any sensitive data from it and package it up for you to have a look at. I'd give you SSH access, but I can't get it on the network due to the memory issues.
Thanks.
|
|
|
|
| Re: Cannot allocate memory BUT failcnt is 0 for all resources [message #22261 is a reply to message #22216] |
Wed, 24 October 2007 08:59 |
khorenko
Messages: 533
Registered: January 2006
Location: Moscow, Russia
|
Senior Member |
|
|
Well, looks like i've no more ideas what to check...
* might be the content of the /proc/meminfo. Does it differ from the meminfo in working VE?
* might be strace of the small program which simply does alloc().
But i suppose the copy of the VE will be the simplest way.
BTW, please, tell me which kernel do you use and the host OS. (i think the latter doesn't matter but anyway).
If your problem is solved - please, report it!
It's even more important than reporting the problem itself...
|
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
