On Tue, Feb 19, 2019 at 6:21 PM Mo <mo7...@gmail.com> 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) <ddp...@gmail.com> wrote:
>>
>>
>>
>> On Mon, Feb 18, 2019 at 3:57 PM Mohammed A <mo7...@gmail.com> 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
>>
>>
>> Have you tried including this password in the agent request?
>>
>>>
>>> 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
>>> 2019/02/18 11:22:30 ossec-authd: INFO: New connection from 172.16.215.130
>>> 2019/02/18 11:22:30 ossec-authd: ERROR: Invalid password provided by 
>>> 172.16.215.130. Closing connection.
>>>
>>> While my agent's terminal output is:
>>>
>>> 2019/02/18 09:57:41 ossec-authd: INFO: Started (pid: 24182).
>>> INFO: Connected to 172.16.215.129:1515
>>> INFO: Using agent name as: secondary.example.com
>>> INFO: Send request to manager. Waiting for reply.
>>> INFO: Connection closed.
>>>
>>> How can I remedy this? It's racking my brain. Here's what I'm typing:
>>> On server: # /var/ossec/bin/ossec-authd -p 1515 >/dev/null 2>&1 &
>>> On agent: # /var/ossec/bin/agent-auth -m 172.16.215.129 -p 1515
>>>
>>> Tail of my ossec.log on agent:
>>> 2019/02/18 09:56:39 ossec-agentd: INFO: Using IPv4 for: 172.16.215.129 .
>>> 2019/02/18 09:56:49 ossec-agentd(1218): ERROR: Unable to send message to 
>>> server.
>>> 2019/02/18 09:57:01 ossec-agentd(1218): ERROR: Unable to send message to 
>>> server.
>>> 2019/02/18 09:57:02 ossec-agentd(4101): WARN: Waiting for server reply (not 
>>> started). Tried: '172.16.215.129'.
>>> 2019/02/18 09:57:41 ossec-authd: INFO: Started (pid: 24182).
>>> 2019/02/18 09:58:52 ossec-agentd: INFO: Trying to connect to server 
>>> (172.16.215.129:1514).
>>> 2019/02/18 09:58:52 ossec-agentd: INFO: Using IPv4 for: 172.16.215.129 .
>>> 2019/02/18 09:59:02 ossec-agentd(1218): ERROR: Unable to send message to 
>>> server
>>>
>>> Many thanks to any who can help. I'm running into brickwalls on a Google 
>>> search.
>>>
>>> --
>>>
>>> ---
>>> You received this message because you are subscribed to the Google Groups 
>>> "ossec-list" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>> email to ossec-list+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>
>> --
>>
>> ---
>> You received this message because you are subscribed to the Google Groups 
>> "ossec-list" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to ossec-list+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups 
> "ossec-list" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ossec-list+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"ossec-list" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ossec-list+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to