don't think that it's related to IPMI/Server board vs. Desktop board - but maybe it's something related to when the servers were setup - or secure-boot related... - do you happen to remember when you set them up? - and does `dmesg|grep -i secure`...
term.log received via different channel.
from the one you sent - looking through the large output - you can find:
Installing for x86_64-efi platform.
grub-install.real: error: cannot find EFI directory.
Failed: grub-install --target=x86_64-efi...
Hm - could I ask you for the term.log from the dist-upgrade in this case?
Maybe you ran into something we haven't considered yet - or something we could add a warning about to pve8to9 (and thus help users who yet have to upgrade)
Thanks!
After a Debian update, my PMG cluster is no longer synching. Main node is active and the two nodes are always in 'synching' state. Syslog keeps on showing on both nodes:
pmgtunnel[4515]: status update error: command 'ip -details -json link show'...
The instances were setup on top of Debian. These are Cloud VMs at Hetzner if this matters. Running since at least 2,5 years without any problems until now.
root@mx01:~# pmgcm status...
I think I found the issue and prepared a patch: https://lore.proxmox.com/pmg-devel/20250818131333.13364-1-s.ivanov@proxmox.com/T/#u
However
I'd still recommend to add an entry to your /etc/hosts which points your local hostname to a...
Thanks for adding the output and reporting that you're affected as well!
hm - did not manage to reproduce the issue here locally...
Could you additionally provide:
* the complete output of `pmgcm status`
* the contents of `/etc/pmg/cluster.conf`...
A fresh installation from the ISO has the contrib component for the Debian repositories enabled/included, while the docs: [1] do not mention it.
[1] https://pve.proxmox.com/pve-docs/chapter-sysadmin.html#_debian_base_repositories
Hmm we had a few similar reports - could you please share /var/log/apt/term.log (or the rotated variant that covers the upgrade from 8 to 9)?
my guess is - you still had `systemd-boot` installed while upgrading - see...
Please provide the output of `pmgversion -v`
else:
what's the output of `ip -details -json link show` ?
EDIT: did you reboot/restart any services after the upgrade? - if not - does restarting `pmgtunnel` make the warnings go away?
EDIT2...
The mail is blocked in your configured rules - more concretely by the rule called Blacklist - take a look there.
Just to have mentioned it explicitly: PMG 7.2 is EOL since over one year now - please consider updating to the latest version as...
The reason why we don't add it there is that this is a one-way street - once you've upgraded your zpools you cannot use a kernel that is shipping an older (minor) version for ZFS.
In general I'd recommend to rather upgrade a zpool if you need...
FYI, multiple (external) users reported [0] [1] [2] that processes with the name "kauditd0" were malware running on their system / containers, especially because they try to imitate a kernel thread but are clearly not a kernel thread at all.
[0]...
the results from address verification are cached - PMG uses postfix functionality for the recipient verification:
https://www.postfix.org/ADDRESS_VERIFICATION_README.html
and
https://www.postfix.org/verify.8.html
show which parameters can be used...
No - PMG does not have a permission system that is domain-aware - and for now we don't plan on implementing it.
And the tracking center is also not a privilege of its own
I hope this helps!