OpenVZ Forum


Home » General » Support » How to prevent total unavailability due Unable to fork
How to prevent total unavailability due Unable to fork [message #51204] Fri, 07 March 2014 22:09 Go to previous message
postcd is currently offline  postcd
Messages: 73
Registered: April 2013
Member
Cannot allocate memory: Unable to fork..

I mean some VM has high memory usage and it get totally locked so admin cant do commands in it, user cant login SSH, but websites working....

How can vps node admin can prevent this to happen allowing user to know what is happening with his VPS, or how to ensure user is able to use SSH?

Im not sure why this Unable to fork message appears. I thought it should be that load decrease and VPS becomes accessible, but it appears that this message is definite and VM must be manually restarted which makes customers unhappy. DOes XEN have same issues with inaccessibility and need restart?

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: How to use tc to limit traffic?
Next Topic: Strange Centos 5 container behaviour on Centos 6 node
Goto Forum:
  

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

Current Time: Fri Feb 20 20:20:14 GMT 2026

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