OpenVZ Forum


Home » General » Support » -bash: fork: Cannot allocate memory
Re: -bash: fork: Cannot allocate memory [message #29148 is a reply to message #29109] Mon, 07 April 2008 10:41 Go to previous messageGo to previous message
kir is currently offline  kir
Messages: 1645
Registered: August 2005
Location: Moscow, Russia
Senior Member
Quote:

The privvmpages count persists across restarts of the VE. Does this mean it's a cumulative count of *all* memory allocations, ever. for that VE? That seems wrong, unless this parameter is not meant be used except in unusual circumstances.


privvmpages.held (as well as all other UBC parameters) shows the current usage of this resource. If a container is stopped and any parameter's held value is more than zero, this means either a resource leak or a bug in accounting -- and in both cases should be reported straight to http://bugzilla.openvz.org/

Speaking of fail counters, see http://wiki.openvz.org/UBC_failcnt_reset

For more info, see http://wiki.openvz.org/privvmpages and in general http://wiki.openvz.org/UBC

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: startproc issue in a VPS
Next Topic: SOLVED: Hang on vzctl start/stop in futex() in the ve.
Goto Forum:
  

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

Current Time: Mon Apr 20 03:34:19 GMT 2026

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