httpd.event.logs(4)

NAME | SYNOPSIS | DESCRIPTION | EXAMPLES | ATTRIBUTES | SEE ALSO | NOTES

NAME

httpd.event.logs- Description of the Events Log files.

SYNOPSIS

/var/adm/messages

DESCRIPTION

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.

Syntax

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 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:

time

The date and time (in the format: MMM DD hh:mm:ss) that the error occurred.

host

The node name of the host (uname --n).

tag [pid]

A tag and a pid form the framework for error messages from user space. The tag reveals which Sun^TM WebServer^TM 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 preceeded by "sws". The pid contains the process id of the process that generated the error message.

version

The version of the error message format.

message_id

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.

seq_no

A sequence number determines the exact sequence of error messages in the log. This field is always "0" for Sun WebServer.

source

This field contains the source of the error. The source is always "SW" for Sun WebServer.

severity

The errors can be one of four severity levels:

CRITICAL

Critical condition such as failure to daemonize.

ERROR

Error conditions such as server being unable to bind to port. Error conditions cause a significant part of the server to fail.

WARNING

Warning conditions such as being unable to write to a log file. Warning conditions do not prevent the server from running.

NOTICE

Normal but significant conditions. May require special handling.

message

The actual text of the message.

EXAMPLES

---

Example 1




Sample event log entries:

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

---

ATTRIBUTES

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

ATTRIBUTE TYPE	ATTRIBUTE VALUE
Availability	SUNWhttp
Interface Stability	Evolving

SEE ALSO

syslogd(1m), syslog.conf(4)

NOTES

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

---

Note -

The whitespace 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  Last Revised 17 July 1998

NAME | SYNOPSIS | DESCRIPTION | EXAMPLES | ATTRIBUTES | SEE ALSO | NOTES