Internal server error message in Evo manager frames

Hello,

Lately I have noticed a client's Evo websites (6 on the same shared hosting on a reseller account) displaying internal server error messages in one or more of the Evo manager frames when logging into, or generally using, the Evo Manager.

The internal server error message can usually be removed by refreshing the frame. When the issue is happening, it always appears on login. It also can appear after saving a resource or element.

The error message usually occurs in only one of the manager frames at a time, with the "main RHS" frame being most common - but it can also appear in the "LHS tree" frame, and less occasionally in the "top header" frame.

I've noticed this happening recently on some client sites (all on shared servers) at a couple of different web hosts.

It started happening on Evo 1.0.12 (now 1.0.14) sites on the same reseller account after a short period of time (say a month or so) of being moved to newer shared hosting servers which has "Cloud Linux" installed (case A).
* MySQL 5.5.25-cll
* PHP 5.3.28
* memory_limit 256MB

The issue never previously occurred on these sites on the older shared hosting servers at the same host.
* MySQL 5.0.96-community
* PHP 5.2.17
* memory_limit 64MB

It also happens on a different Evo website (1.0.10) (case B) which is at a different webhost. Although interestingly, when I logged into this Evo manager to today to check version numbers the error did not occur which is the first time ever.
* MySQL 5.5.36-cll
* PHP 5.3.27
* memory_limit 64MB

So I am not sure if the error is related to Cloud Linux - or a setting on the server - or something in Evo which causes the problem.

(I have never seen the issue on WordPress or PrestaShop sites.)

After going back and forth with one of the Australian web hosts, it was suggested that its to do with resource usage. On the main lot of servers that I am talking about above (case A), a 1 GB memory limit applies (which I believe refers to RAM). The host says "This 1 GB memory limit is assigned to each cPanel user on the server. If the websites hosted under that user exceeds that limit then only website shows the internal server error. If website run within that limit then website will not show this error anymore."

When the host resets the "Cloud Linux", the case A problem goes away and all manager frames load as expected - no error messages appear. Unfortunately we cannot control the resetting - that is handled by the host and applies to all sites on the server so is not a viable solution.

One of the case A sites is medium size (100 pages) and gets a fair bit of traffic. The others are just small sites with standard traffic. The case B site is small in size and traffic.

The case A client contacted the host about the issue directly today and was advised something different: "For that you must contact your developer and ask him to optimize the website's PHP memory_limit usage". How can I do that? And regardless, the memory_limit for the case A sites is bigger than the older server than had no issue.

I'd love to know what is causing the issue and wonder if any other Evo users have experienced the internal server error message in one or more of the Evo manager frames - and what can be done to stop if from happening again?

Thanks in advance. [ed. note: nickf08 last edited this post 12 years, 3 months ago.]

me too , I have a same problem.

My old hosting -
Apache version 2.2.24
PHP version 5.3.27
MySQL version 5.5.36-cll

My new Hosting -
Apache version 2.2.24
PHP version 5.3.25
MySQL version 5.5.35-cll


Thank you .

3 thoughts...
1. http://wiki.modxcms.com/index.php/What_is_mod_security_and_how_does_it_affect_me
2. File permissions 755/644
3. You normally set memory_limit in a php.ini file but can be done through htaccess

Quote from: zawlinoo at Jun 18, 2014, 02:01 PM

me too , I have a same problem.

Hi zawlinoo, lets see if we can get it sorted...

Quote from: mrhaw at Jun 18, 2014, 06:36 PM

3 thoughts...
1. http://wiki.modxcms.com/index.php/What_is_mod_security_and_how_does_it_affect_me
2. File permissions 755/644
3. You normally set memory_limit in a php.ini file but can be done through htaccess

Thanks MR Haw.

After the client chatted with the host, they reset the cloud linux for him - so today the issue is not happening.
I can't really test anything from the 1st point from the Wiki until the error starts again.
Are you able to test any of those things zawlinoo and see if they make a difference?

File permissions are set at 755 folders and 644 files so that looks ok.

What is the recommended memory_limit for Evo 1.0.14?

Hi, Mr Haw

1 & 3 not work, I add htaccess -

<IfModule mod_php5.c>
php_value memory_limit 64M
</IfModule>

But not work, I ask my hosting's support team to change -

Resource Limits memory_limit Maximum amount of memory a script may consume (32MB) 32M

in my php configuation.

2 -
my current file permission is 755.

Tonight, I try to reinstall modx and add only (images,templates folder from old host's ), because I move all of the folder from old host. ( mysite -> assets , manager ).

Thank you Mr Haw , nickf08

Quote from: mrhaw at Jun 18, 2014, 06:36 PM

3 thoughts...
1. http://wiki.modxcms.com/index.php/What_is_mod_security_and_how_does_it_affect_me
2. File permissions 755/644
3. You normally set memory_limit in a php.ini file but can be done through htaccess

Quote from: nickf08 at Jun 18, 2014, 10:25 PM

What is the recommended memory_limit for Evo 1.0.14?

I'm using 128MB without problems but if you use 3rd party apps such as ecommerce etc. go for 256MB or more.

Quote from: mrhaw at Jun 19, 2014, 07:29 AM

I'm using 128MB without problems but if you use 3rd party apps such as ecommerce etc. go for 256MB or more.

Thanks Mr Haw, I will see if the host will let us have that much (from memory this host can be a bit stingy with that).

How did you go zawlinoo?

php.ini

memory_limit = 256M

.htaccess

<IfModule mod_suphp.c>
suPHP_ConfigPath /home/msc/public_html
</IfModule>

<IfModule mod_security.c>
# Turn the filtering engine Off
SecFilterEngine Off
</IfModule>

Problem still occur .
I think VPS plan can solve it.

But other sites from Shared Host (same company) not show internal server error.
But Reseller plan's shared host show the error.

And Error log :
[Fri Jun 20 01:41:05 2014] [error] [client xx.xx.xx.xx] (12)Cannot allocate memory: couldn't create child process: /opt/suphp/sbin/suphp for /home/msc/public_html/mydomain.com/index.php, referer: http://www.mydomain.com/manager/index.php?a=1&f=menu

Quote from: zawlinoo at Jun 20, 2014, 03:47 AM

And Error log :
[Fri Jun 20 01:41:05 2014] [error] [client xx.xx.xx.xx] (12)Cannot allocate memory: couldn't create child process: /opt/suphp/sbin/suphp for /home/msc/public_html/mydomain.com/index.php, referer: http://www.mydomain.com/manager/index.php?a=1&f=menu

Hmm... https://www.google.com/search?q=/opt/suphp/sbin/suphp

Ask you hosting company if they can see what is different in your setup between the other sites working.
I believe traffic has to do with it and a VPS would help. Why not ask the hosting company if you can try it for free
a month.

Quote from: mrhaw at Jun 19, 2014, 07:29 AM

I'm using 128MB without problems but if you use 3rd party apps such as ecommerce etc. go for 256MB or more.

I forgot to check my original numbers in the first post - the sites are already at 256MB so that should probably be enough

Great research zawlinoo, thanks for sharing all that info.

This a mystery.

But Reseller plan's shared host show the error.

Maybe reseller plans get squished because the web host gives the same total amount of memory usage regardless of how many sites there are and how much traffic they have? Reseller owners probably don't ever get told this.
Regardless, the same problem was happening for me on the case B standalone site with a different host so that was not a reseller issue.