httpd.servlet.logs(4)

NAME | DESCRIPTION | EXAMPLES | ATTRIBUTES | SEE ALSO

NAME

httpd.servlet.logs and httpd.cgi.logs- The log files for servlet requests and CGI script errors.

DESCRIPTION

The httpd.servlet.logs log errors are generated by servlets. You can specify the location of the log files with htservlet or through the Sun^TM WebServer^TM GUI. See htservlet(1m) for details on configuring log settings.

The httpd.cgi.logs log errors are generated by CGI scripts. You can specify the location of the log files through the Sun WebServer GUI.

Log files will be named prefix.sequence, where sequence is a cycling number. Each entry is a Common Log File (CLF) format header indicating the request that launched the servlet or CGI, followed by all error messages generated during the request.

The servlet error logs will have the following format:

{client_name  [DD/MM/YYYY:hh:mm:ss] "request" "vhostname" "script_file_name"} 
error_messages

where error_messages is the error output for the servlet.

The CGI error logs will have the following format:

{client_name  [DD/MM/YYYY:hh:mm:ss] "request" "vhostname" "script_file_name" [block_number]} 
error_messages

where error_messages is the error output for the CGI script, and block_number identifies the block number of the CGI script. The final block from a script also has a keyword "FINAL" at the end of the header. Since Sun WebServer uses constant buffer sizes and many CGI scripts are using the same error log file, it is possible that error messages from a given script are logged into more than one non-adjacent block. If Sun WebServer could log all the error messages from the script into just one block, then it doesn't print either the block number or the keyword FINAL.

The most recent log file can be accessed through the log prefix. If the prefix is /var/http/logs/se_log, then apart from having log files with names /var/http/logs/se_log.1, you will also have a symbolic link called /var/http/logs/se_log, which points to the latest log file that the server is writing.

See httpd.request.logs(4) for a description of the CLF.

EXAMPLES

---

Example 1




Sample CGI error logs:

{129.146.115.80 [14/Mar/1998:11:03:23 -0800] \\
"GET /cgi-bin/login HTTP/1.0" www.A.com /tmp/tp/root1/cgi-bin/login} \\
Invalid number of parameters

{129.146.115.80 [14/Mar/1998:12:03:29 -0800] \\
"GET /cgi-bin/sendfile HTTP/1.0" www.A.com /tmp/tp/root1/cgi-bin/sendfile 1}\\
Unable to open file: /var/http/server/websites/public/profiles/file.1

Output not generated.

{129.146.115.80 [14/Mar/1998:13:03:35 -0800] \\
"GET /cgi-bin/login HTTP/1.0" www.A.com /tmp/tp/root1/cgi-bin/login 2} \\
Authentication failed for user "user1"

---

---

Example 2




Sample servlet error logs:

{120.120.120.120 [07/Nov/1998:15:51:52 -0800] \\
"GET /servlet/security HTTP/1.0" www.A.com /servlet/security} 
cannot exec: exec

{120.120.120.120 [07/Nov/1998:15:51:54 -0800] \\
"GET /servlet/network HTTP/1.0" www.A.com /servlet/network}
cannot open url connection: connect

{120.120.120.120 [07/Nov/1998:15:51:56 -0800] \\
"GET /servlet/remote HTTP/1.0" www.A.com /servlet/remote}
 
com.sun.sws.se.ServletSecurityException: file.read
        at com.sun.sws.se.ServletSecurity.checkRead(ServletSecurity.java:473)
        at com.sun.sws.se.ServletSecurity.checkRead(ServletSecurity.java:427)
        at java.io.FileInputStream.(FileInputStream.java)
        at java.io.FileReader.(FileReader.java)
        at RemoteServlet.service(RemoteServlet.java:22)
        at com.sun.sws.se.ServletHandler.servletService(ServletHandler.java:191)
        at com.sun.sws.se.ServletHandler.handle_servlet_service\\
(ServletHandler.java:258)

{- [07/Nov/1998:15:51:57 -0800] "- - -" - -}
SimpleServlet: init

---

ATTRIBUTES

See attributes(5) for descriptions of the following attributes:

ATTRIBUTE TYPE	ATTRIBUTE VALUE
Availability	SUNWhtsvl
Interface Stability	Evolving

SEE ALSO

htIntro(4), httpd.conf(4), httpd.site.conf(4), httpd.request.logs(4)

Sun WebServer 2.1  Last Revised 22 February 1999

NAME | DESCRIPTION | EXAMPLES | ATTRIBUTES | SEE ALSO