Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: pass (nike.apache.org: local policy)
From: Stefan Fritsch <sf@sfritsch.de>
To: dev@httpd.apache.org
Subject: Re: no http-404 errors in ErrorLog
Date: Thu, 7 Feb 2013 21:54:42 +0100
User-Agent: KMail/1.13.7 (Linux/3.2.0-4-amd64; KDE/4.8.4; x86_64; ; )
References: <51138F69.3040708@thelounge.net>
In-Reply-To: <51138F69.3040708@thelounge.net>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: 7bit
Message-Id: <201302072154.42968.sf@sfritsch.de>

On Thursday 07 February 2013, Reindl Harald wrote:
> ErrorLog "/var/log/apache_error.log"
> LogLevel info
> 
> https://issues.apache.org/bugzilla/show_bug.cgi?id=35768
> 
> what is here "fixed in 2.4.1"?
> httpd-2.4.3 does not log 404 errors in ErrorLog
> 
> imagine admins like me with some hundret vhosts and all
> of the systems and templates are developed inside the
> own company - fine with httpd-2.4 you have to grab in
> each access-log to see typos - that is impossible
> 
> the "opening for a denial of service attack on the disk
> space of the server" is simply borked because the same
> would affect CustomLog and if you do not want 404 in
> the ErrorLog use a higher LogLevel
> 
> additionally if your server allows a DOS to the disk
> space from single client-IPs you should consider
> learning to use rate-controls in front of the httpd

The level was changed to info, because the gazillions of error log 
entries caused by bots and missing favicon.ico files were not 
considered to be very valuable.

Switching the loglevel to info works for me:

$ grep exist /usr/local/Apache2.4/logs/error_log
[Thu Feb 07 21:42:31.161127 2013] [core:info] [pid 6545:tid 
4111465328] [client 127.0.0.1:50447] AH00128: File does not exist: 
/usr/local/Apache2.4/htdocs/foobar

$ grep -i loglevel /usr/local/Apache2.4/conf/httpd.conf
# LogLevel: Control the number of messages logged to the error_log.
LogLevel info


If you can provide a simple example config that sets the loglevel for 
core to info but does not log these messages, please file a (new) PR 
in bugzilla.


As a workaround, you may want to look at mod_log_debug's LogMessage. 
That can do logging conditional on the status and also catches cases 
where some modules set the status to 404 without logging something to 
the error log.