Recent content by Stoiko Ivanov

We added an entry to the known-issues section: https://pve.proxmox.com/wiki/Roadmap#Known_Issues_%26_Breaking_Changes Feedback welcome :)

Thanks for chiming in here! Very much appreciated! The 2 locations are probably indeed a oversight from me - Thanks for noticing! - I sent a patch: https://lore.proxmox.com/pve-devel/20260623102957.246597-1-s.ivanov@proxmox.com/T/#u memtest being newer could also be due to `bootctl install`...

I sent a patch to add the override for abstractions/consoles to the pve-devel list: https://lore.proxmox.com/pve-devel/20260622164522.836988-1-s.ivanov@proxmox.com/T/#u

A colleague managed to reproduce the issue locally - I failed because I checked inside tmux or via ssh :) It seems the issue is with `/etc/apparmor.d/dig` (or rather the included `/etc/apparmor.d/abstractions/console`) Could you try the following to verify that any of the changes below fixes...

Hm - could not reproduce dig not providing any output in a container that I installed fresh from the ubuntu 26.04 template (guessed the version based on `1:9.20.18-1ubuntu2.1` version for bind9-dnsutils) - here it produces the root-nameservers: # dig ; <<>> DiG 9.20.18-1ubuntu2.1-Ubuntu <<>>...

Thanks for digging into this, and the pointers to the OVH documentation! I was not aware that there is a way to explicitly tell which boot-entry to load - so that seems like a workaround if you want to keep the option to boot into rescue mode without going through the BIOS to change the...

No need to apologize! - I do see that it's a bit harder to read - I think I never noticed/wasn't bothered by it, as it looks fine in the template itself. I'll see if I can adapt the template to add linkebreaks there (without adding tons of whitespace if any of the options is not used. Thanks...

Thanks for the report - seems the case of having /var/spool/pmg on a dedicated mount-point/filesystem in a container was missed while testing - I sent a patch for discussion to the pmg-devel mailing-list. once this or an improved version has been merged the issue should be gone. Out of...

the config does work though? - I agree that this can be improved and would become more readable - but want to make sure that I don't miss something here?

There are mails originating from PMG (the bounces generated directly by postfix) that are not signed in PMG - could that be the source of the reported mails?

prinzipiell ist in der default config in einem PMG delay_warning_time auf 4h - sprich der ursprüngliche sender sollte von PMG eine mail bekommen, dass die mail noch nicht zugestellt werden konnte - siehe: https://www.postfix.org/postconf.5.html#delay_warning_time...

hm - if this also happens in a live-system that does not touch zfs before that's a bit odd (if anything or someone in the debian installation, tried running zpool import for all pools that would explain subsequent commands hanging) as is - restoring the data on the broken storage-01 pool from...

if the download manager uses many connections than it will run into rate-limits on all our download mirrors. Thanks for the feedback - would be great if you could try again with the other 2 hosts (with a short pause in between and a single wget) - might help us get a better view of how we could...

Quickly skimming through the thread here and the upstream issue (so I might have missed something). I think the core issue here is that the broken zpool storage-01 is still configured as storage in PVE? - in that case pvestatd would try to import it repeatedly - which would explain the hung...

hm - is this node part of a cluster ? - maybe the cluster sync interferes here? else - if you share the log - and your acme configuration files we might see something more. "transient data" - this includes quarantined mails, and the tracking-center (/var/log/syslog is not included in the...