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-5941: How to use Diagnostic Tool to collect logs in 5.2.4

12 April,16 at 11:44 AM

Applies to: Centrify DirectControl for Mac 5.2.4

Question:

Due to the changes made for Apple's System Integrity Protection feature in OS X 10.11, the Mac Diagnostic Tool may miss some files when packing up a Full Log Pack.
How can it be ensured that the Diagnostic Tool will collect all the needed files?


Answer:

Option 1:


This issue only affects the operation of the [ 2. Save Debug Log files to Desktop ] button in the Diagnostic Tool.
As workaround, instead of pushing the "Save Debug Log files..." button, use the following Terminal command to pack up the logs instead:
  • sudo /usr/local/share/centrifydc/bin/cdcdebug -f pack john.doe 
  • adquery user -A john.doe > /tmp/adquery.log 
(Replace "john.doe" with the actual username of the AD User experiencing the issue.) 

When the command completes, send in the following files to Support for analysis: 
  • /var/centrify/tmp/cdcdebug.tar.gz 
  • /tmp/adquery.log 



Option 2:

If the debug steps are to be performed by an end-user and running Terminal commands is not preferred, the following steps can be used to get the button working again instead:
  1. Copy the attached cdcdebug and adinfo_extra.sh files to the Mac in the following location:
    • /usr/local/share/centrifydc/bin/
      • Note: There are two ways in which this can be done:
        1. First option is to copy the files manually to the destination Mac
          •  ​Once copied over, reset the permissions by running:
            • sudo chown root:wheel /usr/local/share/centrifydc/bin/adinfo_extra.sh
            • sudo chown root:wheel /usr/local/share/centrifydc/bin/cdcdebug
        2. Alternatively, the files could also be copied over using group policy:
          • Computer Configuration / Centrify Settings / Common UNIX Settings / "Copy files"
          • Copy the two files to the domain SYSVOL folder and add two new entries into the GP above:
            • Entry 1:
              • Filename: cdcdebug
              • Destination: /usr/local/share/centrifydc/bin/
              • Use destination file ownership and permissions
              • Copy as binary file: Enabled
            • Entry 2:
              • Filename: adinfo_extra.sh
              • Destination: /usr/local/share/centrifydc/bin/
              • Use destination file ownership and permissions
              • Copy as binary file: Enabled
          • Save the GPO and then go to the Mac and either wait for the next group policy refresh, or run the command to immediately retrieve the files:
            • adgpupdate
  2. Login as the affected AD user (if the issue is that the AD user cannot login, then login as Local Admin)
     
  3. Press the following buttons in order:
    • [ 0. Clear Debug Log Files ]
    • [ 1. Enable / Disable Debugger ] 
    • (The Debug Status will switch to: ON ) 
  4. Reproduce the problem on the Mac and let the debugger record the events. For example:
    • For login issues, try to login as the AD user.
    • For group policy issues, switch to the Group Policy tab on the Diagnostic Tool and press the [ GP Update ] button.
    • For any other issues, retrace the steps needed to make the problem appear and the debugger should be able to record what it can.
  5. Go back to the Diagnostic Tool and insert the name of the affected AD user in the username box on the left.
     
  6. Press the buttons in order:
    • [ 1. Enable / Disable Debugger ] 
    • [ 2. Save Debug Log files to Desktop ]
  7. Send the log file from the Desktop to Support for analysis.




Note:
  • The Diagnostic Tool will be fixed in a future release of the Centrify agent.
Attachments:

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