For the past month, I have been encountering some problems with my WordPress installation. I keep getting the Error 500. I checked the log files and here’s what I found.
(12)Cannot allocate memory: couldn't create child process: /opt/suphp/sbin/suphp for

It’s can’t be right because JaguarPC has just upgraded my VPS and my new limit 640MB. I checked my memory usage and it’s only 112MB. I raised a ticket and the support did not find any problem on my settings and they also noticed that I have ample amount of spare memory. Take note that my VPS has a 2GB burstable memory. So that’s quite big for a small site that I maintain. So what’s the problem? My guess is on my settings especially that I did not change it ever since I started with 198MB of guaranteed memory. Others are blaming WordPress 3.2. Honestly, I don’t know what’s the cause but here are the things that I did.

First, increase the prefork settings on httpd.conf.
<IfModule prefork.c>
StartServers 5
MinSpareServers 10
MaxSpareServers 20
ServerLimit 100
MaxClients 100
MaxRequestsPerChild 2000
</IfModule>

Second is the KeepAlive settings which was set to Off

KeepAlive Off

After doing this, it seemed like the server stabilized. However, I again hit the error the next day. So I again checked what I can change. This time, I looked at the php.ini’s memory limit.

memory_limit = 32M ; Maximum amount of memory a script may consume (8MB)

That was originally 64M. I’ll update the post later if I hit the problem again. I might tweak both the php.ini and prefork settings if it fails again.

Comments are closed.

Post Navigation