httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tobias Adolph <Tobias.Ado...@lrz.de>
Subject Re: AH01075 severity?
Date Fri, 24 Jul 2015 07:17:20 GMT
I think this is related to

Bug https://bz.apache.org/bugzilla/show_bug.cgi?id=58118

Whereas the 503-logging has been fixed, the verbose error logging is 
still an issue in 2.4.16 (I planned to report this).

Speaking for modules/proxy/mod_proxy_fcgi.c, lowering the log level in 
line 836  to something like debug or trace1 (I'm not familiar with the 
policy or formality of loglevels in Apache httpd) should help.

It would be even better to log only conditionally (in line 848 just 
before the HTTP_SERVICE_UNAVAILABLE retval), since at this point we can 
exclude any return value from dispatch that is not due to the client 
closing the connection or sending a bad request.

Should I propose a patch?

Kind regards,
Tobias Adolph


Am 24.07.2015 um 03:48 schrieb Eric Covener:

https://bz.apache.org/bugzilla/show_bug.cgi?id=58118


>  From IRC twice recently:
>
>   [Thu Jul 23 20:43:45.302847 2015] [proxy_fcgi:error] [pid 26912:tid
> 140172515514112] (32)Broken pipe: [client $IP:2587] AH01075: Error
> dispatching request to : (passing brigade to output filters)
>
> We would not report broken pipe on the client side as "error" in other places.
>
> (there's also some issue with a NULL sever_portstr which is why it
> reads a littlef unny)

-- 
###############################
# Tobias Adolph		      #		
# Leibniz-Rechenzentrum	      #
# Zimmer I.2.019	      #
# Boltzmannstra├če 1           #	
# 85748 Garching bei M├╝nchen  #	
###############################


Mime
View raw message