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-36111: DirectAudit Agent with two network interfaces

Auditing and Monitoring Service ,  

17 June,20 at 07:31 PM

Problem: On a Unix/Linux server with multiple network interfaces running the Centrify DirectAudit agent, the agent will not connect to a Collector. The output of the "dainfo -d" command will show messages like the following:

Current state: The agent is not connected to a Collector

But a more specific message in the output will show the following:

Audit store 'Audit-North' services 10.238.2.135
Audit store 'Audit-South' services 10.202.254.119
Audit stores 'Audit-North' and 'Audit-South' are misconfigured to both contain this computer



Cause: The issue here is due to the server having multiple network interfaces. Since the server will have multiple IPs and if the IPs belongs to different AuditStore scopes, this will cause confusion to the CentrifyDA agent running on the server and will therefore not connect to any Collector.


Solution: Starting with the 2017 release (CentrifyDA 5.4.0) the following parameter in the /etc/centrifyda/centrifyda.conf file has been added to specify which AuditStore will be preferred:

preferred.audit.store


For example:

preferred.audit.store: Audit-North


Then run the "dareload" command and the agent will now connect to the Collector serving the Audit-North AuditStore.
 

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