(notification) child pid XXXX output signal Segmentation error (11), possibly coredump in / etc / apache2

I keep getting the following error in my Apache log:

[Wed Sep 18 17:59:20 2013] [notice] Apache/2.2.22 (Ubuntu) PHP/5.3.10-1ubuntu3.8 with Suhosin-Patch configured -- resuming normal operations [Wed Sep 18 18:06:30 2013] [notice] child pid 7505 exit signal Segmentation fault (11), possible coredump in /etc/apache2 [Wed Sep 18 18:06:35 2013] [notice] child pid 7497 exit signal Segmentation fault (11), possible coredump in /etc/apache2 [Wed Sep 18 18:13:53 2013] [notice] child pid 7501 exit signal Segmentation fault (11), possible coredump in /etc/apache2 [Wed Sep 18 18:13:53 2013] [notice] child pid 7506 exit signal Segmentation fault (11), possible coredump in /etc/apache2 [Wed Sep 18 18:14:14 2013] [notice] child pid 8708 exit signal Segmentation fault (11), possible coredump in /etc/apache2 

I tried to execute it by following these steps:

 user:~$ sudo gdb user 8670 8571 0 18:12 pts/3 00:00:00 grep --color=auto httpd user:~$ sudo gdb (gdb) attach 8571 Attaching to process 8571 Reading symbols from /bin/bash...(no debugging symbols found)...done. Reading symbols from /lib/x86_64-linux-gnu/libtinfo.so.5...(no debugging symbols found)...done. Loaded symbols for /lib/x86_64-linux-gnu/libtinfo.so.5 Reading symbols from /lib/x86_64-linux-gnu/libdl.so.2...(no debugging symbols found)...done. Loaded symbols for /lib/x86_64-linux-gnu/libdl.so.2 Reading symbols from /lib/x86_64-linux-gnu/libc.so.6...(no debugging symbols found)...done. Loaded symbols for /lib/x86_64-linux-gnu/libc.so.6 Reading symbols from /lib64/ld-linux-x86-64.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/ld-linux-x86-64.so.2 Reading symbols from /lib/x86_64-linux-gnu/libnss_compat.so.2...(no debugging symbols found)...done. Loaded symbols for /lib/x86_64-linux-gnu/libnss_compat.so.2 Reading symbols from /lib/x86_64-linux-gnu/libnsl.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/x86_64-linux-gnu/libnsl.so.1 Reading symbols from /lib/x86_64-linux-gnu/libnss_nis.so.2...(no debugging symbols found)...done. Loaded symbols for /lib/x86_64-linux-gnu/libnss_nis.so.2 Reading symbols from /lib/x86_64-linux-gnu/libnss_files.so.2...(no debugging symbols found)...done. Loaded symbols for /lib/x86_64-linux-gnu/libnss_files.so.2 0x00007f553000244e in waitpid () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) backtrace #0 0x00007f553000244e in waitpid () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x0000000000441419 in ?? () #2 0x000000000044255c in wait_for () #3 0x0000000000432c88 in execute_command_internal () #4 0x00000000004352fe in execute_command () #5 0x000000000041e31d in reader_loop () #6 0x000000000041ca87 in main () (gdb) backtrace full #0 0x00007f553000244e in waitpid () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. #1 0x0000000000441419 in ?? () No symbol table info available. #2 0x000000000044255c in wait_for () No symbol table info available. #3 0x0000000000432c88 in execute_command_internal () No symbol table info available. #4 0x00000000004352fe in execute_command () No symbol table info available. #5 0x000000000041e31d in reader_loop () No symbol table info available. #6 0x000000000041ca87 in main () No symbol table info available.` 

I can not talk about the problem.

