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-8906: DirectAudit Advanced Monitoring does not consistently start after a reboot

Auditing and Monitoring Service ,  

1 July,17 at 06:57 AM

Applies to:
All version of DirectAudit installed on Red Hat and CentOS operating systems.

Problem:
After rebooting systems with DirectAudit installed, Advanced Monitoring status does not consistently start.

Cause:
An unexpected error occurs upon reboot causing Advanced Monitoring not to start upon system reboot.

Resolution:
This issue is fixed in Centrify Server Suite 2017.1 but can be worked around with the following procedure:
run service auditd restart and then run dacontrol -m

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

Related Articles

 articleKB-9441: Default audit rules in CentOS 7.3 conflicts with Advanced monitoring articleKB-7555: Unable to login as root after upgrade to Centrify Suite 2016 (CDC 5.3.0) articleCentrify Advanced Monitoring enables SIEM tools to alert on the creation of SSH keys articleCentrify's Privileged Identity Management Solution for Big Data articleKB-2109: Are there any sizing guides to help plan for scalability and storage requirements for DirectAudit? articleKB-10409 How to suppress <no_login_user> from DirectAudit anaylze Report and Powershell ? articleCheat Sheet - DirectAudit Commands on Unix & Linux Systems articleKB-4602: Pre-requisite SQL server and database permissions for users articleUnderstanding DAINFO Output