You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@httpd.apache.org by Stanislav Davydov <st...@gmail.com> on 2012/08/15 14:48:10 UTC
[users@httpd] clean_child_exit result in Program terminated with signal 11,
Segmentation fault.
Hello, everybody.
I am using my setup of Apache for rather long time and all the time it
spoof my logfiles with messages like:
[Wed Aug 15 13:37:55 2012] [notice] child pid 7415 exit signal Segmentation
fault (11), possible coredump in /etc/apache2
It does not affect services running on Apache but it makes difficult to
monitor state of services and also break my confidance that all is good
with config.
As I have found with GDB backtrace ("bt full") all those Segmentation
fault (11) are result of clean_child_exit() which invokes during destroying
of child process. That is why it does not affect our services.
Same time I want to avoid this problem.
I have attached config files and below is some explanations to those
configs.
We are using wildcard SSL now - so using statements like
<VirtualHost *:443 *:80>
in "ezserver.both"
with silent using of SSL certificates from default virtualhost
"109.35.9.221_my.ezserver.com.ssl.conf".
Then with help mod_rewrite we force users to use HTTPS instead of HTTP.
Due changes in Apache 2.2.12 (I consider that is bug in Apache)
we using trick in ports_STAGING.conf
Listen 443 http
More on that is here:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=541607
http://serverfault.com/questions/232782/debian-squeeze-upgrade-breaks-apache-ssl/415936#415936
http://www.aliov.org/123/server-should-be-ssl-aware-but-has-no-certificate-configured-hint-sslcertificatefile-null0/
Same time "Segmentation fault" we was reciving before using wildcard
certificates and using trick in "Listen" statement
--
--
Stanislav Davydov <st...@gmail.com>
[users@httpd] Fwd: clean_child_exit result in Program terminated with signal 11,
Segmentation fault.
Posted by Stanislav Davydov <st...@gmail.com>.
Hello, everybody.
I am using my setup of Apache for rather long time and all the time it
spoof my logfiles with messages like:
[Wed Aug 15 13:37:55 2012] [notice] child pid 7415 exit signal
Segmentation fault (11), possible coredump in /etc/apache2
It does not affect services running on Apache but it makes difficult
to monitor state of services and also break my confidance that all is
good with config.
As I have found with GDB backtrace ("bt full") all those
Segmentation fault (11) are result of clean_child_exit() which invokes
during destroying of child process. That is why it does not affect our
services.
Same time I want to avoid this problem.
I have attached config files and backtraces.
--
Stanislav Davydov <st...@gmail.com>