gt;
> On Thu, Feb 9, 2017 at 9:48 AM, Quintin Beukes > wrote:
> > Hi group,
> >
> > Server uname: Linux 2.6.32-642.13.1.el6.x86_64 #1 SMP Wed Jan 11
> 20:56:24
> > UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
> > Agent uname: Linux 2.6.32-642.13.1.el6.x86_64 #1
Hi group,
Server uname: Linux 2.6.32-642.13.1.el6.x86_64 #1 SMP Wed Jan 11 20:56:24
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Agent uname: Linux 2.6.32-642.13.1.el6.x86_64 #1 SMP Wed Jan 11 20:56:24
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
I am generating 5 log messages at 2 second intervals to tr
The ownership and permissions are the same as yours.
An unfortunate and rare event just occurred: all the agents are now showing
online. This happens occasionally and sticks for a few days.
I'll keep monitoring it and when the agents start giving problems again
I'll refer back to this message.
Hi group,
I'm trying to debug why my agent's are always showing disconnected. They
would work for a bit, and then randomly stop working. Some agents will
disconnect permanently, some intermittently switch between
connected/disconnected. Any advice on how to increase logging verbosity or
why my
Tue, Jul 19, 2016 at 10:19 AM, Quintin Beukes
> wrote:
> > The logs on the agent show this:
> > 2016/07/19 16:18:27 ossec-agentd(4101): WARN: Waiting for server reply
> (not
> > started). Tried: 'ossec.jeoffice/10.10.12.171'.
> > 2016/07/19 16:18:29
sec-agentd: INFO: Using IPv4 for: 10.10.12.171 .
2016/07/19 16:18:44 ossec-logcollector: WARN: Process locked. Waiting for
permission...
Quintin
On Tue, Jul 19, 2016 at 4:13 PM Quintin Beukes
wrote:
> Hi,
>
> A few days ago some of my OSSEC agents started going offline and stop
> send
Hi,
A few days ago some of my OSSEC agents started going offline and stop
sending alerts, and then a long while after come back online again like
nothing's wrong. Restarting the agents don't help fix the offline status.
This affects both agents running through a router/firewall to reach the
se
Hi,
A few days ago some of my OSSEC agents started going offline and stop
sending alerts, and then a long while after come back online again like
nothing's wrong. Restarting the agents don't help fix the offline status.
This affects both agents running through a router/firewall to reach the
se