Table of Contents
Facility Administration and Message Logging
Facility Administration and Message Logging
This section describes Resource Manager facilities and explains how and where messages are logged. Resource Manager log messages are written to the syslog facility. Resource Manager debugging messages are written to the /var/adm/CSCOpx/log/daemons.log file. This chapter includes the following sections:
Syslog Facility
Resource Manager uses a syslog facility (0 to 7) for storing log messages. By default, all router log messages are written to local7 by Cisco routers. Resource Manager uses the first unused facility in the range local0 through local6 to store log messages. If an unused syslog facility cannot be found at the time of installation, the Resource Manager installation tool stops the installation and gives you the option to abort or to specify which syslog facility to use for storing log messages.
Error Message Storage
Resource Manager error messages are written to the /var/adm/CSCOpx/log/dmgtd.log file. Because messages are continuously added to this file, you might want to occasionally copy this file to a different name, compress it, and empty dmgtd.log.
Debugging messages from Resource Manager back end processes are written to the /var/adm/CSCOpx/log/daemons.log file. This file is cleared every time you restart Resource Manager. If you encounter any problems with Resource Manager, these messages will be valuable in debugging the problem. See Appendix A, "Troubleshooting," for more information about debugging error messages.
Scheduling Scheme
Process Status
Any Resource Manager user can view the status of any process by clicking Admin, then selecting System Admin > Process Status. Only Resource Manager users with administrator privileges can start and stop processes.
If you have administrator privileges, you can view the status of back end processes by clicking Admin > System Admin. Table 4-1 lists possible back end processes and their expected status.
Table 4-1: Back End Process Status
| Process Name | Process Description | State |
|---|---|---|
|
DbServer |
Data storage engine |
Running normally |
|
DIServer |
Import server |
Running normally |
|
diskWatcher |
Disk space monitor |
Running normally |
|
AvInputGen |
Availability daemon |
Running normally |
|
AvIcmpPoller |
Availability ICMP1 poller |
Running normally |
|
AvSnmpPoller |
Availability SNMP2 poller |
Running normally |
|
AvLoader |
Availability daemon |
Running normally |
|
IcServer |
Availability collector |
Running normally |
|
SyslogAnalyzer |
Syslog message analyzer |
Running normally |
|
WebServer |
http server |
Running normally |
| 1ICMP=Internet Control Message Protocol 2SNMP=Simple Network Management Protocol |
Table 4-2 describes what each process (or daemon) state means.
Table 4-2: Process Status Defined
| State | Definition |
|---|---|
|
Never started |
The process is not configured for autostart. The process must be started manually. |
|
Program started - No mgt msgs received |
The process has started, but the status has not been reported to the Daemon Manager. |
|
Running normally |
The process is successfully started and reporting status to the Daemon Manager. |
|
Failed to run |
The process has failed by exiting or sending a failed init message. |
|
Administrator has shut down this server |
The administrator or another program has shut down the process. |
|
Transient terminated |
The process has completed its function and has terminated normally. |
|
Running but busy flag set |
The process is successfully started, but does not participate in process management messaging. |