Search results

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...

That usually is not a problem - as TLS in SMTP is opportunistic - if your downstream/backend mailserver does not advertise STATTLS PMG should simply transfer the mails without TLS. If you run into problems - please share the logs - then we might be able to help...

hm - there were a few posts about mismatched grub stages after an upgrade ... I'd check if you can look through the ESP (EFI service partition) and try the proxmox/shim / proxmox/grub or BOOTX64.efi entries on them - most UEFIs have an option to select these... (maybe that's what Super Grub2...

Thanks - will try reproducing it with the 8.0 ISO - afaics it's a single disk system? yeah it's not the most straight-forward to read - but it does contain the most information - and in that case it points us to the issue with your system: This system is booted via proxmox-boot-tool, running...

Do you remember when the breaking systems were initially setup? - there were changes to how booting is handled for btrfs installs during PVE 8.0 - so it would help to know which ones make problems for you. * Are those UEFI or legacy BIOS setups? * RAID configuration or single-disk installs...

Do the guests in question have a RNG device configured? (see the changelog for PVE 8.4 - UEFI PXE boot needs on in recent versions : https://pve.proxmox.com/wiki/Roadmap#8.4-known-issues)

Thanks for the reminder about this thread! both the pve8to9 check and our recommendation have changed (since I suggested to keep systemd-boot installed). Currently you should uninstall the package if you don't need it (no root on ZFS with uefi) - and install the meta package in all cases after...

The check was adapted in the mean time to deal with that situation: https://lore.proxmox.com/all/175466070754.625540.12444949078147201723.b4-ty@proxmox.com/T/#u (the current recommendation is to remove the systemd-boot meta-package after upgrading - and ensuring that `efibootmgr -v` points to a...