Piggyback service discovery

**CMK version: Checkmk Raw Edition 2.3.0p14 **
**OS version: Ubuntu 22.04 and 24.04 **

Hello everyone, Im asking once again for help due to problems with the piggyback mechanism.

My piggyback servers are recognized as such and also receive data, but only 3 services are displayed in the service discovery. I miss the other services which are also displayed on my other hosts:


(Unfortunately, as a new user, I can only upload one picture, which is why I had to cut the two together. I hope Im not breaking any rules and if I am, I apologize for the inconvenience.)

When I run the agent on the parent server, I believe that all the required information is read out in the output. But I don’t know where the error is, do I have to configure the service discovery further?

I think its due to a problem understanding my side of the configuration or something like that. If you need further configuration settings from me, I will be happy to provide them.

My first guess would be that you don’t have an agent installed or no matching agent plugin rule on the piggyback hosts but on your other example Host.

Maybe Im missing a bit of context to my setup:
I have two hosts, where host A has two IP addresses, one public and one private. Host B only has a private one and is therefore only accessible to the outside world via NAT, which is why I would like to use the piggyback mechanism for it. The agent is installed on both hosts, host A also receives all services automatically in the discovery. To get the data from host B to host A, I have written a small bash script, which is located in the check_mk plugins folder, with the following content:

#!/bin/bash
echo “<<<<Host-B>>>>”
ssh Host-B -T '/usr/bin/check_mk_agent'
echo “<<<<>>>>”

If I run the script manually, I get the data from host B on the terminal of host A. If I run the agent manually via “check_mk_agent” on the terminal, the data from host B is also included in the output as an attachment to the data from host A.

It works now, I have reconfigured the whole setup. Unfortunately I cant say what the problem was.

1 Like