Start performance monitoring collector service
The collector services on the GUI node must be functioning properly to display the performance data in the IBM Storage Scale management GUI.
The following are the corresponding event details and the proposed solution:
- Event ID: pmcollector_down
- Limitation: This DMP is not available in sudo wrapper clusters when a remote pmcollector service is used by the GUI. A remote pmcollector service is detected in case a different value than localhost is specified in the ZIMonAddress in file, which is located at: /usr/lpp/mmfs/gui/conf/gpfsgui.properties. In a sudo wrapper cluster, the user name is different from 'root'. The system detects the user name by finding the parameter GPFS_USER=<user name>, which is available in the file /usr/lpp/mmfs/gui/conf/gpfsgui.properties.
- Problem: The performance monitoring collector service pmcollector is in inactive state.
- Solution: Issue the systemctl status pmcollector to check the status of the collector. If pmcollector service is inactive, issue systemctl start pmcollector.
The system restarts the performance monitoring services by issuing the systemctl restart pmcollector command.
The performance monitoring collector service might be on some other
node of the current cluster. In this case, the DMP first connects
to that node, then restarts the performance monitoring collector service.
ssh <nodeAddress> systemctl restart pmcollector
For example: ssh 10.0.100.21 systemctl restart pmcollector
In a sudo wrapper cluster, when collector on remote node is down, the DMP does not restart the collector services by itself. You need to do it manually.