Our linux guru gave us the solution : add more swap :-)

The server (running inside ESX) had 8Gb RAM with 3Gb used and only 512Mb swap. 
When forking a new process, the kernel first ensure there is enough space 
available on the swap to hold the process if needed.

So, we added a new disk and created a 8Gb swap onto. An no more error code.
--
Florian Deckert
SopraGroup France




-------------------- m2f --------------------

Read this topic online here:
http://forums.zenoss.com/viewtopic.php?p=32397#32397

-------------------- m2f --------------------



_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users

Reply via email to