Oracle HTTP Server Administration Guide Release 2 (9.0.2) Part Number A92173-02 |
|
This chapter discusses the log formats and describes various log files and their locations. Topics include:
LogFormat
specifies the information included in the log file, and the manner in which it is written. The default format is the Common Log Format. The CLF format is: host ident authuser date request status bytes
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 a password-protected site.
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.
bytes
: This is the number of bytes, excluding headers, returned to the client.
The following section describes the function and location of log files.
The server access log 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 contents of the logs.
See Also:
"AccessLog directive" in the Apache Server documentation |
The server records error messages to a log file located, by default, in ORACLE_HOME
/Apache/Apache/logs/error_log
in UNIX, and ORACLE_HOME
\Apache\Apache\logs\error_log
in Windows. The filename can be set using the ErrorLog
directive.
See Also:
"ErrorLog directive" in the Apache Server documentation |
JServ log tracks actions performed, and exceptions generated from JServ applications, such as servlets and JSPs. It is located in ORACLE_HOME
/Apache/Jserv/logs/jserv.log
in UNIX, and ORACLE_HOME
\Apache\Jserv\logs\jserv.log
in Windows.
PID File
When the server is started, it notes the process id of the parent httpd process to the PID file located by, default, in ORACLE_HOME
/Apache/Apache/logs/httpd.pid
. This filename can be changed with the PidFile
directive. The process id is for use by the administrator in restarting and terminating the daemon. If the process dies (or is killed) abnormally, then it will be necessary to kill the children httpd processes.
See Also:
"PidFile directive" in the Apache Server documentation |
Rewrite Log is 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
directive.
See Also:
"RewriteLog directive" in the Apache Server documentation |
Script Log allows you to record the input to and output from the CGI scripts. This should only be used in testing, and not for live servers.
See Also:
"ScriptLog directive" in the Apache Server documentation |
When Oracle HTTP Server starts in SSL mode, it creates ssl_engine_log
and ssl_requrest_log
in ORACLE_HOME
/Apache/Apache/logs
in UNIX, and ORACLE_HOME
\Apache\Apache\logs
in Windows. ssl_engine_log
tracks ssl and protocol issues, where as ssl_request_log
records user activity. Use the SSLLogFile
directive to control output.
Transfer Log specifies the file in which to store the log of accesses to the site. If it is not explicitly included in the conf file, then no log is generated. The server will typically log each request to a transfer file located, by default, in ORACLE_HOME
/Apache/Apache/logs/access_log
in UNIX, and ORACLE_HOME
\Apache\Apache\logs\access_log
in Windows. The filename can be set using a CustomLog
directive.
|
Copyright © 2002 Oracle Corporation. All Rights Reserved. |
|