On Mar 16, 2018 6:48 AM, "Igor" <6513...@gmail.com> wrote:
so how can i resolv this error?
ossec-logcollector(1202): ERROR: Configuration error at
'/var/ossec/etc/shared/agent.conf'. Exiting.
Check the ossec.log for more information.
четверг, 15 марта 2018 г., 0:16:19 UTC+3 пользователь dan
so how can i resolv this error?
ossec-logcollector(1202): ERROR: Configuration error at
'/var/ossec/etc/shared/agent.conf'. Exiting.
четверг, 15 марта 2018 г., 0:16:19 UTC+3 пользователь dan (ddpbsd) написал:
>
> On Wed, Mar 14, 2018 at 6:28 AM, Igor <651...@gmail.com >
> wrote:
> >
> >> You e
On Wed, Mar 14, 2018 at 6:28 AM, Igor <6513...@gmail.com> wrote:
>
>> You edit the file on the server. That file then gets pushed to the client.
>>
> i have edit this file on a server, but file on client from
> /var/ossec/etc/shared/agent.conf on client side
>
The server should be pushing this fil
> You edit the file on the server. That file then gets pushed to the client.
>
> i have edit this file on a server, but file on client from
/var/ossec/etc/shared/agent.conf on client side
--
---
You received this message because you are subscribed to the Google Groups
"ossec-list" group.
To
On Mar 13, 2018 12:23 PM, "Igor" <6513...@gmail.com> wrote:
вторник, 13 марта 2018 г., 18:08:44 UTC+3 пользователь dan (ddpbsd) написал:
> On Tue, Mar 13, 2018 at 9:33 AM, Igor <651...@gmail.com> wrote:
> >
> >
> > вторник, 13 марта 2018 г., 16:20:58 UTC+3 пользователь Igor написал:
> >>
> >>
>
вторник, 13 марта 2018 г., 18:08:44 UTC+3 пользователь dan (ddpbsd) написал:
>
> On Tue, Mar 13, 2018 at 9:33 AM, Igor <651...@gmail.com >
> wrote:
> >
> >
> > вторник, 13 марта 2018 г., 16:20:58 UTC+3 пользователь Igor написал:
> >>
> >>
> >>>
> >>> If you have commands in your agent.con
On Tue, Mar 13, 2018 at 9:33 AM, Igor <6513...@gmail.com> wrote:
>
>
> вторник, 13 марта 2018 г., 16:20:58 UTC+3 пользователь Igor написал:
>>
>>
>>>
>>> If you have commands in your agent.conf, you need to set
>>> "logcollector.remote_commands" to "1" in internal_options.conf.
>>>
>>> https://osse
вторник, 13 марта 2018 г., 16:20:58 UTC+3 пользователь Igor написал:
>
>
>
>> If you have commands in your agent.conf, you need to set
>> "logcollector.remote_commands" to "1" in internal_options.conf.
>>
>> https://ossec.github.io/docs/syntax/head_internal_options.analysisd.html?highlight=remo
>
> If you have commands in your agent.conf, you need to set
> "logcollector.remote_commands" to "1" in internal_options.conf.
>
> https://ossec.github.io/docs/syntax/head_internal_options.analysisd.html?highlight=remote%20command#intopt-logcollector.remote_commands=0
>
>
> now i have logcol
On Tue, Mar 13, 2018 at 4:40 AM, Igor <6513...@gmail.com> wrote:
> I have edit /var/ossec/etc/ossec.conf on a client
>
>
>
>
>
> my_ip
>
>
>
> and get this error
>
> Started ossec-agentd...
> 2018/03/13 11:33:40 ossec-logcollector: Remote commands are not accepted
> from the manager. I
I have edit /var/ossec/etc/ossec.conf on a client
my_ip
and get this error
Started ossec-agentd...
2018/03/13 11:33:40 ossec-logcollector: Remote commands are not accepted
from the manager. Ignoring it on the agent.conf
2018/03/13 11:33:40 ossec-logcollector(1202): ERROR: Configur
Hello Igor!
I also installed OSSEC 2.9.3 by rpm packages on centos7, same as you (as
described here:
https://ossec.github.io/docs/manual/installation/installation-package.html#rpm-installation
).
I had the same problem, and it's caused because /etc/ and /bin/ appears on
the check list on both
12 matches
Mail list logo
