We are happy to announce that Vesta is back under active development as of 25 February 2024. We are working on v1 candidate and expect to engage more with the community over the coming months. We are committed to open source, and we encourage contributors to help us build the future of Vesta.
[ERROR] AH00052: child pid [PID] exit signal Aborted (6)
[ERROR] AH00052: child pid [PID] exit signal Aborted (6)
Hello,
I see this notice in /var/log/apache2/error.log and I can't figure out what the problem is.
The notice appears at random intervals. For example:
Running a Google Search on this Forum, returned 0 results, which is quite strange. Am I the only one with this problem?
Running a general Google Search, some results indicate mod_ruid2 as the source of the problem. Is this so?
It's worth noting that even with this error in the logs, vhosts (different web sites) seem to be doing fine.
Anyone else facing this problem? Any suggestions?
OS: Ubuntu 16.04.3 LTS
VESTA CP: 0.9.8 (amd64) Release:19
I see this notice in /var/log/apache2/error.log and I can't figure out what the problem is.
Code: Select all
AH00052: child pid [PID HERE] exit signal Aborted (6)
Code: Select all
[Wed Jan 24 20:32:27.911581 2018] [core:notice] [pid 917] AH00052: child pid 31072 exit signal Aborted (6)
[Wed Jan 24 20:39:15.285921 2018] [core:notice] [pid 917] AH00052: child pid 31887 exit signal Aborted (6)
[Wed Jan 24 20:49:14.838257 2018] [core:notice] [pid 917] AH00052: child pid 3818 exit signal Aborted (6)
[Wed Jan 24 21:14:13.249387 2018] [core:notice] [pid 917] AH00052: child pid 6866 exit signal Aborted (6)
[Wed Jan 24 21:16:46.392158 2018] [core:notice] [pid 917] AH00052: child pid 12894 exit signal Aborted (6)
[Wed Jan 24 21:44:09.941337 2018] [core:notice] [pid 917] AH00052: child pid 2429 exit signal Aborted (6)
[Wed Jan 24 21:47:02.107842 2018] [core:notice] [pid 917] AH00052: child pid 17907 exit signal Aborted (6)
[Wed Jan 24 22:08:02.284286 2018] [core:notice] [pid 917] AH00052: child pid 21707 exit signal Aborted (6)
[Wed Jan 24 22:09:08.344324 2018] [core:notice] [pid 917] AH00052: child pid 31304 exit signal Aborted (6)
[Wed Jan 24 22:13:27.590386 2018] [core:notice] [pid 917] AH00052: child pid 24231 exit signal Aborted (6)
[Wed Jan 24 22:32:35.677303 2018] [core:notice] [pid 917] AH00052: child pid 26798 exit signal Aborted (6)
[Wed Jan 24 22:34:09.760577 2018] [core:notice] [pid 917] AH00052: child pid 26204 exit signal Aborted (6)
[Wed Jan 24 22:38:33.003439 2018] [core:notice] [pid 917] AH00052: child pid 31889 exit signal Aborted (6)
[Wed Jan 24 22:54:15.873379 2018] [core:notice] [pid 917] AH00052: child pid 14299 exit signal Aborted (6)
[Wed Jan 24 23:12:09.868539 2018] [core:notice] [pid 917] AH00052: child pid 14304 exit signal Aborted (6)
Running a general Google Search, some results indicate mod_ruid2 as the source of the problem. Is this so?
It's worth noting that even with this error in the logs, vhosts (different web sites) seem to be doing fine.
Anyone else facing this problem? Any suggestions?
OS: Ubuntu 16.04.3 LTS
VESTA CP: 0.9.8 (amd64) Release:19
Re: [ERROR] AH00052: child pid [PID] exit signal Aborted (6)
After a month of researching, I think that PHP7 is not very well compatible with mod_ruid2.Felix wrote: ↑Wed Jan 24, 2018 11:07 pmI see this notice in /var/log/apache2/error.log and I can't figure out what the problem is.Code: Select all
AH00052: child pid [PID HERE] exit signal Aborted (6)
Not on every server... I feel we hit a bug only on servers with lot of domains and lot of traffic.
mod_ruid2 works fine with PHP 5.6... but obviously there is some glitch with PHP7 in combination with lot of domains and lot of traffic.
I couldn't find a solution - the only solution is to switch everything to PHP-FPM (see viewtopic.php?f=41&t=17129 ) - remove completely PHP from Apache - remove mod_ruid2 from Apache - and finaly - switch Apache to mod_event :
Code: Select all
a2dismod ruid2
a2dismod suexec
a2dismod php5.6
a2dismod php7.0
a2dismod php7.1
a2dismod php7.2
a2dismod php7.4
a2dismod mpm_prefork
a2enmod mpm_event
find /home/*/web/*/public_html/ -type f -name ".htaccess" -exec sed -i 's|php_value|# php_value|g' {} \;
find /home/*/web/*/public_html/ -type f -name ".htaccess" -exec sed -i 's|php_admin_value|# php_admin_value|g' {} \;
find /home/*/web/*/public_html/ -type f -name ".htaccess" -exec sed -i 's|php_flag|# php_flag|g' {} \;
find /home/*/web/*/public_html/ -type f -name ".user.ini" -exec sed -i 's|auto_prepend_file|# auto_prepend_file|g' {} \;
find /home/*/web/*/public_shtml/ -type f -name ".htaccess" -exec sed -i 's|php_value|# php_value|g' {} \;
find /home/*/web/*/public_shtml/ -type f -name ".htaccess" -exec sed -i 's|php_admin_value|# php_admin_value|g' {} \;
find /home/*/web/*/public_shtml/ -type f -name ".htaccess" -exec sed -i 's|php_flag|# php_flag|g' {} \;
find /home/*/web/*/public_shtml/ -type f -name ".user.ini" -exec sed -i 's|auto_prepend_file|# auto_prepend_file|g' {} \;
find /home/*/conf/web/ -type f \( -name "apache2.*" -or -name "sapache2.*" -or -name "*.apache2.conf" -or -name "*.apache2.ssl.conf" \) -exec sed -i 's|php_|# php_|g' {} \;
service apache2 restart
There is no negative impact in server perfomance (tested on pretty loaded server with 300 domains)... in fact... everything is just more stable...
There are no more segfaults and "exit signal Aborted" in Apache.