Your message dated Sun, 29 May 2016 14:05:03 +0200 (CEST)
with message-id <[email protected]>
and subject line Re: Bug#736304: apache2-mpm-worker: error.log: child NNN exit
Segmentation fault
has caused the Debian Bug report #736304,
regarding apache2-mpm-worker: error.log: child NNN exit Segmentation fault
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
736304: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736304
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: apache2-mpm-worker
Version: 2.2.22-13
Severity: normal
File: /usr/sbin/apache2
Dear maintainer,
I recently noticed that long-running HTTP connections to my webserver
are closed at random points in time, and whenever such an event occurs,
a corresponding "child N exit Segmentation fault" message appears in
/var/log/apache2/errors.log. Here's an excerpt of errors.log:
[Mon Jan 20 11:24:54 2014] [notice] child pid 24196 exit signal
Segmentation fault (11)
At the exact same time, a connection to the server opened via
proxytunnel -v -B -p $host:443 -d <MAGIC_IP>:2222
was closed. I was monitoring the connection via tcpdump:
11:24:45.094427 IP CLIENT.39172 > SERVER.443: Flags [.],
ack 5889, win 212, options [nop,nop,TS val 3379557 ecr 168685518],
length 0
11:24:54.271639 IP SERVER.443 > CLIENT.39172: Flags [F.],
seq 5889, ack 5680, win 444, options [nop,nop,TS val 168687824 ecr
3379557], length 0
11:24:54.322112 IP CLIENT.39172 > SERVER.443: Flags [F.],
seq 5680, ack 5890, win 212, options [nop,nop,TS val 3381864 ecr
168687824], length 0
11:24:54.325877 IP SERVER.443 > CLIENT.39172: Flags [.],
ack 5681, win 444, options [nop,nop,TS val 168687837 ecr 3381864],
length 0
The connection was processed via mod_proxy_connect. However, even when
no connections via mod_proxy are active, I see lots of these Segmenation
fault messages, so I currently assume that the problem is not in
mod_proxy but somewhere deeper in apache's internals. For reference,
this is the mod_proxy configuration that I'm using:
--8<--
ProxyRequests on
AllowCONNECT 2222
ProxyVia on
<Proxy *>
Order deny,allow
Deny from all
</proxy>
SetEnvIf User-Agent ^magic_string_blablabla SSHTUNNEL_AUTHORIZED
<Proxy MAGIC_IP>
Order deny,allow
Deny from all
Allow from env=SSHTUNNEL_AUTHORIZED
</Proxy>
--8<--
Looking at my errors.log, I see 10 "Segmentation fault" messages for
Jan/20, while in the same time frame access.log lists 700 and
ssl_access.log lists 30 requests.
Maybe the problem is related to this bug [1]?
cheers,
David
[1] https://issues.apache.org/bugzilla/show_bug.cgi?id=50335
-- System Information:
Debian Release: 7.3
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: mipsel (mips64)
Kernel: Linux 2.6.39.4-dk1-fix1
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages apache2-mpm-worker depends on:
ii apache2.2-bin 2.2.22-13
ii apache2.2-common 2.2.22-13
apache2-mpm-worker recommends no packages.
apache2-mpm-worker suggests no packages.
-- no debconf information
--
GnuPG public key: http://dvdkhlng.users.sourceforge.net/dk2.gpg
Fingerprint: B63B 6AF2 4EEB F033 46F7 7F1D 935E 6F08 E457 205F
pgpOwNOxSQnoF.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---
version: 2.4.9-1
On Wed, 22 Jan 2014, David Kuehling wrote:
> I recently noticed that long-running HTTP connections to my webserver
> are closed at random points in time, and whenever such an event occurs,
> a corresponding "child N exit Segmentation fault" message appears in
> /var/log/apache2/errors.log. Here's an excerpt of errors.log:
>
> [Mon Jan 20 11:24:54 2014] [notice] child pid 24196 exit signal
> Segmentation fault (11)
> Maybe the problem is related to this bug [1]?
> [1] https://issues.apache.org/bugzilla/show_bug.cgi?id=50335
The bug you referenced has been fixed in 2.4.8. I am closing this report
accordingly. If you encounter this problem with more recent versions,
please re-open.
--- End Message ---