Error: 3013

[Sainz]

Good Morning

Could you help me with this problem?
I'm not sure I understand

Thanks

Error

Error: 3013 - Error connecting with socket: Socket 'auth' cannot receive connections

Error: Error: 3013 - Error connecting with socket: Socket 'auth' cannot receive connections at RegisterAgent._callee3$ (https://******/45103/bundles/plugin/wazuh/wazuh.chunk.10.js:5:5120589) at tryCatch (https://*********/45103/bundles/plugin/customImportMapDashboards/customImportMapDashboards.plugin.js:13:760622) at Generator.invoke [as _invoke] (https://*****/45103/bundles/plugin/customImportMapDashboards/customImportMapDashboards.plugin.js:13:764638) at Generator.throw (https://******/45103/bundles/plugin/customImportMapDashboards/customImportMapDashboards.plugin.js:13:761817) at register_agent_asyncGeneratorStep (https://*****/45103/bundles/plugin/wazuh/wazuh.chunk.10.js:5:5111638) at _throw (https://****/45103/bundles/plugin/wazuh/wazuh.chunk.10.js:5:5112064)

[Norberto Cesar Vicchi]

Hello Sainz!

Based on the error message, it seems that there is an issue with the socket connection in the Wazuh agent. The error 'Error: 3013 - Error connecting with socket: Socket 'auth' cannot receive connections' indicates that the agent is unable to establish a connection with the authentication socket. This could be due to a misconfiguration or a network issue.

To troubleshoot this problem, you can try the following steps:
.:

• Verify that the Wazuh manager is running: /var/ossec/bin/wazuh-control status
• Verify that the Wazuh manager is reachable: if there is  a firewall installed, try disabling it, and try from another computer in the same subnet a command like telnet manager_ip 1514
• Verify, if the Wazuh manager is behind a router, that all required ports are correctly forwarded.
• Check the agent configuration file (usually located at '/var/ossec/etc/ossec.conf') and ensure that the 'auth' socket is correctly configured, and that the manager IP its correct.
• Restart the Wazuh agent and monitor the logs for any additional error messages.

If the issue persists, please provide more details about your environment and any relevant log files for further assistance.

Regards!

[Sainz]

Wazuh-control status:

wazuh-clusterd not running...
wazuh-modulesd is running...
wazuh-monitord is running...
wazuh-logcollector is running...
wazuh-remoted is running...
wazuh-syscheckd is running...
wazuh-analysisd is running...
wazuh-maild not running...
wazuh-execd is running...
wazuh-db is running...
wazuh-authd: Process 1840 not used by Wazuh, removing...
wazuh-authd not running...
wazuh-agentlessd not running...
wazuh-integratord not running...
wazuh-dbd not running...
wazuh-csyslogd not running...
wazuh-apid is running...Abet

Firewall: Disable

I looked in the Ossec.conf file, it's a Windows file ( open with blocnote) , and I didn't find "Socket".
The IP is correct.
However this problem occurred after a few days, before everything was working.

[Norberto Cesar Vicchi]

Please execute:

wazuh-authd is not running, that's why it cannot connect. Please execute:
/var/ossec/bin/wazuh-control stop

/var/ossec/bin/wazuh-control start

On another terminal, execute before:

tail -f /var/ossec/logs/ossec.log

so we can see what's going on when it starts

Regards!

[Sainz]

Hi!

The problem was solved with Stop\Start!

Thanks!