Usually there are warning or error messages in ossec.log file (check those
both in the agent and manager).
On Mon, Jan 4, 2016 at 11:06 AM, Cal wrote:
> Found a solution, thinking it might be a key issue. On one server, I had
> to chmod the keys file, which allowed
Found a solution, thinking it might be a key issue. On one server, I had to
chmod the keys file, which allowed the agent to connect. I tried re-adding
the existing key to the other agents and configuring the permissions
without anything working. Finally, I re-issued the keys for the disconnect
Also, from agent:
# netstat -panu | grep 1520
udp0 0 AGENT_IP:43737 SERVER_IP:1520 ESTABLISHED
30669/ossec-agentd
On Monday, January 4, 2016 at 12:25:02 PM UTC-5, Cal wrote:
>
> I have about 20 OSSEC agents connected to my OSSEC server without issue.
> There are