Troubleshooting the uid_sync check

Submit New Article

July 30, 2009 10:00 PM PDT


The uid_sync check verifies that the user and group data is consistent across the cluster.  A user or group present on some nodes but others will cause this check to fail.  Here is an example of how the check reports differences found between nodes:

User and Group Uniformity, (uid_sync)...............................................................FAILED
subtest 'gid = 1313' failed
- failing hosts node00001 - node00128 returned: 'clck:x:1313:'
- failing host node00129 returned: 'group does not exist'
subtest 'uid = 1313' failed
- failing hosts node00001 - node00128 returned: 'clck:x:1313:1313:::cluster checker:/home/clck:/bin/bash'
- failing host node00129 returned: 'user does not exist'

The ID of the user or group is displayed as the subtest description: subtest 'gid = 1313' failed.  The output under the heading identifies the nodes on which the user exists and provides the corresponding entry from the user or group database (e.g., /etc/group or /etc/password). 

This check most often fails when there are mismatches or conflicts with NIS or the local group or user databases.  Depending on the method you employ, you should ensure that NIS is properly configured on the inconsistent node(s) or that the /etc/group and /etc/password files are correctly propagated to the inconsistent node(s). 


Do you need more help?


This article applies to: Intel® Cluster Checker Knowledge Base,   Intel® Cluster Ready Knowledge Base