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-0564: How to Collect Debug Logs from a DirectAudit Agent

Auditing and Monitoring Service ,  

17 September,16 at 12:44 AM

Question:

What are the steps to enable debug logging for the DirectAudit agent for UNIX/Linux to send to Centrify Support?

Answer:

Use either section A) or B) depending on the version of the agent you are running (run dainfo -v to verify)

A) Turning on debug logging for the DirectAudit agent versions 3.1.1 and higher (dad process) running on Unix/Linux machines: 

Login as root or execute with privileged the following:

  1. Turn on Centrify debug: 

# /usr/share/centrifydc/bin/addebug clear
# /usr/share/centrifydc/bin/addebug on
# /usr/sbin/dadebug clear 
# /usr/sbin/dadebug on
(If TRACE log is required, please run /usr/sbin/dadebug set TRACE)
Now dad agent will write debug information into a file "centrifydc.log" found under system's syslog directory.

  1. Reproduce issue by restarting DirectAudit service:

# /etc/init.d/centrifyda restart

  1. Collect adinfo and wait for it to complete:

# adinfo -t

  1. Turn off debug:

# /usr/sbin/dadebug off
# /usr/share/centrifydc/bin/addebug off

  1. Send to support the files:

a) /var/centrify/tmp/adinfo_support.tgz 
b) /var/centrifyda/tmp/support.tar.gz

  1. If support is requesting a debug log for the DirectAudit Collector as well please follow the steps in:

KB-5727: How to enable debug logging for the DirectAudit Collector
 

B) Turning on debug logging for the DirectAudit agent versions 2.x-3.1.0 (dad process) running on Unix/Linux machines: 

  1. Turn on Centrify debug:

# /usr/share/centrifydc/bin/addebug clear
# /usr/share/centrifydc/bin/addebug on
# /usr/sbin/dadebug clear 
# /usr/sbin/dadebug on
(If TRACE log is required, please run /usr/sbin/dadebug set TRACE)
Now dad agent will write debug information into a file "centrifydc.log" found under system's syslog directory.

  1. Reproduce issue by restarting DirectAudit service:

# /etc/init.d/centrifyda restart

  1. Collect information and wait for it to complete:

# adinfo -t
# dainfo --diag > /tmp/dainfo.txt
# ls –al /bin/ > /tmp/ls.out

  1. Turn off debug:

# /usr/sbin/dadebug off
# /usr/share/centrifydc/bin/addebug off

  1. Send to support the files:

a) /tmp/adinfo_support.tar.gz or /var/tmp/centrify/adinfo_support.tgz
b) /tmp/dainfo.txt
c) /var/log/centrifydc.log
d) /etc/centrifyda/centrifyda.conf
e) /tmp/ls.out

  1. If support is requesting a debug log for the DirectAudit Collector as well please follow the steps in:

KB-5727: How to enable debug logging for the DirectAudit Collector



 

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

Related Articles

 articleKB-5727: How to Collect Debug Logs from a DirectAudit Collector articleKB-0062: How to Collect Debug Logs from a DirectControl Agent articleKB-0446: How to Collect Debug Logs from a Samba Server articleKB-0547: How to Collect Debug Logs from a DB2 server with the Centrify App Server Plug-in articleKB-2137: How to Collect Debug Logs from a Centrify NIS Server (adnisd) articleKB-10599: How to Collect Debug Logs from a Centrify Access Manager Console articleKB-3285: How to Collect Debug Logs from an OpenSSH Server articleKB-8262: How to Collect Debug Logs from Centrify Agent for Windows articleKB-10531: How to Collect Debug Logs from the Agent for Linux cclient