Search results

please send it to our development list - and provide a short explanation why this is needed in your case. Thanks!

hmm - check if there are some files in `/etc/ssh/ssh_config.d/` - or even a bit more general run - `grep -rE 'ssh-dss' /etc/` - check this on all nodes in your cluster! if that does not point to the issue - please open a new thread (feel free to mention me with @Stoiko Ivanov) - and share the...

as @LnxBil said - it would help a lot to know which commands you ran to get in that situation? (and to provide /var/log/apt/term.log and history.log from that upgrade) a very blind guess: did you maybe run `apt upgrade` instead of `apt dist-upgrade`?

No - the permission system in PMG is not domain aware - and for a very large part of the administration/configuration the settings are global (e.g. rules, most postfix configuration,...) I hope this helps!

Contributions are very welcome - thanks for the suggestion! We use a mail-based workflow - see https://pve.proxmox.com/wiki/Developer_Documentation for submitting patches.

from a quick look at the code: https://git.proxmox.com/?p=pve-container.git;a=blob;f=src/PVE/LXC/Setup/Base.pm;h=dbfc775c6f4769609c50caa6c8a7b91a91566080;hb=HEAD#l294 It should be set to true, if you set the containers IPv6 config to 'auto' (called SLAAC) in the GUI (did not test this explicitly...

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