6
Configuring and Using Server Logs< /font>

• host: This is the client domain name or its IP number.
• ident: If IdentityCheck is enabled and the client machine runs identd, then this is the client identity information.
• authuser: This is the user ID for authorized user.
• date: This is the date and time of the request in the <day/month/year:hour:minute:second> format.
• request: This is the request line, in double quotes, from the client.
• status: This is the three-digit status code returned to the client.< /li>
• bytes: This is the number of bytes, excluding headers, returned t o the client.

Specifying Log Level

Table& nbsp;6-3 lists all the different logging levels, their descriptions, and, example messages:

Table 6-3 Logging Level

Specifying Log Files

The log files are discussed in the sub sequent sections:

• Access Log
• CustomLog
• Error Log
• PID File
• Piped Log
• Rewrite Log
• Script Log
• SSL Log
• Transfer Log

It is important to periodically rotate the log files by moving or deleting existing log s on a moderately busy server. For this, the server must be restarted after the log files are moved or deleted so that new log files are opened.

Access Log

The server access l og records all requests processed by the server. The location and content of the access log is controlled by the CustomLog directive. The LogFormat directive can be used to simplify the selection of the con tents of the logs.

CustomLog

The Cust omLog directive is used to log requests to the server. A log format is specified, and the logging can optionally be made condi tional on request characteristics using environment variables.

< a name="1006109">

Error Log

The server sends diagnostic information and records error messages to a log file located, by default, in:

• UNIX: ORACLE_ HOME/Apache/Apache/logs/error_log
• Windows: ORACLE_HOME\Apache\Apache\logs\error_log

The file name can b e set using the ErrorLog directive.

PID File

When the server is started, it not es the process ID of the parent httpd process to the PID file located by, default, in

• UNIX: ORACLE_HOME/Apache/Apache/logs/httpd.pid
• Windows: ORACLE_HOME\Apache\Apache\logs\httpd.pid

This filename can be changed with the PidFile directive. T he process ID is for use by the administrator for restarting and terminating the daemon. If the process dies (or is killed) abnormall y, then it is necessary to kill the children httpd processes.

Piped Log

Oracle HTTP Server is capable of writing error and access log files through a pipe to another process, r ather than directly to file. This increases the flexibility of logging, without adding code to the main server. In order to write log s to a pipe, replace the file name with the pipe character "|", followed by the name of the executable which should accept log entrie s on its standard input. Oracle HTTP Server starts the piped-log process when the server starts, and restarts it if it crashes while the server is running.

Rewrite Log

Rewrite Log i s necessary for debugging when mod_rewrite is used. This log file produces a detailed analysis of how the rewriting engine transforms requests. The level of detail is controlled by the RewriteLogLevel dire ctive.

Script Log

Script Log enables you to record the input to and output from the CGI scripts. This should only be used in testing, and not for live servers.

SSL Log

When Oracle HTTP Server starts in SSL mode , it creates ssl_engine_log and ssl_request_log in

• UNIX: ORACLE_HOME/Apache/Apache/logs
• Windows: ORACLE_HOME\Apache\Apache\logs