6027-4209 [E] Unable to contact current cluster manager
Explanation
The CCR is not able to contact the current cluster manager over the daemon network during a file commit, when the cluster is configured with tiebreaker disks. Files committed to the CCR, like the mmsdrfs file, reside only on quorum nodes and not on tiebreaker disks. In order to commit a new version of a file to the CCR, the cluster manager must be reachable over the daemon network, so that the file can be sent to the cluster manager.
The following are the possible reasons for the file commit failure:
- A new cluster manager election process has started but it is not finished when the file is committed to the CCR.
- The cluster manager has access to the tiebreaker disks but it is not reachable by other quorum nodes over the daemon network. In such cases, the cluster manager still responds to challenges written to the tiebreaker disks. However, the file commit fails until the cluster manager is reachable over the daemon network.
User response
- Issue the mmlsmgr -c command to verify whether a cluster manager is elected.
- Verify that either the mmsdrserv daemon or mmfsd daemon is running on the current cluster manager. For example, you can verify this on the Linux® environment by issuing the ps command. If mmsdrserv daemon is running, it indicates that IBM Storage Scale is down and if the mmfsd daemon is running, it indicates that IBM Storage Scale is active on the cluster manager.
- Ensure that the IBM Storage Scale daemon is reachable on the current cluster manager node. To identify the problem, issue the mmhealth node show GPFS -v command or the mmnetverify command as described in the topic Analyze network problems with the mmnetverify command in the IBM Storage Scale: Problem Determination Guide.
