Error message:
[piggyback]: Piggyback file not updated by source ‘proxmox. mydomain. com’
Output of “cmk --debug -vvn proxmox. mydomain. com”:
...
Storing piggyback data for: 'proxmoxvm'
Trying to acquire lock on /omd/sites/cmk/tmp/check_mk/piggyback/proxmoxvm/proxmox. mydomain. com
Got lock on /omd/sites/cmk/tmp/check_mk/piggyback/proxmoxvm/proxmox.mydomain.com
Releasing lock on /omd/sites/cmk/tmp/check_mk/piggyback/proxmoxvm/proxmox.mydomain.com
Released lock on /omd/sites/cmk/tmp/check_mk/piggyback/uproxmoxvm/proxmox.mydomain.com
...
So piggyback data is definitely written to the system.
However:
Output of “cmk --debug -vvn proxmoxvm. mydomain. com”:
...
Piggyback file '/omd/sites/cmk/tmp/check_mk/piggyback/proxmoxvm. mydomain .com/proxmox.mydomain.com' is outdated (Piggyback file not updated by source 'proxmox.mydomain.com'). Skip processing.
...
So obviously, the proxmox host provides the piggyback data WITHOUT the vm FQDN, only the hostname, but the vm looks for the data with the FQDN.
I have created a rule to address this:
Host Name translation for piggybacked hosts:
Convert FQDN
Case Translation (all lower case)
This does works for my docker containers, but NOT for the proxmox vms…
btw, if I “cheat” by creating a symbolic link from /omd/sites/cmk/tmp/check_mk/piggyback/proxmoxvm.mydomain.com to /omd/sites/cmk/tmp/check_mk/piggyback/proxmoxvm, it works. So it seems to be a problem of FQDN vs. pure hostnames…
I assume that anything in piggyback gets regularly purged, so my link will be removed at some time in the future… so that’s not a sustainable solution?
I readed your first post also now you expect that your VM has an FQDN but you defined a rule that removes the domain part of your VM name.
If you make a renaming rule without FQDN and your VM exists inside Proxmox with FQDN then you should also receive the piggyback data with FQDN.
