Search results

send a patch for this just yesterday: https://lore.proxmox.com/pbs-devel/20250818194026.840749-2-s.ivanov@proxmox.com/T/#u :) Thanks for the report in any case!

see: https://pmg.proxmox.com/pmg-docs/pmg-admin-guide.html#pmgconfig_template_engine - v320.pre is handled by the templateing system. I hope this helps!

Yes! (systems not using proxmox-boot-tool should have it mounted on /boot/efi) proxmox-boot-tool is (currently) used for all installations which are not using Ext4/XFS (with LVM) - it was initially added to handle ESPs for machines with multiple disks (and to add sensible support to UEFI...

See: https://pmg.proxmox.com/pmg-docs/pmg-admin-guide.html#pmgconfig_template_engine - the postfix configuration is done via templates. 127.0.0.1 is also called the loop-back ip (localhost) and is e.g. used to speak with services on the same computer via TCP/IP - PMG sends mails through the...

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` indicate that secure-boot is in use? anyways -...

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 WARNING: Bootloader is not properly installed...

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!

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 non-loopback-ip (for ipv4 one not starting with `127.`...

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` * the contents of `/etc/hosts` * the output of...

the latest version of `pve8to9` should warn you in that situation - anyways - glad you resolved your issue!

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: please provide the output from all your clusternodes...

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 soon as possible.

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 one of the new features and have ensured that your...

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 to tweak the lifetime of the cache. all mail...

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!

usually you can simply enable TLS in the GUI: https://pmg.proxmox.com/pmg-docs/pmg-admin-guide.html#pmgconfig_mailproxy_tls

Thanks - looking through them (and knowing what to search for) - shows: Replacing config file /etc/default/grub with new version Installing for x86_64-efi platform. grub-install.real: error: cannot find EFI directory. Failed: grub-install --target=x86_64-efi WARNING: Bootloader is not properly...

yes - can relate to that - it bit me while testing as well ... - We do try to add checks for more common problematic configurations to the `pve8to9` script (using proxmox-boot-tool, while having the ESP mounted on /boot/efi is nothing I've seen too often until now) to prevent some of the issues...

I guess you have mounted your btrfs (sda3, sdb3 at a directory - for the reminder assume /target) * check if you have /etc/kernel/proxmox-boot-uuids (this is the check if proxmox-boot-tool is used) - and the contents match the UUIDs of sda2 sda3 * if you have it - mount the proc,sys, and other...