Recent content by hvillemoes

Oh, I rest my case - this mail was actually logged. I'm sorry for the disturbance. Maybe the mails missing from the pmg logging was sent around pmg and directly to the recipient domain. I will look into that. I might close port 25 outgoing in my firewall :-)

2026-02-06T16:50:37.933740+01:00 mailgw postfix/smtpd[194687]: connect from localhost.localdomain[127.0.0.1] 2026-02-06T16:50:37.935643+01:00 mailgw postfix/smtpd[194687]: E4674E174A: client=localhost.localdomain[127.0.0.1], orig_client=odysseus[10.9.10.32] 2026-02-06T16:50:37.977550+01:00...

HI - I do not agree. My pmg is configuret as I have read the manual, that is: Mail from the internet to my domains are received by pmg on port 25 and after filtering relayed to my internal mailserver. These mails are logged and can be observed on the GUI. Mail fron internal senders to...

It seems, that external smtp mail sent via port 26 is not logged and cannot be displayed in the tracking center. How do I enable that logging ? Thanks / Harald

Setting NFS version to 4 and rebooting did the trick for me. Only rebooting did not help. Thank you all. / Harald

Cure found: systemctl restart pvestatd Storage icons, however, still has '?' status. root@flamme:~# systemctl status pvestatd â pvestatd.service - PVE Status Daemon Loaded: loaded (/lib/systemd/system/pvestatd.service; enabled; vendor preset: enabled) Active: active (running) since...

I can add, that pve-qemu-kvm: 6.1.0-2 worked flawless. Again thank you for the fast response and fix. / Harald

Thank you for your advice. I tried to "migrate" by restoring from my proxmox backup server. When I powered up the restored server, I got error messages from the /home xfs file system. I had similar problems, when I "migrated" the server from ESXi to proxmox. My conclusion is, that I must either...

Same result, the problem persists. VM config: root@proxmox3:/etc/pve/nodes/proxmox3/qemu-server# cat 10013.conf agent: 1 boot: order=sata0 cores: 8 memory: 32924 name: agurk8-webhotel net0: e1000=76:23:91:7F:A5:94,bridge=vmbr0,firewall=1 onboot: 1 ostype: l26 sata0...

root@proxmox3:~# pveversion -v proxmox-ve: 7.0-2 (running kernel: 5.11.22-7-pve) pve-manager: 7.0-14+1 (running version: 7.0-14+1/08975a4c) pve-kernel-helper: 7.1-4 pve-kernel-5.11: 7.0-10 pve-kernel-5.11.22-7-pve: 5.11.22-12 pve-kernel-5.11.22-5-pve: 5.11.22-10 pve-kernel-5.11.22-4-pve...

I tried to use the command line migrate with reduced transfer rate, but with same result: qm migrate 10013 proxmox2 --bwlimit 50000 --migration_type insecure --targetstorage data2 --online yes --with-local-disks yes ... drive-sata0: transferred 31.5 GiB of 100.0 GiB (31.52%) in 11m 4s...

Hi I get this kernel error during migrate to another host. This stops the VM and aborts the migrate. I have migrated the very same VM to this host a few days ago. Any idea will be appreciated. syslog: Nov 14 10:30:21 proxmox3 kernel: [94205.987480] kvm[2288]: segfault at 68 ip...

It works like a charm - only stone on the road was to add the existing storage to the new server, which had to be done manual in /etc/proxmox-backup/datastore.cfg

Thank you. I will test and if ok, use.

The purpose is to be able to recover after pve1 with pbs1 has crashed. Then I want to be able to restore on pve2 with pbs2. Would that work ? Can pbs2 recognize and understand the .lock and .chunk structure created by pbs1? It works when using build-in pve backup, but I want to use the nice...