Page 1 of 1

Frequent 500 Internal Server Errors

Posted: Fri Feb 13, 2015 7:02 am
by pensivedog
I have a couple of VPS servers running CentOS 6.4 x32, each of which uses Vesta and hosts a single website built on Drupal 7.

All of these receive frequent 500 errors (almost daily) that require a server reboot to fix. This has been happening for months.

I have not had this issue running Drupal in other environments, which makes me think that it is an issue with Vesta, either a bug or just some server settings that need to be adjusted.

I am not very advanced when it comes to the webserver management or debugging, and I have not been able to find any error logs that could reveal the problem.

As one of the live websites experiencing this issue receives about 20,000 pageviews per month, I am really getting desperate to find a solution.

Please help!

Many thanks in advance!

Re: Frequent 500 Internal Server Errors

Posted: Fri Feb 13, 2015 8:41 am
by joem
pensivedog wrote:I have a couple of VPS servers running CentOS 6.4 x32, each of which uses Vesta and hosts a single website built on Drupal 7.

All of these receive frequent 500 errors (almost daily) that require a server reboot to fix. This has been happening for months.

I have not had this issue running Drupal in other environments, which makes me think that it is an issue with Vesta, either a bug or just some server settings that need to be adjusted.

I am not very advanced when it comes to the webserver management or debugging, and I have not been able to find any error logs that could reveal the problem.

As one of the live websites experiencing this issue receives about 20,000 pageviews per month, I am really getting desperate to find a solution.

Please help!

Many thanks in advance!
Can you please show us your php and apache error logs. Also which template are you using for nginx and apache
You can find the location of your errors logs below

Cent
http://vestacp.com/docs/#config-log-loc ... hel-centos

Debian and Ubuntu
http://vestacp.com/docs/#config-log-loc ... ian-ubuntu

Re: Frequent 500 Internal Server Errors

Posted: Fri Feb 13, 2015 9:29 am
by pensivedog
Thanks so much for the reply.
Can you please show us your php and apache error logs. Also which template are you using for nginx and apache
Apache error log mostly looks like this:

Code: Select all

[Fri Feb 13 06:26:11 2015] [notice] child pid 12443 exit signal Segmentation fault (11)
[Fri Feb 13 06:26:18 2015] [notice] child pid 12445 exit signal Segmentation fault (11)
[Fri Feb 13 06:27:14 2015] [notice] child pid 12446 exit signal Segmentation fault (11)
[Fri Feb 13 06:27:24 2015] [notice] child pid 12215 exit signal Segmentation fault (11)
[Fri Feb 13 06:27:33 2015] [notice] child pid 12448 exit signal Segmentation fault (11)
[Fri Feb 13 06:27:46 2015] [notice] child pid 12447 exit signal Segmentation fault (11)
[Fri Feb 13 06:28:02 2015] [notice] child pid 12444 exit signal Segmentation fault (11)
[Fri Feb 13 06:28:19 2015] [notice] child pid 12449 exit signal Segmentation fault (11)
[Fri Feb 13 06:28:25 2015] [notice] child pid 12450 exit signal Segmentation fault (11)
However there are a few places where this happens:

Code: Select all

[Fri Feb 13 06:23:19 2015] [notice] child pid 12204 exit signal Segmentation fault (11)
[Fri Feb 13 06:23:59 2015] [notice] child pid 12207 exit signal Segmentation fault (11)
[Fri Feb 13 06:24:14 2015] [notice] child pid 12209 exit signal Segmentation fault (11)
zend_mm_heap corrupted
[Fri Feb 13 06:24:15 2015] [notice] child pid 12211 exit signal Segmentation fault (11)
[Fri Feb 13 06:24:27 2015] [notice] child pid 12208 exit signal Segmentation fault (11)
[Fri Feb 13 06:24:39 2015] [notice] child pid 12206 exit signal Segmentation fault (11)
And the most recent part looks like this:

Code: Select all

[Fri Feb 13 06:39:51 2015] [notice] child pid 12955 exit signal Segmentation fault (11)
[Fri Feb 13 06:40:28 2015] [notice] child pid 12950 exit signal Segmentation fault (11)
[Fri Feb 13 06:40:47 2015] [notice] child pid 12957 exit signal Segmentation fault (11)
[Fri Feb 13 06:41:12 2015] [notice] child pid 12958 exit signal Segmentation fault (11)
[Fri Feb 13 06:41:35 2015] [notice] caught SIGTERM, shutting down
[Fri Feb 13 06:41:58 2015] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Fri Feb 13 06:41:58 2015] [notice] Digest: generating secret for digest authentication ...
[Fri Feb 13 06:41:58 2015] [notice] Digest: done
[Fri Feb 13 06:41:58 2015] [notice] mod_ruid2/0.9.4 enabled
[Fri Feb 13 06:41:59 2015] [notice] Apache/2.2.15 (Unix) DAV/2 PHP/5.4.24 mod_ssl/2.2.15 OpenSSL/1.0.0-f$
The php error log is very large (about 29MB) and mostly looks like this:

Code: Select all

2015/02/13 09:06:06 [crit] 1575#0: *11381 stat() "/home/admin/web/mywebsite.com/public_html/misc/grippie.png" failed (13: Permission denied), client: 120.204.156.175, server: mywebsite.com, request: "GET /misc/grippie.png HTTP/1.1", host: "www.mywebsite.com", referrer: "http://www.mywebsite.com/article/659"
For nginx and apache I am using the Vesta default templates.

Re: Frequent 500 Internal Server Errors

Posted: Sat Feb 14, 2015 4:52 pm
by skurudo
Oh... problems with apache and permissions... and it vesta fault? I like this way of thinking ;-)

Please check permissions and usergroup on files and folders first.
Then monitor a bit error log, segmentation fault it's weird and tricky webserver error.

Re: Frequent 500 Internal Server Errors

Posted: Sat Apr 11, 2015 7:35 am
by pensivedog
So this wasn't an issue with permissions or apache. Seems it was a conflict with Drupal 7 or some Drupal 7 modules with the version of PHP that was installed by Vesta. I have since followed digitalocean tutorials to setup an ubuntu 14.04 server with no control panel and transferred the site there. Everything is working smoothly, problem solved!

Re: Frequent 500 Internal Server Errors

Posted: Wed Apr 15, 2015 11:35 am
by skurudo
was a conflict with Drupal 7 or some Drupal 7 modules with the version of PHP that was installed by Vesta
Nope ;) Vesta use your system OS repo for all soft, which will be installed.
If Drupal module use old or depricaded methods like for php5.2 and you installed php5.4 or newer, that's can happen.