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-3021: How to record and capture issues using the Mac Diagnostic Tool.

Centrify Identity Service, Mac Edition ,  

25 July,16 at 07:00 PM

Applies to: Centrify Identity Service, Mac Edition



Question:

How can the Mac Diagnostic Tool be used to capture debug logs for recording issues (such as login problems)?


Answer:

Note:
To capture debug logs:
  1. Login as the affected AD user (if the issue is that the AD user cannot login, then login as Local Admin)
  2. Download and open the Diagnostic Tool and switch to the Debug / Logs tab.
  3. Press the following buttons in order:
    • [ 0. Clear Debug Log Files ]
    • [ 1. Enable / Disable Debugger ]
       
    • (The Debug Status will switch to: ON )
       
    • If the problem to be recorded is a login issue, and the Mac is Connected to the domain, press [ Flush AD Cache ] and logout of the Local Admin account (the Debug Status will remain 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 ]
       
    • (The Debug Status will switch to: OFF )
  7. Send the generated log file pack from the Desktop to Centrify Support.
 
User-added image






Note:

To perform the same debug capture sequence using the Terminal command line:
  1. Login to the system as Local Admin and open a Terminal session (alternatively, login via SSH). 
     
  2. Enter the following commands:
    • sudo /usr/local/share/centrifydc/bin/addebug clear
    • sudo /usr/local/share/centrifydc/bin/cdcdebug on
    • sudo adflush
  3. Logout of the Local Admin account and (try to) login as the AD user. 
     
  4. Reproduce the problem and let the debugger record the sequence of events.
     
  5. Log back in as Local Admin and open the Terminal again.
     
  6. Enter the following commands: 
    • sudo /usr/local/share/centrifydc/bin/cdcdebug off 
    • sudo /usr/local/share/centrifydc/bin/cdcdebug -f pack AD_Username
    • adquery user -A AD_Username > /tmp/adquery.log
       
    • (Where AD_Username is the username of the AD User that was logged in.) 
  7. Send the following files to Support: 
    • /var/centrify/tmp/cdcdebug.tar.gz  (or /tmp/cdcdebug.tar.gz )
    • /tmp/adquery.log 

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