OpenVZ Forum


Home » General » Support » Recommendations for setting overcommit_memory (Apparently the default can cause problems)
Re: Recommendations for setting overcommit_memory [message #51094 is a reply to message #51091] Fri, 31 January 2014 23:51 Go to previous message
mustardman is currently offline  mustardman
Messages: 91
Registered: October 2009
Member
Ok so I guess it wasn't the Node having a problem but a container on the node. I concluded that because the first oom-killer message is oom-killer in ub xxx. Where xxx is apparently the container ID and it's always the same one. Seems to happen regularly on the hour and the container isn't even close to hitting their memory limits. Not sure what is going on now.

I am seeing this on several nodes. Always just one container.
 
Read Message
Read Message
Previous Topic: LVM checksum problem after yum update from CentOS 5.9 to CentOS 5.10 (w/o vzkernel update)
Next Topic: IPv6 ping but not work
Goto Forum:
  


Current Time: Thu Oct 17 03:59:50 GMT 2024

Total time taken to generate the page: 0.05356 seconds