On Wed, Feb 20, 2019 at 12:48 PM Mo wrote:
>
> No luck, unfortunately. Could the problem be more to do with these lines?
>
> 2019/02/18 11:22:23 IPv6: :: on port 1515
> 2019/02/18 11:22:23 Request to allocate and bind sockets failed.
> 2019/02/18 11:22:23 ossec-authd: Unable to bind to port 1515
No luck, unfortunately. Could the problem be more to do with these lines?
2019/02/18 11:22:23 IPv6: :: on port 1515
2019/02/18 11:22:23 Request to allocate and bind sockets failed.
2019/02/18 11:22:23 ossec-authd: Unable to bind to port 1515
--
---
You received this message because you are
On Tue, Feb 19, 2019 at 6:21 PM Mo wrote:
>
> Thanks for the reply. No.. how would I go about doing that?
>
Add the password to `/var/ossec/etc/authd.pass` on the agent and
re-run agent-auth.
> On Monday, 18 February 2019, dan (ddp) wrote:
>>
>>
>>
>> On Mon, Feb 18, 2019 at 3:57 PM Mohammed A
Thanks for the reply. No.. how would I go about doing that?
On Monday, 18 February 2019, dan (ddp) wrote:
>
>
> On Mon, Feb 18, 2019 at 3:57 PM Mohammed A wrote:
>
>> My server's var/ossec/logs/ossec.log reports:
>>
>> 019/02/18 11:22:23 ossec-authd: INFO: Started (pid: 9154).
>> 2019/02/18
On Mon, Feb 18, 2019 at 3:57 PM Mohammed A wrote:
> My server's var/ossec/logs/ossec.log reports:
>
> 019/02/18 11:22:23 ossec-authd: INFO: Started (pid: 9154).
> 2019/02/18 11:22:23 Accepting connections. Random password chosen for
> agent authentication: 7c60a713f0d91d8193998ef01d85c92c
>