NAME | SYNOPSIS | DESCRIPTION | EXAMPLES | ATTRIBUTES | SEE ALSO | NOTES
/var/adm/messages
The httpd server puts out error messages and warnings via syslogd(1m) to /var/adm/messages by default. Use /etc/syslog.conf to change the default location.
The definitions in the httpd.event.logs file have the following format:
<time> <host> sws.<instance>[pid]: [<version> <message_id> <seq_no> (<source>) <severity>]: <message>
Errors sent to the screen before the daemon has been created or started are sent in console format. The format of the messages written to the console will be:
<message_id> <time> <severity>: <message>
The following keyword directives are valid in the httpd.event.logs file:
The date and time (in the format: MM DD hh:mm:ss) that the error occurred.
The node name of the host (uname --n).
A tag and a PID form the framework for error messages from user space. The tag reveals which SunTM WebServerTM daemon logged the message. The instance name spans multiple starts and stops of a single server. The tag contains the instance name of the server preceded by "sws". The PID contains the process ID of the process that generated the error message.
The version of the error message format.
The unique identifier for the error message with the form modulename.id_number. The modulename refers to a shared object or to a subsystem in the httpd daemon code. The id_number mirrors the message catalog number.
A sequence number determines the exact sequence of error messages in the log. This field is always "0" for Sun WebServer.
This field contains the source of the error. The source is always "SW" for Sun WebServer.
The errors can be one of four severity levels:
Critical condition such as failure to daemonize.
Error conditions such as server being unable to bind to port. Error conditions cause a significant part of the server to fail.
Warning conditions such as being unable to write to a log file. Warning conditions do not prevent the server from running.
Normal but significant conditions. These may require special handling.
The actual text of the message.
May 17 15:39:10 hostname sws.admin[14454]: [1 httpd.134 0 (SW) NOTICE]: \\ Received a SIGHUP signal; restarting the server. May 17 15:39:10 hostname sws.admin[14454]: [1 admin.195 0 (SW) NOTICE]: \\ Running with SWS Configuration file \\ "/usr/http/admin_server/conf/admin.httpd.conf". May 18 15:35:33 hostname sws.Secure_Sites[15257]: [1 net.61 0 (SW) WARNING]: \\ Network interface 129.146.146.25 is not configured on this host. May 18 15:35:33 hostname sws.Secure_Sites[15257]: [1 net.183 0 (SW) ERR]: \\ httpd cannot bind to any configured port May 18 15:36:49 hostname sws.Large_Sites[15077]: \\ [1 servlet.231 0 (SW) WARNING]: Servlets not allowed in this server.\\ The specified servlet-engine block in virtual host www.A.com will be ignored
See attributes(5) for descriptions of the following attributes:
ATTRIBUTE TYPE | ATTRIBUTE VALUE |
Availability | SUNWhttp |
Interface Stability | Evolving |
htIntro(4), syslogd(1m), syslog.conf(4)
To ensure that all Sun WebServer messages are logged by syslogd(1m), create an entry for daemon.notice
messages in syslog.conf(4).
For example, to log Sun WebServer messages to /var/adm/messages, create the following entry:
daemon.notice /var/adm/messages
The white space between the message type and the file name consists only of tabs.
This entry would cause all messages with a severity of "notice" or greater generated by any daemon process to be logged to /var/adm/messages.
Sun WebServer 2.1 Last Revised 22 February 1999NAME | SYNOPSIS | DESCRIPTION | EXAMPLES | ATTRIBUTES | SEE ALSO | NOTES