Monitoring clustered watch folder with the mmhealth command
Use the following information to monitor clustered watch folder with the mmhealth command.
To see the active status on a watch in mmhealth, use the mmhealth
node show
command:
mmhealth node show
Node name: node1.ibm.com
Node status: HEALTHY
Status Change: 1 day ago
Component Status Status Change Reasons
-------------------------------------------------------------------------
GPFS HEALTHY 1 day ago -
NETWORK HEALTHY 1 day ago -
FILESYSTEM HEALTHY 5 hours ago -
CES HEALTHY 1 day ago -
GUI HEALTHY 1 day ago -
PERFMON HEALTHY 1 day ago -
THRESHOLD HEALTHY 1 day ago -
WATCHFOLDER HEALTHY 1 day ago -
This command displays the current state
of the watch folder components on the defined node.To see the status across the cluster, use the mmhealth cluster show
command:
mmhealth cluster show
Component Total Failed Degraded Healthy Other
---------------------------------------------------------------------------------------------------
NODE 4 0 2 0 2
GPFS 4 0 1 0 3
NETWORK 4 0 0 4 0
FILESYSTEM 3 0 0 3 0
DISK 6 0 0 6 0
CES 2 0 1 1 0
CESCLUSTER 1 0 0 1 0
GUI 1 0 1 0 0
PERFMON 4 0 0 4 0
THRESHOLD 4 0 0 4 0
WATCHFOLDER 4 0 0 4 0
You can then see a more verbose status of the health with the mmhealth node show
watchfolder -v
command:
# mmhealth node show watchfolder -v
Node name: node1.ibm.com
Component Status Status Change Reasons
-----------------------------------------------------------------------------------------------------------------
WATCHFOLDER HEALTHY 2019-03-19 16:50:57 -
gpfs0/13222185860284578504/CLW1553028625 HEALTHY 2019-03-19 16:50:57 -
Event Parameter Severity Active Since Event Message
--------------------------------------------------------------------------------------------------------------
watchfolder_service_ok gpfs0/13222185860284578504/ INFO 2019-03-19 16:50:57 Watchfolder service is running.
CLW1553028625
watchfolderp_ok gpfs0/13222185860284578504/ INFO 2019-03-19 16:50:57 Event producer for file system
CLW1553028625 gpfs0 is ok.