I also run gdb on apache as follows:

 user:~$ sudo gdb apache2 Reading symbols from /usr/sbin/apache2...(no debugging symbols found)...done. (gdb) run Starting program: /usr/sbin/apache2 [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". apache2: bad user name ${APACHE_RUN_USER} [Inferior 1 (process 6925) exited with code 01] 

I don’t know if this is due to this problem, but as soon as I installed gdb, the following message is displayed at login:

 => There were exceptions while processing one or more plugins. See /var/log/landscape/sysinfo.log for more information. 

sysinfo.log contains the following:

 for process_info in info.get_all_process_info(): File "/usr/lib/python2.7/dist-packages/landscape/lib/process.py", line 49, in get_all_process_info process_info = self.get_process_info(process_id) File "/usr/lib/python2.7/dist-packages/landscape/lib/process.py", line 85, in get_process_info process_info["state"] = STATES[state] KeyError: 't (tracing stop)' 2013-09-18 18:43:35,633 ERROR Processes plugin raised an exception. Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/landscape/sysinfo/sysinfo.py", line 99, in run result = plugin.run() File "/usr/lib/python2.7/dist-packages/landscape/sysinfo/processes.py", line 18, in run for process_info in info.get_all_process_info(): File "/usr/lib/python2.7/dist-packages/landscape/lib/process.py", line 49, in get_all_process_info process_info = self.get_process_info(process_id) File "/usr/lib/python2.7/dist-packages/landscape/lib/process.py", line 85, in get_process_info process_info["state"] = STATES[state] KeyError: 't (tracing stop)' 

A bit of background.

I am running a WordPress site from my VPS. VPS is an Ubuntu-based LAMP server with PERL and CURL installed. I use APC for caching, but my segmentation errors occurred before I installed APC. Finally, I start my server through the Google PageSpeed ​​service, so I installed mod_remoteip mod for Apache 2.2 and you have the X-Forwarded-For header.

The ulimit kernel is not limited. My phpinfo () file can be found here: http://tecne.ws/11v

Help. It would be very grateful!

+7
source share
6 answers

I had this problem and changed LogLevel warn to LogLevel debug in apache configuration. On restarting, it seems to have been interrupted immediately after mod_deflate.

Disabling mod_deflate in debian / ubuntu should only be sudo a2dismod deflate

+5
source

I solved it indirectly. I installed Nginx in front of Apache and I no longer have segmentation errors. In my opinion, Nginx before Apache is better configured. Cache varnish may also have solved the problem.

+3
source

After a whole day trying to trace it, no solutions worked. In the end, however, I turned Apache to debug the registration level and immediately noticed hundreds of notifications / warnings from Google mod_pagespeed for Apache trying to rewrite images from Jetpack Photon images.

I made a simple a2dismod pagespeed and no longer experienced segmentation failures.

Also noticed that my sites actually work faster when mod pagespeed is disabled.

There seem to be a few error messages in the pages causing segmentation errors.

Not sure if its just mod_pagespeed or a combination of mod_pagespeed, wordpress and php .... but it's disabled, now the problem is gone.

I ended up with this for now, as well as in the process of moving everything to Nginx. Tracing errors on Apache always turn into a nightmare, with Nginx I can find errors a few seconds to a minute.

+1
source

Try to install

max_input_time = -1

in the php.ini file.

from php.ini ...

; Maximum amount of time each script may spend parsing request data. It a good; idea to limit this time on productions servers in order to eliminate unexpectedly ; long running scripts. ; Note: This directive is hardcoded to -1 for the CLI SAPI ; Default Value: -1 (Unlimited) ; Development Value: 60 (60 seconds) ; Production Value: 60 (60 seconds) ; http://php.net/max-input-time ; Maximum amount of time each script may spend parsing request data. It a good; idea to limit this time on productions servers in order to eliminate unexpectedly ; long running scripts. ; Note: This directive is hardcoded to -1 for the CLI SAPI ; Default Value: -1 (Unlimited) ; Development Value: 60 (60 seconds) ; Production Value: 60 (60 seconds) ; http://php.net/max-input-time ;

0
source

I had the same problem with Varnish> Apache> PHP-FPM on Centos 6.

I solved this by disabling KeepAlive in Apache.

0
source

In my case, an error occurred when I accessed my site with iOS / MacOS Safari. After the first access from one of these devices, apache continued to fail with segmentation errors on any request from any device until the next restart.

The problem disappeared after disabling the Google module mod_spdy .

0
source

Source: https://habr.com/ru/post/954087/


All Articles