Well, I did what you did in the Dockerfile for OSSEC: Defined a dummy local
agent. Ok for now, I'll watch
for https://github.com/ossec/ossec-hids/pull/662.
--
---
You received this message because you are subscribed to the Google Groups
"ossec-list" group.
To unsubscribe from this group and
Note that there is a pull request to fix this on GitHub. The initial
attempt didn't work but the latest should.
https://github.com/ossec/ossec-hids/pull/662
On Saturday, 20 February 2016 01:58:12 UTC, Santiago Bassett wrote:
>
> no, you need to restart the manager, after the first agent is
no, you need to restart the manager, after the first agent is added. Once
that is done then you don't need to restart it anymore. You can actually
insert a dummy agent, if you really need to have remoted running since the
very beginning.
best
On Fri, Feb 19, 2016 at 5:16 PM, Barry Kaplan
Old post, sorry. I'm not sure I understand what to do in this case. Will
remoted start again if an agent is registered some time after the server
starts and remoted decides to shut down?
--
---
You received this message because you are subscribed to the Google Groups
"ossec-list" group.
To
that even when the keys file
is empty.
Just a thought.
Best wishes…
Colin
From: ossec-list@googlegroups.com [mailto:ossec-list@googlegroups.com] On
Behalf Of Joel Parker
Sent: 25 November 2014 00:52
To: ossec-list@googlegroups.com
Subject: [ossec-list] remoted not starting
I have an ansible-ized
On Mon, Nov 24, 2014 at 7:52 PM, Joel Parker rootri...@gmail.com wrote:
I have an ansible-ized install of ossec as a server, using the art rpm's to
install (ossec-hids and ossec-hids-server). I have it working as expected on
a server in our office, however when I run the same setup on a server
On Tuesday, November 25, 2014 6:14:48 AM UTC-8, dan (ddpbsd) wrote:
On Mon, Nov 24, 2014 at 7:52 PM, Joel Parker root...@gmail.com
javascript: wrote:
(gdb) set follow-fork-mode child
(gdb) run -df
set follow-fork-mode child
or
run -df
hmm??
ossec.conf (I've tried every
On Tue, Nov 25, 2014 at 1:18 PM, Joel Parker rootri...@gmail.com wrote:
On Tuesday, November 25, 2014 6:14:48 AM UTC-8, dan (ddpbsd) wrote:
On Mon, Nov 24, 2014 at 7:52 PM, Joel Parker root...@gmail.com wrote:
(gdb) set follow-fork-mode child
(gdb) run -df
set follow-fork-mode child
or
*To:* ossec...@googlegroups.com javascript:
*Subject:* [ossec-list] remoted not starting
I have an ansible-ized install of ossec as a server, using the art rpm's
to install (ossec-hids and ossec-hids-server). I have it working as
expected on a server in our office, however when I run
I have an ansible-ized install of ossec as a server, using the art rpm's to
install (ossec-hids and ossec-hids-server). I have it working as expected
on a server in our office, however when I run the same setup on a server in
our remote data center I am unable to get remoted to stay running.
10 matches
Mail list logo
