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-2967: Unable to see any audited sessions

Auditing and Monitoring Service ,  

12 April,16 at 11:09 AM

Applies to: All versions of Centrify DirectAudit
 
Question:
 
Auditing is enabled and there are no issues with dainfo --diag output, however no audited sessions are seen with Audit Analyzer even after waiting for several hours.
 
Is there any reason for this?

 
Answer:

Audited sessions may not make it to the Audit Analyzer if the SQL Express Database becomes full.
 
The only way to resolve this is:
 
a) Create a new SQL database and detach the old Database using DirectAudit Administrator Console. The Collector needs to be stopped momentarily. (Recommended method)
 
b) Using SQL Management studio, go to Centrify's Audit database and clear these entries.The caveat here is the audited data is completely gone and irrecoverable.
 
- Drill down to Centrify's audited DB table and run the queries:
 
  DELETE FROM session WHERE state=3
 
  DBCC SHRINKDATABASE(0)  
 
(The number 3 in the first command means “Completed Sessions”) 
 

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

Related Articles

 articleKB-19499: Terminal Sessions May Hang if dzdo is Audited and Has Output Piped Under /bin/sh articleKB-4436: How to run a query that can run against the active Audit Store database to find all sessions created by the scp/rsync/sftp traffic and how to delete the sessions? articleKB-4018: DirectAudit Session logging (scp file stream content) can cause excessive DB usage articleKB-4105: Questions on Centrify DirectAudit system audited data cache when the collector is not available. articleKB-7555: Unable to login as root after upgrade to Centrify Suite 2016 (CDC 5.3.0) articleKB-6041: How to show current license type in use by adclient articleKB-20210: Common Questions Regarding Centrify DirectControl and CoreOS 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?