OpenVZ Forum


Home » General » Support » How to prevent total unavailability due Unable to fork
Re: How to prevent total unavailability due Unable to fork [message #51209 is a reply to message #51204] Sun, 09 March 2014 11:59 Go to previous messageGo to previous message
Ales is currently offline  Ales
Messages: 330
Registered: May 2009
Senior Member
Unable to fork means that your VM's resources are exhausted and the programs within are experiencing fatal errors because of it.

The reason why this doesn't rectify itself after the resource usage has lowered is that the programs have actually already crashed beacuse they couldn't operate normally. When this happens to crucial parts of the OS, the only solution is a restart.

I mean, even of some websites appear to work, it doesn't mean they are working properly. Your apache might be serving some of the pages, while the database back-end could already be in a broken state. Any number of serious errors might happen, even such that corrupt the user's data permanently.

What you should do is monitor the beancounters actively and warn users as soon as you spot first failures. If the user constantly experience such problems, tell them to upgrade to a bigger VM as a precaution.

If they don't want to upgrade, tell them it's their responsibility and they should live with the consequences. It's as simple as that, really.

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: Sat Apr 11 15:12:01 GMT 2026

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