File: apache-6.html

package info (click to toggle)
linuxconf 1.26r4-2
  • links: PTS
  • area: main
  • in suites: woody
  • size: 56,432 kB
  • ctags: 27,217
  • sloc: cpp: 158,803; perl: 7,484; sh: 4,134; java: 3,105; ansic: 2,492; makefile: 2,216; python: 109
file content (33 lines) | stat: -rw-r--r-- 1,211 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
 <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
 <TITLE>Apache Web Server: Error log</TITLE>
 <LINK HREF="apache-7.html" REL=next>
 <LINK HREF="apache-5.html" REL=previous>
 <LINK HREF="apache.html#toc6" REL=contents>
</HEAD>
<BODY>
<A HREF="apache-7.html">Next</A>
<A HREF="apache-5.html">Previous</A>
<A HREF="apache.html#toc6">Contents</A>
<HR>
<H2><A NAME="s6">6. Error log</A></H2>

<P>The path to the log file for error messages.  Usually, it is
<CODE>logs/error_log</CODE>, which is relative to the ServerRoot.  Often the
directory <CODE>logs</CODE> in ServerRoot is a symbolic link to
<CODE>/var/log/httpd</CODE>.  Then the log path above would result in error
messages being logged to <CODE>/var/log/httpd/error_log</CODE>.
<P>You should monitor this log after reconfiguring, since most
configuration errors are logged here (Linuxconf, sadly, catches
only a few of them.)  Additionally, any failed accesses by
clients (non-existent pages, failed authorization and so on)
are also logged here.
<P>
<HR>
<A HREF="apache-7.html">Next</A>
<A HREF="apache-5.html">Previous</A>
<A HREF="apache.html#toc6">Contents</A>
</BODY>
</HTML>