httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject DO NOT REPLY [Bug 45792] Worker segmentation fault
Date Thu, 18 Sep 2008 07:02:59 GMT

--- Comment #7 from Jacek Kaczmarek <>  2008-09-18 00:02:58 PST ---
Created an attachment (id=22599)
 --> (
truss log collected from httpd processes

truss log collected from httpd processes while 3 of them segfaulted in read()
invoked from ap_mpm_pod_check():54.

We were able to isolate this: the bug was reproduced by sending about 2000
requests in multiple threads (average spawning delay 10ms) to a static text
file (static.html - 0.5kB) served over reverse proxy.

configuration lines:

ProxyPass /php http://backend_server/php/proxied
ProxyPassReverse /php http://backend_server/php/proxied

The problem also occurs when using proxy balancer and a rewrite rule instead of
proxy pass:

RewriteRule ^/php/(.*)$ balancer://php_cluster/$1?%{ENV:QUERY_STRING} [P,L,QSA]
<Proxy balancer://php_cluster> 
  BalancerMember http://backend_server_1 smax=10 loadfactor=20
  BalancerMember http://backend_server_2 smax=10 loadfactor=20
  ProxySet maxattempts=2 stickysession=BALANCEID
(regardless of query string forwarding presence)

This problem does not occur when using a single backend server (no balancer)
with a rewrite rule
RewriteRule ^/php/(.*)$ http://backend_server/php/proxied/$1 [P,L,QSA]
For this scenario we get a different segmentation fault in
connection_destructor():1814 in proxy_util.c though. Stack trace follows. We
will check if the other segfault was already reported.

Of course the problem doesn't occur on locally served files. 

Configure bugmail:
------- You are receiving this mail because: -------
You are the assignee for the bug.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message