Centrify

Tips for finding Knowledge Articles

  • - Enter just a few key words related to your question or problem
  • - Add Key words to refine your search as necessary
  • - Do not use punctuation
  • - Search is not case sensitive
  • - Avoid non-descriptive filler words like "how", "the", "what", etc.
  • - If you do not find what you are looking for the first time,reduce the number of key words you enter and try searching again.
  • - Minimum supported Internet Explorer version is IE9
Home  >
article

KB-1557: rsyncd errors regarding nss.uid.ignore, nss.gid.ignore

Centrify DirectAudit ,   Centrify DirectControl ,   Centrify Identity Service, Mac Edition ,  

12 April,16 at 11:13 AM

Applies to:  All versions of Centrify DirectControl for UNIX/Linux on all platforms

Question:

The following errors were shown when using rsyncd in cron job even though the files /etc/centrifydc/uid.ignore and /etc/centrifydc/gid.ignore exist. Is there any way to eliminate the error?

host1 rsyncd[2050]: ERROR: Failure in list match for key 'nss.uid.ignore' from file '/etc/centrifydc/centrifydc.conf': file does not exist
host1 rsyncd[2050]: ERROR: Failure in list match for key 'nss.gid.ignore' from file '/etc/centrifydc/centrifydc.conf': file does not exist

Answer:

rsyncd does chroot which means it will not be able to talk to adclient and open socket to adclient.

To eliminate the error, set "use chroot = false" (default is true) in rsyncd.conf.

You can find more information on 'use chroot' in man pages of rsync that explain in more details regarding its usage.

Still have questions? Click here to log a technical support case, or collaborate with your peers in Centrify's Online Community.

Related Articles

 articleKB-4698: hadoop fs -ls /user commands fails with error message articleKB-4589: Error codes when installing SQL server bundled with Centrify DirectAudit and Centrify Reporting Services articleKB-6073: How to join the Linux/Unix Centrify Server to Active Directory with specific Computer Role? articleKB-6041: How to show current license type in use by adclient? articleKB-5964: Sync failure when user account UPN changes to a different federated domain articleKB-6040: How to change the license type in use after adclient successful joined to the AD? articleKB-6180: Troubleshooting SSH Connection Problems Preauth articleKB-6056: How to report the group policy settings that are in effect for the local computer? articleKB-6038: How to specify the license type to use when joining the server to AD using adjoin?