VPS / virtual private servers > Virtual servers - general

Major RAM issue on VPS

(1/2) > >>

michel:
Hello,

I rented a VPS Pro XL EM-Edition 2016 a few days ago, and today I can finally take the time to start configuring it. Sadly I repeatedly get this error message when I try to install or run things:

--- Quote ---fork failed: Cannot allocate memory
--- End quote ---
A quick search confirmed the obvious: this message means I don't have enough RAM. However, top shows that I'm supposed to have +/-7 GB of free RAM...

Does my VPS really own 8 dedicated GB of RAM, or is the RAM provide as "best effort"? I don't really need 8 GB, but I do need 4 GB AND not to run into issues caused by the system having actually less RAM than it believes it has.

If this is an known issue, I'd like you to please cancel my VPS and credit its prorated value back into my account (no need for a PayPal refund, I'll use it to pay for my dedicated server - or you can do a PayPal refund if that's easier), as the VPS is unusable as-is. I can't even install fail2ban so I can't even secure it properly!

Here is a screenshot of me trying to install fail2ban:


and a top just after (note how many times I had to try to get it started...):


(Please tell me if I should open a ticket about this)

Thank you

Forum-Support2:
Hi,

OpenVZ is a little bit tricky with message "fork failed: Cannot allocate memory" because it display this message for reasons not only indicating low RAM. For instance it becomes displayed if you have a lot of network sockets open.

Please check the beancounter with

--- Code: ---cat /proc/user_beancounters
--- End code ---

If there are "failcounts" in one line, please contact the support for further checking. Please describe your application and how it works. They are able to explain the failcounts and find a solution for you.


kind regards,
Thomas

michel:
Hi,

Thank you, but even that won't work :

I've never had such an issue with any other VPS...

Regards

Forum-Support2:
Hello,

first of all:
Please note that different providers do provide different virtualization technologies. That can cause different error messages. A full virtualization is in our eyes the better technology compared with OpenVZ/Virtuozzo. But unfortuately EUserv does not provide full virtualized servers yet. (But we will do it in future.)

In your case:
Make a reboot via customer panel and perform command again.

kind regards,
Thomas

michel:
After reboot, failcnt = 0


About 5 minutes later, lots of numproc fails (and even more a few minutes later - can't even use the "reboot" command):

Navigation

[0] Message Index

[#] Next page

Go to full version