Ubuntu10.4 Nginx + Wordpress is working only short time and found Cannot allocate memory

  • Posted April 19, 2014


I tried to install Ubuntu10.4 Nginx + Wordpress and I can load my site just only a short time and got message on Firefox browser "The page you are looking for is temporarily unavailable. Please try again later. "

Then I went back to ssh terminal and trying to check if nginx is running, I found “-bash: fork: Cannot allocate memory”

and whenever I use any command, I found the same message -bash: fork: Cannot allocate memory

then shortly after, It will work again, then after loading a few pages then it lost connection again.

Please help I tried so many times , I followed many configurations from digital ocean but not succeed.


Submit an answer
You can type!ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

What size droplet are you using? Could you describe your Wordpress set up a little? Do you have a large number of plugins installed? <br> <br>You might want to consider moving to a larger droplet.

Hello <br> <br>Please help <br> <br>Thanks <br>Bright

I’m just curious why I got so less memory on this line <br>Mem: 1018820 860364 158456 0 34508 142884 <br> <br>It said free memory left just 158456 <br> <br>

Hi Sianinos, <br> <br>Thank you for your reply. <br>Here’s what I found <br> <br>> free -l <br> <br> total used free shared buffers cached <br>Mem: 1018820 860364 158456 0 34508 142884 <br>Low: 1018820 860364 158456 <br>High: 0 0 0 <br>-/+ buffers/cache: 682972 335848 <br>Swap: 0 0 0 <br> <br> <br> <br>> unlimit -a <br>core file size (blocks, -c) 0 <br>data seg size (kbytes, -d) unlimited <br>scheduling priority (-e) 0 <br>file size (blocks, -f) unlimited <br>pending signals (-i) 7813 <br>max locked memory (kbytes, -l) 64 <br>max memory size (kbytes, -m) unlimited <br>open files (-n) 1024 <br>pipe size (512 bytes, -p) 8 <br>POSIX message queues (bytes, -q) 819200 <br>real-time priority (-r) 0 <br>stack size (kbytes, -s) 8192 <br>cpu time (seconds, -t) unlimited <br>max user processes (-u) 7813 <br>virtual memory (kbytes, -v) unlimited <br>file locks (-x) unlimited

Your droplet probably run out of memory. Can you post us the results of the following commands? <br>free -h <br>ulimit -a