Viewing The Error Log File - Netscape ENTREPRISE SERVER 6.1 - 08-2002 ADMINISTRATOR Administrator's Manual

Table 9-1
Access Log Field
Hostname or IP address of
client
RFC 931 information
Username
Date/time of request
Request
Protocol
Status code
Bytes transferred
The following is an example of an access log using the flexible logging format (you
specify the format in the Log Preferences page; see "Setting Log Preferences" on
page 212 for more information):
wiley.example.com - frank [27/Mar/2002:00:20:49 -0800] "GET /cgi-bin/Worth.pl
HTTP/1.1" 200 1292 "-" "Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9+)
Gecko/20020308"
192.168.0.1 - - [27/Mar/2002:02:30:59 -0800] "GET /pogues/ HTTP/1.0" 302 0 "-"
"Mozilla/5.0 (Macintosh; U; PPC; en-US; rv:0.9.2) Gecko/20010726 Netscape6/6.1
OmniWeb/4.1-v374"
coyote.example.com - - [27/Mar/2002:02:31:01 -0800] "GET /Images/mozilla2.gif
HTTP/1.1" 200 4372 "http://www.example.com/" "Mozilla/5.0 (Macintosh; U; PPC;
en-US; rv:0.9.2) Gecko/20010726 Netscape6/6.1 OmniWeb/4.1-v374"

Viewing the Error Log File

The error log file contains errors the server has encountered since the log file was
created; it also contains informational messages about the server, such as when the
server was started. Unsuccessful user authentication is also recorded in the error
log. Use the error log to find broken URL paths or missing files.
The fields in the last line of the sample access log file
Example
arrow.example.com. (In this case, the hostname is shown
because the web server's setting for DNS lookups is
enabled; if DNS lookups were disabled, the client's IP
address would appear.
- (RFC 931 identity not implemented)
john (username entered by the client for authentication)
29/Mar/2002:4:36:53 -0800
GET /help
HTTP/1.0
401
571
Viewing the Error Log File
Chapter 9 Using Log Files 209