OpenVZ Forum


Home » General » Support » fork: Cannot alocate Memory ([solved] starting dimdim server)
Re: fork: Cannot alocate Memory [message #38155 is a reply to message #38154] Tue, 24 November 2009 08:37 Go to previous messageGo to previous message
khorenko is currently offline  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. Smile

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

 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Memory Allocation issues
Next Topic: canno start VE's --> openvz kernel problem?
Goto Forum:
  


Current Time: Thu Jul 24 13:14:27 GMT 2025

Total time taken to generate the page: 0.48055 seconds