On Wed, Oct 8, 2014 at 2:25 PM, Abhi <[email protected]> wrote: > Hi, > > We are using automated scripts through Chef to instal OSSEC and use > ossec-authd to control key exchange. After a recent install, the Agent is > sending the alerts correctly, but OSSEC(ossec_agent_control) still reports > that the agent has "Never Connected". I have verified that it's same > reporting host in both type of alerts. > > This agent was not added manually.. It was connected using agent-auth. > > I verified using ./agent-control and there too, agent is listed as "Never > Connected". Is there a way to find out what is causing this mismatch. We > rely on messages from ossec_agent_control for creating Splunk dashboards, > giving health and current status for agents. >
Make sure there aren't any errors in the ossec.log on the agent or manager. Check /var/ossec/queue/agent-info. There should be a file there for this agent. You could either try deleting it and restarting the agent's OSSEC processes or maybe checking its permissions. > Thanks, > > Abhijit > > > -- > > --- > You received this message because you are subscribed to the Google Groups > "ossec-list" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- --- You received this message because you are subscribed to the Google Groups "ossec-list" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
