11 April,19 at 11:50 AM
root@engcen6 centrifyagent]# dainfo
Pinging adclient: adclient is available
Daemon status: Online --> If status says online means the daemon is up and communicating to DirectAudit collectors
Current installation: 'DirectAudit' (configured via Group Policy) --> This is the DirectAudit instance the server is using. If you are using Centrify GPO to control this it will state it
Current collector: MEMBER.james.vms:5063:HOST/MEMBER.james.vms@JAMES.VMS --> This is the collector the host is currently using. If blank it isn’t talking to a collector.
Session offline store size: 1.22 MB --> This is the space of the offline cache
Despool rate: 14.79 KB/second
Audit trail offline store size: 0.00 Bytes
Getting offline database information:
Size on disk: 4.87 MB --> This is how much cache is on the server locally
Database filesystem use: 1.81 GB used, 7.98 GB total, 6.17 GB free --> How much file system information
DirectAudit NSS module: Active --> Let’s you know if NSS module is active or not
DirectAudit advanced monitoring: Enabled --> If advanced monitoring is enabled or not
DirectAudit advanced monitoring status: running --> If advanced monitoring is running or not
User (root) audited status: Yes --> Current user that ran the dainfo command is getting audited
DirectAudit is not configured for per command auditing. --> By default it will audit all commands that have the role enabled to audit if we setup only to audit dzdo commands then this will state different
For Centrify DirectAudit the main fields will be Daemon status, Current installation, and Current collector
Daemon status = Online --> Good
Daemon status = Offline --> Direct Audit not working
Current installation = CentrifyDirectAuditInstallation --> Good
Current installation = not configured --> Direct audit hasn’t been configured or is having a problem
Current collector = collectorserverFQDN --> Direct audit agent is talking to a collector
Current collector = N/A --> DirectAudit agent isn’t talking to a collector.