on a hunch - please compare the maximal message size (in the Mail Proxy Options) with the Maximal Spam Detector size - if the second is lower the issue is that the mail is not being shown to spamassassin completely which explains the modified...
Thanks, it looks the config correct, so the issue seems on the VM.
The network config on the VM doesn't sees to include auto start (auto) [0]; could you try to bring the interfacr up on the VM:
~# ifup enp6s18
[0]...
Da kann man jetzt keinen Rat geben, wenn man den Preis für den 4350 nicht kennt. Wenn der Preisunterschied im Bereich von sagen wir mal 20 Euro liegt, würde ich den größeren nehmen. Kerne und RAM kann man durch nichts ersetzen. 6 Kerne + HT, da...
Wenn, dann einem Ryzen PRO 5 5650G, der ist neuer als die Ryzen PRO 4000 Serie
und mit seinen 6C/ 12T kann man vieles Anstellen, auch HT deaktivieren um weitere ca - 40% Leistungsaufnahme einzusparen.
Dann laufen halt die Prozesse 40% länger in...
Your blocklist object lists:
* '.*@warsawexpo.e.*` as regex
* warsawaexpo.eu as domain
the mail's envelope sender is: 'sm.21177883674.m9f0c8k9bh6zheoe05-zaproszenie=warsawexpo.eu@emsgrid.com'
and does not match your object (there is no @ before...
Microsoft allows downgrade. you need to get media and product key yourself or ask your OEM manufacturer.
Media/Keys sources are not really relevant, proof of the original 2025 purchase is.
You can try the eval ISO to dig out. win11 eval ISO can...
@Stoiko Ivanov beat me to it ;)
Just to add the reference to the docs [1]:
[1] https://pmg.proxmox.com/pmg-docs/pmg-admin-guide.html#pmg_mailfilter_who
Your blocklist object lists:
* '.*@warsawexpo.e.*` as regex
* warsawaexpo.eu as domain
the mail's envelope sender is: 'sm.21177883674.m9f0c8k9bh6zheoe05-zaproszenie=warsawexpo.eu@emsgrid.com'
and does not match your object (there is no @ before...
I have successfully installed systemd-coredump, gdb, and pve-qemu-kvm-dbgsym on the node as suggested. However, this migration crash has not happened again since then.
If the issue recurs, I will make sure to capture and post the full stack...
Hi @Darkbotic,
there is a report in Debian about buggy firmware that won't boot a dual-signed shim. Maybe it's the same for your setup:
https://wiki.debian.org/SecureBoot/BuggyFirmware
I have successfully installed systemd-coredump, gdb, and pve-qemu-kvm-dbgsym on the node as suggested. However, this migration crash has not happened again since then.
If the issue recurs, I will make sure to capture and post the full stack...
Hi,
you can use apt install systemd-coredump gdb pve-qemu-kvm-dbgsym, then you can recover a full stack trace if the crash happens again. I also recommend updating to the current version...
Here is the part of storage.cfg
root@vnpttt-nvme-7003-s106:~# cat /etc/pve/storage.cfg | grep -A 2 -B 2 "vms"
username root@pam
zfspool: vms
pool rpool/vms
blocksize 16k
content images,rootdir
mountpoint /rpool/vms
sparse 1
As expected, creating these soft symlinks patched the issue for me.
ln -sf ../../sda3 /dev/disk/by-id/scsi-3500a0751e6e9b12b-part3
ln -sf ../../sdb3 /dev/disk/by-id/scsi-3500a0751e6e9b0bf-part3
But a more robust solution would have been...
zpool...