[ossec-list] Re: ERROR: Unable to Bind port '1514'

Hi Carlos, i have been fighting with the same issue, and i finally got it. In this article: https://github.com/ossec/ossec-hids/issues/1061 I configured support to IPV6 configuring the /etc/sysctl.conf net.ipv6.conf.all.disable_ipv6 = 0 net.ipv6.conf.default.disable_ipv6 = 0 After run sysctl

Re: [ossec-list] Re: ERROR: Unable to Bind port '1514'

Hello dan, I killed the instance but anything happend, i had that start the process manualy because de services get down. =S Regards... El viernes, 25 de agosto de 2017, 11:01:25 (UTC-5), dan (ddpbsd) escribió: > > > > On Aug 25, 2017 11:32 AM, "Carlos Islas" > wrote:

[ossec-list] Re: ERROR: Unable to Bind port '1514'

I have seen this happen on FreeBSD systems using OSSEC 2.8.3. The issue is usually an inability to write the ar socket, but the error message in the logs/ossec.log file can be any number of things. It is caused by a permission issue with the sockets used for the queues, and shows up in both

Re: [ossec-list] Re: ERROR: Unable to Bind port '1514'

On Aug 25, 2017 11:32 AM, "Carlos Islas" wrote: Hi dan, Sorry, im newbie in that kind of commands. How can i kill the instance? I usually use `pkill ossec-remoted` You can also use `ps` to get the pid (or look for the pid in /var/ossec somewhere) and kill it that

[ossec-list] Re: ERROR: Unable to Bind port '1514'

Hi dan, Sorry, im newbie in that kind of commands. How can i kill the instance? Regards... El jueves, 24 de agosto de 2017, 16:19:57 (UTC-5), Carlos Islas escribió: > > Hello, > > I am having this issue when i execute the command ./ossec-remoted > > ossec.log: > > 2017/08/24 16:16:22