Error message:
[agent] Success, [special_proxmox_ve] Success, [piggyback] Missing data
Output of “cmk --debug -vvn hostname”: (If it is a problem with checks or plugins)
…
No piggyback files for ‘fqdn of server’. Skip processing.
No piggyback files for ‘ip of server’. Skip processing.
…
[agent] Success, [special_proxmox_ve] Success, [piggyback] Missing data(!), execution time 7.4 sec | execution_time=7.420 user_time=0.170 system_time=0.000 children_user_time=2.550 children_system_time=0.120 cmk_time_agent=3.910 cmk_time_ds=0.670
…
I have piggyback data coming in for my running vm’s just fine but I’m still getting a warning for the pve host check_mk service. I see the above lines in the output and wonder if it’s because it’s looking for data for the FQDN and the ip which there aren’t any hosts or vm’s in the PVE inventory that match them. The host is just the hostname in the inventory but I use FQDN in checkmk to match the valid certificate.
Normally you have no piggyback data on an Proxmox host object if it is queried directly with the special agent.
In my systems only the Proxmox hosts that are member of the cluster and not directly queried with the special agent have piggyback data from the queried Proxmox server.
This can also be a problem as your names from the Proxmox don’t need to be FQDN.
You can use the “piggyback hostname translation” rule to add the domain suffix to the shortname of your Proxmox hosts.
The host has the checkmk agent installed and I definitely have piggyback data coming through as my vm’s have proxmox services identified. I went looking around in logs to try to find what piggyback data is missing and it lead me to the two statements in the output previously listed about no piggyback… Skip processing.
Checkmk has the host as FQDN to match the TLS certificate, the host is just the hostname in PVE. When I first added the host to checkmk, I didn’t use FQDN and it errored out. I could have disabled TLS checking but would rather not so I readded it with FQDN.
The IP, I’m not sure where it’s coming up with that as it’s not defined on the host in checkmk.
There is no piggyback data missing. The message comes only as you selected “Alwasy use and expect piggyback data”. This option don’t need to be set.
If you see these two services on your Proxmox host.
Then all is fine.
The wording in the blog article is a little bit misleading. It means for the objects where you receive piggyback data for you should make this setting.
I don’t think so - can you show how the host is now configured and the warning?
If you only see this warning at the “Check_MK Discovery” service than it’s fine. This service is only executed every 2, 4 or 6 hours. Depending on your configuration.
You’re right. I didn’t hit save Oops.
I remember seeing and activating 1 change on the site but it must have been for something else. It’s now correct and the warnings are gone. Thanks so much for your help!
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.
Oops.