php hitting the wall a lot.

[ColumbusGEEK]

I am attempting to diagnose a issue with a VPS rage for a business I work with.

We seem to be getting a lot of memory allocation errors throughout the day, most noticeably with 50 plus visitors to a Joomla site. Of course I have run into it at night as well with far less users but less frequently.

I have raised the mem_limit to a rather abnormally high value via .htaccess.

php_value memory_limit 200M

as well as crankd up max_execution

php_value max_execution_time 120

Yet we still seem to white screen of death sometimes. is this a limitation of how much ram we have allocated to the VPS? How can I best diagnose this? I'm hoping it's just a tweak needed not a ram upgrade.

This looks discouraging.

         total            used             free       shared       buffers          cached
Mem:      12453500   12380304      73196          0          108876       5712004
-/+ buffers/cache:    6559424    5894076
Swap:     16779884        592   16779292

[ColumbusGEEK]

example.


Fatal error: Out of memory (allocated 3670016) (tried to allocate 4864 bytes)

Fatal error: Out of memory (allocated 524288) (tried to allocate 77824 bytes)

Fatal error: Out of memory (allocated 2883584) (tried to allocate 19456 bytes)

[ColumbusGEEK]

Looking at the RES column and adding it up seems to point the finger to us using all of our allocated ram resources.

Going to do some tweaking to bring the total usage down. Let's see if that solves it.

[lnxcode]

Originally Posted by ColumbusGEEK

example.


Fatal error: Out of memory (allocated 3670016) (tried to allocate 4864 bytes)

Fatal error: Out of memory (allocated 524288) (tried to allocate 77824 bytes)

Fatal error: Out of memory (allocated 2883584) (tried to allocate 19456 bytes)

Please run the command "Free" and let us know the output, but it looks like your using up all your RAM avaliable on the VPS.

[ColumbusGEEK]

I did some tweaking and drastically freed up some ram. Once the node issues clear up I can do some testing to see if I resolved it.

[lnxcode]

I would suggest:

1. Doing an update to cPanel:

# /scripts/upcp (in ssh)

2. Disable Spam Assassin *(TAKES HUGE AMOUNT OF RAM)*

3. Reboot after that.

[Shazam]

Originally Posted by lnxcode

I would suggest:

1. Doing an update to cPanel:

# /scripts/upcp (in ssh)

2. Disable Spam Assassin *(TAKES HUGE AMOUNT OF RAM)*

3. Reboot after that.

Maybe, but why would you want to disable the email spam checking mechanism?

[ColumbusGEEK]

Appreciate the suggestions guys, monitoring memory via top and disabling unneeded resources like spamassasan was the first thing I did. It wasn't enough.

I updated cPanel, we will see how that works out.

Shazam we use Google apps for all of our email needs. It is far superior to anything any hosting provider offers and integrates seamlessly, therefore Spamassasain is not needed. Good thing too, because we would be dropping and losing emails like crazy recently.