ITEM

STATUS

NODE_NAME

NAME

Subnet

unknown

nynode1

195.14.171.0

Subnet

unknown

nynode2

195.14.171.0

Node_Switching_Parameters:

 

NODE_TYPE

STATUS

SWITCHING

NAME

Primary

down

 

nynode1

Alternate

down

 

nynode2

Use the ps command to check for the status of the Continentalclusters monitor daemons cmclrmond and cmclsentryd, which should be running on the cluster node where the monitor package is running.

Reviewing Messages and Log Files

The Continentalclusters commands—cmquerycl, cmcheckconcl, cmapplyconcl, and cmrecovercl—all display messages on the standard output, which is the first place to look for error messages.

All notification messages associated with cluster events are reported in /var/opt/resmon/log/ cc/eventlog on the cluster where monitoring is taking place. An example of output from this file follows:

>-----

Event Monitoring

Service Event Notification ------------

<

Notification

Time: Wed

Nov

10 21:00:39 1999

 

system1 sent

Event Monitor

notification information:

 

/cluster/concl/ccluster1/clusters/LAclust/status/unreachable is =

15

User Comments:

 

 

Cluster "LAclust" has status "unreachable" for 15 sec

 

 

>-----

End Event Monitoring Service Event Notification ----------

<

 

In addition, if you have defined a TEXTLOG destination, notification messages are sent to the file that were specified. (See “Editing Section 3—Monitoring Definitions” (page 82) for more information.)

Also review the monitor startup and shutdown log file /etc/cmcluster/ccmonpkg/ ccmonpkg.cntl.log on any node where a Continentalclusters monitor has been running. Information about the primary or recovery packages may be found in their respective startup and shutdown log files.

If you are using modular monitoring package, then the package log file is the value specified by the script_log_file parameter.

Messages from the Continentalclusters daemon are reported in log file /var/adm/cmconcl/ sentryd.log, and Object Manager messages appear in /var/opt/cmom/cmomd.log. These messages may be helpful in troubleshooting. Use the cmreadlog command to view the entries in these files. Examples:

#/opt/cmom/tools/bin/cmreadlog -f /var/adm/cmconcl/sentryd.log slog.txt

#/opt/cmom/tools/bin/cmreadlog -f /var/opt/cmom/cmomd.log \ omlog.txt

The following is sample output from the cmreadlog command for the sentryd.log file:Oct

20 18:28:22:[[main,5,main]]:FATAL:dr.sentryd:No Continentalclusters found on this node.Oct 22 13:38:45:[[Thread-309,5,main]]:ERROR:dr.sentryd:Error connecting to axe28Oct 22 13:38:45:[[Thread-309,5,main]]:ERROR:dr.sentryd:Connection refusedOct 22 13:38:45:[[Thread-309,5,main]]:INFO:dr.sentryd:Connection failed to axe28Oct 22 13:38:45:[[Thread-311,5,main]]:ERROR:dr.sentryd:Cannot find cluster KC-cluster at location axe29Oct 22 13:38:45:[[Thread-311,5,main]]:ERROR:dr.sentryd:null result from query

General information about Serviceguard operation is found in /var/adm/syslog/syslog.log.

Maintaining Continentalclusters 111