Chapter 4
Monitoring the iPlanet Calendar Server
This chapter describes how to monitor iPlanet Calendar Server activity. It provides examples that show how to obtain server statistics using the most common options for the csstats and cstool command line utilities. For complete details on all the available options, see Appendix A, "Command Line Utilities". It includes the following sections:
Listing Counter Statistics
The csstats utility displays statistical information obtained from counter objects which are defined in the calendar configuration (*.conf) files. Counter objects (such as httpstat, authstat, wcapstat, or dbstat) show information about the iPlanet Calendar Server such as the:
maximum number of concurrent connections and total number of connections
total number of successful and failed logins and connections
number of database reads, writes and deletes
For detailed information on how to interpret iPlanet Calendar Server counter statistics see, Counters.
To view statistical information, use the csstats utility's list command. For example:
To display basic information about the counter objects and the types available, enter the following command:
csstats list
To list statistics specifically about the httpstat counter object, enter:
csstats list http
To list statistics about the wcapstat counter object every 10 seconds for one hour, enter:
csstats -i 360 -s 10 list wcap
Monitoring the iPlanet Calendar Server Log Files
Each calendar service writes status information it's own log file. Each log files is named after its associated service name as described in Table 4-1:
Table 4-1 iPlanet Calendar Server Log Files
|
Service Name
|
Log File name
|
|
csadmind
|
admin.log
|
|
csdwpd
|
dwp.log
|
|
cshttpd
|
http.log
|
|
csnotifyd
|
notify.log
|
The log files are stored in their own log directory:
On Solaris, the default is:
- /var/opt/SUNWics5/logs
On Unix systems other than Solaris, the default is:
- /var/opt/iPlanet/CalendarServer5/logs
On Windows NT, the default is:
- c:\Program Files\iPlanet\CalendarServer5\var\logs
Each log file is rolled-over to a new log file with a new name based on the configured time and size limits as follows:
<ServiceName>.<TimeStamp>.<#>
For example, admin.20000801115354 .1, http.20000801115354 .2, and etc.
Log Event Severity Levels
iPlanet Calendar Server provides eight levels of severity for events reported to the log files as described in Table 4-2.
Table 4-2 iPlanet Calendar Server Log Error Severity Levels
|
Severity Level
|
Meaning
|
|
EMERGENCY
|
System is unusable. This level indicates events with the highest (most critical) severity.
|
|
ALERT
|
Action must be taken immediately.
|
|
CRITICAL
|
Critical condition.
|
|
ERROR
|
Error conditions.
|
|
WARNING
|
Warning conditions.
|
|
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 time stamp, server host name, severity level, process name (process ID), type of event, priority, and description. You can specify the level of severity of the events that Calendar Server reports to the log files by modifying certain configuration settings in the ics.conf file. For more information, see Calendar Log Information Configuration.
The log files should be inspected on a regular basis for EMERGENCY, ALERT, CRITICAL, ERROR, and WARNING level errors and, if found, these events should be examined for possible problems with the operation of the Calendar Server. The NOTICE and INFORMATION level log events are generated during normal operation of the Calendar Server and are provided to help you monitor server activity.
|
Note
|
When requesting technical support for Calendar Server, you may be asked to provide the log files for help in resolving problems.
|
Pinging the iPlanet Calendar Server
Use cstool utility's ping command to verify that a iPlanet Calendar Server service is listening on a specified port number. (Pinging a service does not verify that a service is actually running, but indicates if it can accept a socket connection.) The service options are:
admin (csdamind service)
dwp (csdwpd service)
ens (enpd service)
http (cshttpd service) — the default if a service is not specified
notify (csnotifyd service)
For example, to ping the cshttpd service to verify it is listening on port 80, enter the following command:
cstool -p 80 ping http
where:
-p 80 is the port number the Calendar Server listens to by default.
calserver is the host name of the machine on which Calendar Server is installed
.
|
Note
|
The Calendar Server must be running in order to run cstool.
|
Refreshing the iPlanet Calendar Server Configuration
Use cstool utility's refresh command to force a Calendar Server service to refresh its configuration. For example, to command the cshttpd service to refresh it's configuration, enter the following command:
cstool refresh
|
Note
|
The Calendar Server must be running in order to run cstool.
|