Hi,
my problem is keys of agents, now are ok.
Thanks!!
Em sábado, 4 de março de 2017 18:33:43 UTC-3, dan (ddpbsd) escreveu:
>
> On Sat, Mar 4, 2017 at 2:36 PM, Eduardo Reichert Figueiredo
> wrote:
> > Hi All,
> > i killed de process and take command "ossec-control
On Sat, Mar 4, 2017 at 2:36 PM, Eduardo Reichert Figueiredo
wrote:
> Hi All,
> i killed de process and take command "ossec-control start" and the process
> of remoted stay up.
> But my agents "Windows" display "never connected" but the port 1514 stay up
> and with
Hi All,
i killed de process and take command "ossec-control start" and the process
of remoted stay up.
But my agents "Windows" display "never connected" but the port 1514 stay up
and with tcpdump i see my agents send logs to server.
strange...
Em quarta-feira, 1 de março de 2017 15:37:55
On Wed, Mar 1, 2017 at 6:59 AM, Eduardo Reichert Figueiredo
wrote:
> Port 1514 is already, i received UPD packets (validated with tcpdump), ossec
> is running (monitord, logcollector, syscheck, analysisd), only remoted not
> running, but remoted is displayed for port
Port 1514 is already, i received UPD packets (validated with tcpdump),
ossec is running (monitord, logcollector, syscheck, analysisd), only
remoted not running, but remoted is displayed for port 1514 (netstat
-vandup).
Em quarta-feira, 1 de março de 2017 08:53:21 UTC-3, Eero Volotinen
Is something runnin on port 1514 already? or ossec already running?
Eero
2017-03-01 13:50 GMT+02:00 Eduardo Reichert Figueiredo <
eduardo.reich...@hotmail.com>:
> Dear All,
> i doing installing ossec server in RHEL 6.8, but just ossec-remoted not
> running, i do troubleshooting with commands
Hi Dan - thanks for the reply.
Further research showed the /var/ossec/queue ownership as root:ossec.
I changed this to ossec:ossec. I left the permissions at 750.
Time to change my puppet scripts and rebake the image. It is a mystery how
it ever worked with settings like this
Again -
On Tue, Sep 22, 2015 at 4:56 AM, Matt Hickie wrote:
> Running into an issue with ossec-remoted not running. Setup had been
> working for over a couple of months and now the remoted process just seems
> to die. This is running on AWS linux
>
> Enabled debug with gdb.
>
>