Sun Microsystems Netscape Enterprise Server, Руководство администратора

Страница: 185 / 532

Chapter 8, Understanding Log Files 185
Viewing the Error Log File
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 189 for more information):
wiley.a.com - - [25/Mar/1999:12:55:26 -0800] "GET /index.htm HTTP/1.0" "GET" "/?-" "HTTP/
1.0" 304 0 - Mozilla/2.0 (WinNT; I)
wiley.a.com - - [25/Mar/1999:12:55:26 -0800] "GET / HTTP/1.0" "GET" "/?-" "HTTP/1.0" 304 0
- Mozilla/2.0 (WinNT; I)
wiley.a.com - - [25/Mar/1999:12:55:26 -0800] "GET / HTTP/1.0" "GET" "/?-" "HTTP/1.0" 304 0
- Mozilla/2.0 (X11; I; IRIX 5.3 IP22)
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.
To view the Enterprise Administration Server’s error log file, from Enterprise
Administration Server, choose the Preferences tab, and choose the View Error
Log page.
Table 8.1 The fields in the last line of the sample access log file
Access Log Field Example
Hostname or IP address
of client arrow.a.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 information - (RFC 931 identity not implemented)
Username john (username entered by the client for authentication)
Date/time of request 29/Mar/1999:4:36:53 -0800
Request GET /help
Protocol HTTP/1.0
Status code 401
Bytes transferred 571