fork: Cannot alocate Memory [message #38154] |
Tue, 24 November 2009 08:23  |
P_H_I_L
Messages: 7 Registered: November 2009
|
Junior Member |
|
|
Hey Sir, When I am starting my dimdim server this message is shown me: fork: Cannot alocate Memory
cat /proc/user_beancounters:
uid resource held maxheld barrier limit failcnt
202: kmemsize 3700437 5840579 11055923 11377049 0
lockedpages 0 0 256 256 0
privvmpages 381463 384383 384000 393212 821
shmpages 45 1341 21504 21504 0
dummy 0 0 0 0 0
numproc 78 140 240 240 0
physpages 16907 19458 0 2147483647 0
vmguarpages 0 0 262144 2147483647 0
oomguarpages 16907 19458 26112 2147483647 0
numtcpsock 10 21 360 360 0
numflock 8 9 188 206 0
numpty 0 1 16 16 0
numsiginfo 0 33 256 256 0
tcpsndbuf 89440 136396 1720320 2703360 0
tcprcvbuf 188980 222584 1720320 2703360 0
othersockbuf 6708 16916 1126080 2097152 0
dgramrcvbuf 0 8380 262144 262144 0
numothersock 19 28 360 360 0
dcachesize 0 0 3409920 3624960 0
numfile 1475 2655 9312 9312 0
dummy 0 0 0 0 0
dummy 0 0 0 0 0
dummy 0 0 0 0 0
numiptent 10 10 128 128 0
101: kmemsize 3338174 3816804 11055923 11377049 0
lockedpages 0 0 256 256 0
privvmpages 293342 301963 965536 969632 0
shmpages 0 1341 21504 21504 0
dummy 0 0 0 0 0
numproc 73 80 240 240 0
physpages 135597 145294 0 2147483647 0
vmguarpages 0 0 99933792 2147483647 0
oomguarpages 135597 145294 26112 2147483647 0
numtcpsock 19 26 360 360 0
numflock 4 5 188 206 0
numpty 0 1 16 16 0
numsiginfo 0 12 256 256 0
tcpsndbuf 143104 172172 1720320 2703360 0
tcprcvbuf 131072 221748 1720320 2703360 0
othersockbuf 6708 16916 1126080 2097152 0
dgramrcvbuf 0 8380 262144 262144 0
numothersock 11 18 360 360 0
dcachesize 0 0 3409920 3624960 0
numfile 1346 1559 9312 9312 0
dummy 0 0 0 0 0
dummy 0 0 0 0 0
dummy 0 0 0 0 0
numiptent 10 10 128 128 0
0: kmemsize 6677257 7908659 2147483647 2147483647 0
lockedpages 0 0 2147483647 2147483647 0
privvmpages 73438 92242 2147483647 2147483647 0
shmpages 1358 2974 2147483647 2147483647 0
dummy 0 0 2147483647 2147483647 0
numproc 124 141 2147483647 2147483647 0
physpages 29131 45853 2147483647 2147483647 0
vmguarpages 0 0 2147483647 2147483647 0
oomguarpages 29164 45853 2147483647 2147483647 0
numtcpsock 10 19 2147483647 2147483647 0
numflock 7 11 2147483647 2147483647 0
numpty 1 2 2147483647 2147483647 0
numsiginfo 1 12 2147483647 2147483647 0
tcpsndbuf 98332 335720 2147483647 2147483647 0
tcprcvbuf 163840 839960 2147483647 2147483647 0
othersockbuf 111800 150764 2147483647 2147483647 0
dgramrcvbuf 0 16760 2147483647 2147483647 0
numothersock 92 102 2147483647 2147483647 0
dcachesize 0 0 2147483647 2147483647 0
numfile 2693 3029 2147483647 2147483647 0
dummy 0 0 2147483647 2147483647 0
dummy 0 0 2147483647 2147483647 0
dummy 0 0 2147483647 2147483647 0
numiptent 10 10 2147483647 2147483647 0
Can anybody help me and say the problem?
I have 2 Virtual machines every need min. 1 u. max. 2 gb RAM
How can i configurate this? And I have a Pentium 2,4 Server. What CPUUNIT I can configurate?
I dont know how to calculate in linux. iam a newbie )
Greetz,
Philipp
[Updated on: Wed, 25 November 2009 13:04] by Moderator Report message to a moderator
|
|
|
Re: fork: Cannot alocate Memory [message #38155 is a reply to message #38154] |
Tue, 24 November 2009 08:37   |
khorenko
Messages: 533 Registered: January 2006 Location: Moscow, Russia
|
Senior Member |
|
|
Hi Philipp,
cat /proc/user_beancounters:
uid resource held maxheld barrier limit failcnt
privvmpages 381463 384383 384000 393212 821
Look, you simply got a "privvmpages" failcounters, which means that your Container allocated too much memory and hit its limit (allocated != used).
Well, i think you have to understand what application inside a Container requires so many RAM (381463*4096=1562472448 ~ 1.5 Gb is quite a lot) and decide if this is normal or not for that application.
And if you decide that this is normal, should just have to increase the privvmpages limit.
Hope that helps.
And talking about CPUUNITS... well, just leave it by default at least you get a stable and working system. 
Good luck!
--
Konstantin
If your problem is solved - please, report it!
It's even more important than reporting the problem itself...
[Updated on: Tue, 24 November 2009 10:38] by Moderator Report message to a moderator
|
|
|
|
Re: fork: Cannot alocate Memory [message #38158 is a reply to message #38157] |
Tue, 24 November 2009 15:49   |
khorenko
Messages: 533 Registered: January 2006 Location: Moscow, Russia
|
Senior Member |
|
|
vzctl set 202 --privvmpages 768000:786424 --save
This will provide your Container 3 Gb of RAM for allocation.
--
Konstantin
If your problem is solved - please, report it!
It's even more important than reporting the problem itself...
|
|
|
|
Re: fork: Cannot alocate Memory [message #38163 is a reply to message #38160] |
Wed, 25 November 2009 07:50   |
khorenko
Messages: 533 Registered: January 2006 Location: Moscow, Russia
|
Senior Member |
|
|
Please, post here:
# cat /proc/user_beancounters
# vzctl start 202
# // any command do get "cannot allocate memory" error
# cat /proc/user_beancounters
Thanks.
--
Konstantin
If your problem is solved - please, report it!
It's even more important than reporting the problem itself...
|
|
|
|
Re: fork: Cannot alocate Memory [message #38166 is a reply to message #38164] |
Wed, 25 November 2009 08:20   |
khorenko
Messages: 533 Registered: January 2006 Location: Moscow, Russia
|
Senior Member |
|
|
You've got "numproc" failcounters.
Please, increase "numproc" limits.
If your problem is solved - please, report it!
It's even more important than reporting the problem itself...
|
|
|
|