mentation.
>
> Regards.
>
> On Monday, May 22, 2017 at 6:56:10 PM UTC+2, Topper Bowers wrote:
>>
>> I deleted some of the lines starting with bang (!) but that didn't clear
>> up the problem. My client.keys is now smaller than 2048, but I still can't
>> add age
;"^\d+\s*\!" | wc -l
>
> The solution could be clean the client.keys (lines with "!") after
> removing the agent.
>
> Regards.
>
>
> On Monday, May 22, 2017 at 11:05:38 AM UTC+2, Topper Bowers wrote:
>>
>> Hi,
>>
>> My cli
Hi,
My client has a highly dynamic environment and we're using OSSEC (wazuh
1.1.1 release, OSSEC v2.8). When a server spins up, it registers itself as
an agent to the servers authd and everything was going ok. However, my
client.keys file is now 2048 lines long and no new agents can register.
Old thread. Did it end up working out? We're having trouble with the
sockets being on NFS even just restarting ossec on the same host (let alone
on 5).
On Tuesday, June 24, 2014 at 6:17:52 PM UTC+2, Roy Feintuch wrote:
>
> Just saw this thread and wish to add my 2 cents:
> - Syscheck: there is
Hello!
I'm trying to institute some automatic failover for OSSEC and we're using
amazon's elastic files share as the persistence layer for ossec. Right now
we have the whole /var/ossec directory symlinked to a directory that exists
on the NFS mount.
When we restart the ossec service on the
ening, it will be something like:
>
> $ strace -ff -o log -s 2 -p
>> where is the pid from ossec-agentd
>> and then
>> $ tail -f log. | grep IP_MANAGER
>
>
>
> Regards,
>
> Pedro S.
>
> On Wed, Oct 26, 2016 at 1:45 PM, Topper Bower
ger is listening to that port and agent is sending to that port.
> - Verify/add/generate a new key for the Agent.
>
>
> Regards,
>
> snaow.
>
> On Wed, Oct 26, 2016 at 11:59 AM, Topper Bowers <topping...@vitals.com
> > wrote:
>
>> Hello all,
>>
>>
:59 AM, Topper Bowers
> <topping...@vitals.com > wrote:
> > Hello all,
> >
> > I'm using ossec 2.8.3 from wazzuh and I can't seem to get the agents to
> talk
> > to the host. It is exactly as described here:
> > https://botbot.me/freenode/ossec/201
Hello all,
I'm using ossec 2.8.3 from wazzuh and I can't seem to get the agents to
talk to the host. It is exactly as described
here: https://botbot.me/freenode/ossec/2016-07-21/?msg=70001778=1.
I've also put both the agent and the master into debug mode. I've also run
tcpdump on both the
