Check_MK [Errno 104] Connection reset by peer

CMK version: 2.0
OS version: Centos 7

Error message: Agent Communication failed: [Errno 104] Connection reset by peer

Hi,

I have a situation with a host, for some reason i lost the connectivity with the agent in this host, the error is:

But i already restart the xinetd (this is a Linux host) on the host, and nothing is blocking the port 6556, also when i do a telnet directly on the cmk server to the host port 6556 I received the information of the agent.

Does anyone know what is happened here ?

Thanks

You can do on the command line a “cmk -D hostname” to check if only the normal agent is configured as connection method.

Hi, this is the information that i can see on that part:

Agent mode: Normal Checkmk agent, or special agent if configured
Type of agent:
TCP: 192.x.x.x:6556
Process piggyback data from /omd/sites/sitename/tmp/check_mk/piggyback/ servername

Hi @andreas-doehler

This is the information that i can see on that part:

Is there a configuration needed ?

I’m seeing the same error message trying to reach the agent on a fedora 36 machine. @Gustavo – did you ever get things working?

The configuration of @Gustavo looked fine. If you get a connection reset by peer it looks more like a problem on the client side.

How would you suggest debugging the client side? I don’t see a --debug or --verbose flag on the systemd start script for the cmk-agent-ctl-daemon.service

Reset connection are not so easy to debug. I’m not the specialist for such things :wink:

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed. Contact an admin if you think this should be re-opened.