Hi Alejandro,
The issue seems to be a counter problem since any other error would print
an additional error message.
Try to remove the file: "/var/ossec/queue/rids/" from the agent, for N
being the agent ID. For example:
rm /var/ossec/queue/rids/$(cut -d' ' -f1 /var/ossec/etc/client.keys)
/var/
These are the messages I'm getting from Ossec on the side of the agent:
2017/01/22 09:42:44 ossec-agentd: INFO: Trying to connect to server
(x.x.x.10:1514).
2017/01/22 09:42:44 ossec-agentd: INFO: Using IPv4 for: x.x.x.10 .
2017/01/22 09:42:45 ossec-agentd(1214): WARN: Problem receiving message
Hi Alejandro,
Let me help here. I don't think your error is related with compatibility
issues, and it is not true that the agent included on Wazuh is older than
an OSSEC agent 2.8.3, in fact, is newer (based on OSSEC 2.9+).
OSSEC Agents are totally compatible with Wazuh fork, meaning that you wil
On Jan 22, 2017 4:16 PM, "Kat" wrote:
The Wazuh fork is actually newer, but regardless there should never be a
conflict from 2.x to 2.x with agent and server. When
*With the caveat that this isn't explicitly tested.
you say "conflict" - can you be more specific on the error you are seeing?
K
The Wazuh fork is actually newer, but regardless there should never be a
conflict from 2.x to 2.x with agent and server. When you say "conflict" -
can you be more specific on the error you are seeing?
Kat
On Friday, January 20, 2017 at 5:14:09 PM UTC-6, Alejandro M wrote:
>
> Hello all. I just
