From c8de086646f905d0f192560a53fdfd23b4c69a62 Mon Sep 17 00:00:00 2001
From: Rich Bowen syslog
or pipe them to a
program.
The default format of the error log is relatively free-form and - descriptive. But there is certain information that is contained - in most error log entries. For example, here is a typical - message.
+The format of the error log is defined by the ErrorLogFormat
directive, with which you
+ can customize what values are logged. A default is format defined
+ if you don't specify one. A typical log message follows:
- [Wed Oct 11 14:32:52 2000] [error] [client 127.0.0.1]
- client denied by server configuration:
- /export/home/live/ap/htdocs/test
+ [Fri Sep 09 10:42:29.902022 2011] [core:error] [pid 35708:tid 4328636416]
+ [client 72.15.99.187] File does not exist: /usr/local/apache2/htdocs/favicon.ico
The first item in the log entry is the date and time of the
- message. The second item lists the severity of the error being
- reported. The LogLevel
- directive is used to control the types of errors that are sent
- to the error log by restricting the severity level. The third
- item gives the IP address of the client that generated the
- error. Beyond that is the message itself, which in this case
- indicates that the server has been configured to deny the
- client access. The server reports the file-system path (as
- opposed to the web path) of the requested document.
A very wide variety of different messages can appear in the
error log. Most look similar to the example above. The error
@@ -135,9 +131,7 @@
information written to stderr
by a CGI script will
be copied directly to the error log.
Using the ErrorLogFormat
- directive, you can customize the format of the error log, and what
- values are logged. If you have mod_unique_id
, you
+
If mod_unique_id
is loaded, you
can put a %L
token in both the error log and the access
log, producing a log entry ID with which you can correlate the entry
in the error log with the entry in the access log.
syslog
or pipe them to a
program.
- The default format of the error log is relatively free-form and - descriptive. But there is certain information that is contained - in most error log entries. For example, here is a typical - message.
+The format of the error log is defined by the
The first item in the log entry is the date and time of the
- message. The second item lists the severity of the error being
- reported. The
A very wide variety of different messages can appear in the
error log. Most look similar to the example above. The error
@@ -140,9 +137,7 @@
information written to stderr
by a CGI script will
be copied directly to the error log.
Using the
If %L
token in both the error log and the access
log, producing a log entry ID with which you can correlate the entry
in the error log with the entry in the access log.