OpenVZ Forum


Home » General » Support » Syslog-ng on HN eats RAM and OOM Killer kills VE processess (CRITICAL)
Re: Syslog-ng on HN eats RAM and OOM Killer kills VE processess (CRITICAL) [message #35915 is a reply to message #35913] Thu, 30 April 2009 09:09 Go to previous messageGo to previous message
kir is currently offline  kir
Messages: 1645
Registered: August 2005
Location: Moscow, Russia
Senior Member
januszzz wrote on Thu, 30 April 2009 12:49

Here it goes.


This pretty much answers it. Your mem+swap commitment is more than 100%, meaning you allow to allocate more RAM+swap than you actually have.

See http://wiki.openvz.org/UBC_systemwide_configuration which explains it in great details. In particular, it says "Commitment levels more than 1 means that the containers are guaranteed more memory than the system has. Such overcommitment is strongly not recommended, because in that case if all the memory is consumed, random applications, including the ones belonging to the host system, may be killed and the system may become inaccessible by ssh(1) and lose other important functionality". See, this precisely describes your situation.

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

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: shell used by 'vzctl enter'
Next Topic: df showing wrong output - SOLVED
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Mon Jan 19 10:34:15 GMT 2026

Total time taken to generate the page: 0.80704 seconds
Powered by FUDforum Powered by Virtuozzo Containers