This is the only thing in all of the agent's ossec.conf:
<ossec_config>
<client>
<server-ip>172.xx.x.xxx</server-ip>
</client>
</ossec_config>
And all of the agents have the current version of the agent.conf.
I have a cron job that runs (staggered times) every morning to restart
the agents, and then the server so I can make sure everything is
listening before the server pushes the config out.
Right now, it all seems to be functioning, except for a few agents
that go disconnected until I log in and restart ossec (even after the
cron job restarts them in the morning)...those are the only ones showing
the seg fault at restart, at this time.
~ Carrie
-----Original Message-----
From: [email protected] [mailto:[email protected]]
On Behalf Of dan (ddp)
Sent: Wednesday, December 19, 2012 9:25 AM
To: [email protected]
Subject: Re: [ossec-list] segmentation fault
On Tue, Dec 18, 2012 at 4:28 PM, Carrie Poole
<[email protected]> wrote:
> Ossec.conf:
>
This is the server's ossec.conf. I'm only interested in the ossec.conf
of a system with a segfaulting syscheckd.
With the agent.conf, which sections do the failing agents fall under?
Can you verify that they are picking up those configurations?
CONFIDENTIALITY NOTICE: This e-mail is confidential and intended
solely for the use of the individual or entity to which it is addressed. If
you are not the intended recipient, be advised that you have received
this email in error and that any use, dissemination, forwarding, printing
or copying of this e-mail is strictly prohibited. If you received this e-mail
in error, please delete it from your computer and contact the sender.
