Each Calendar Server service writes status information to its own log file. Each log file is named after its associated service name, as shown in the following table:
Service Name |
Log File Name |
---|---|
Administration Service (csadmind) |
admin.log |
Distributed Database Service (csdwpd) |
dwp.log |
HTTP Service (cshttpd) |
http.log |
Notification Service (csnotifyd) |
notify.log |
Single Sign-on log |
am_sso.log |
Log of start commands |
start.log |
Log of stop commands |
stop.log |
Log of store commands |
store.log |
Calendar Server log files are stored in the following default directory:
/var/opt/SUNWics5/logs
Each log file is rolled-over to a new log file identified by a unique number. For example:
admin.log.8.1083013284 http.log.8.1083013284
Calendar Server provides six levels of severity for events reported to the log files as described in the following table. You can specify the level of severity of the events that Calendar Server reports to the log files by modifying the ics.conf parameter logfile.loglevel.
Severity Level |
Meaning |
---|---|
CRITICAL |
Critical condition. |
ERROR |
Error condition. |
WARNING |
Warning condition. |
NOTICE |
Normal, but signification condition. This is the default reporting level for each calendar service. |
INFORMATION |
Informational. |
DEBUG |
Debug-level message. |
A log event is represented by a single line that shows the associated timestamp, server host name, severity level, process name (process ID), type of event, priority, and description.
For information regarding the ics.conf log settings, see Appendix E, Calendar Server Configuration Parameters.