Troubleshooting mmwatch

This topic contains information for troubleshooting clustered watch folder.

Use the following log names and locations to troubleshoot mmwatch:

/var/adm/ras/mmwatch.log contains information about the setup and configuration operations that affect the clustered watch while in process. Valid on any node that is running the clustered watch command or location where the conduit might be running.
/var/adm/ras/mmwfclient.log contains information about clustered watch folder connections.
/var/adm/ras/mmfs.log.latest is the daemon log. It contains entries when major cluster watch activity occurs.
/var/log/messages (Red Hat®) or /var/log/syslog (Ubuntu) also might contain messages from the producer and consumers that are running on a node.

It can take up to 10 minutes for system health to refresh the clustered watch folder components. This means that the accurate state of a watch might not be reflected until 10 minutes after an event is sent. If the states of the watch is FAILED, then the mmhealth node show --refresh -N all command can be used to force an update of the states.
When you view the configuration with mmwatch all list, the output might show the incomplete state in one of the fields. The incomplete state means that a disable operation did not complete successfully. To remedy this, you can attempt to disable it again.