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-2468: adfixid --restart fails

Authentication Service ,  

12 April,16 at 11:09 AM

Applies to: All versions of Centrify DirectControl
 
Question:
 
The Centrify CLI adfixid --restart command is not working as expected. 
 
It worked originally when an initial test was run, but restart only fixed the files that had changed since last time. 
 
The data is resynced (rsync) over to the Raid assuming that it would just do a --restart and re-run the command. A groupmap file is used. The original run updated over 660,000 files, then only updated about 138,000 files, and it will continue running. Even when run on a specific folder, it does nothing (after --restart). 
 
The commands used: 
 
#adfixid --commit --groupmap ./mapfile-hhcc.txt /color 
#adfixid --restart 
 
The below commands were also attempted.
 
#adfixid --restart --groupmap ./mapfile-hhcc.txt /color 
#adfixid -R --groupmap ./mapfile-hhcc.txt /color 
 
adfixid was also attempted on a subfolder of /color, but made no difference. 
It still doesn't change the group permissions even though a non-commit run shows the correct mapping conflicts. 
 
Is there any reason for this?
 
Answer:
 
adfixid will not do "the commit or a commit all" as the CLI only restarts where it left off & will simply report that it found conflicts. This is by design. 
If --restart flag still wants to be used, the journal which adfixid uses to keep track will need to be removed.
 
The location of the file is /etc/centrifydc/adfixid.log.
 
adfixid -V --restart >& /home/napc/CENTRIFY/Restart-post.out 
 
-------------------- 
commit: false 
commitAll : false 
reportFiles: 0 
userMapFile: 0 
groupMapFile: 0 
newIDRange: 50000 ..60000 
follow: false 
xdev: false 
restart: true 
undo: false 
debug: false 
verbose: true 
directories (1) 

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

Related Articles

 articleKB-6041: How to show current license type in use by adclient articleKB-6073: How to join the Linux/Unix Centrify Server to Active Directory with specific Computer Role? articleKB-6040: How to change the license type in use after adclient successful joined to the AD? 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? articleKB-7555: Unable to login as root after upgrade to Centrify Suite 2016 (CDC 5.3.0) articleKB-20210: Common Questions Regarding Centrify DirectControl and CoreOS articleKB-5793: AIX hosts in 'down' mode running Centrify DirectControl 5.0.2, stop and restart failed articleKB-14300: Centrify NIS Service Fails and Cannot be Restarted by niswatch Daemon