Livestatus issue with Docker installation

Troubleshooting
, ,
1

CMK version: 2.2.0p22
OS version: docker

Error message:[Errno 104] Connection reset by peer

**Hello, i newly created new docker installation of CheckMK raw. On my primary site I added this new site (connection) into Distributed monitoring, but Livestatus end with “[Errno 104] Connection reset by peer”. Login was successfull, I see the status Online.

I am really confused, becaused I use the same configuration as in my another Docker remote site installation without any problem. All installations have the same version.

I also check Firewall and there is visible communication between primary site and remote site.

Thank you**

2

Hi Michal,

you need to set an environment variable CMK_LIVESTATUS_TCP=on and also expose 6557/tcp.

3

This is the funny fact. CMK_LIVESTATUS_TCP is already set to “on”. Port 6557/tcp exposed and verified on Firewall that primary site is successfully communicating with the site. Configuration connection on port 5010/tcp is working properly. Only the 6557/tcp is not working properly.

So I tried to change the port 6557/tcp to 5009/tcp and it ends with the same error.

Do you have other ideas?

Thank you so much, Michal

4

Are you connecting via IPv6 or IPv4? If v6, then you need to add IPv6 as a flag in your ~/etc/mk-livestatus/xinetd.conf.

5

It is IPv4 connection

6

Can you show us the output of: docker exec <name of your container> omd status?

Also: docker logs <name of your container> (maybe strip the sensitive data, if CMK_PASSWORD is what you will use productively later)

7

Simon, thank you so much for your time and effort. I figured out.

The problem was that I put CMK_LIVESTATUS_TCP as Docker variable, but I had to go into Docker container terminal and set proper values also in omd config.

Have a perfect day, Michal

8

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.