Recent content by Moayad

Hi, The SPF reject usually means the service is still submitting mail to PMG on the external SMTP port 25, where SPF checks are applied. Could you please configure the internal service to use PMG as smarthost on the internal SMTP port, default 26 [0], and retest? If it must use port 25, add...

Hi @Chronos.Song I would check the `/etc/hostname` and see if contains only the short node name and that it resolves correctly, then restart or reboot hte affected node.

Hi, Thank you for sharing the soltuion. For your informaiton I set your thread as [SOLVED] to help other people who have the same issue.

Thank you for the output! The pool can perform well, but the affected VM image itself is slow. That is the important distinction. For the recreate, I would a temporary second RBD storage ID pointing to the same pool. That avoids direct manual renames in RBD and keeps PVE in control of the VM...

Thank you for the output! The `rbd bench` numbers are from a scratch image. That confirms the pool cluster can deliver high throughput, but it does not fully rule out an issue specific to the actual VM image object layout. We recently had a case where pool-level tests looked fine, but the...

Thank you for the test! Could you please run the following read-only benchmarks on the same RBD image used for VM 701? rbd bench --io-type read --io-size 64K --io-threads 1 --io-total 1G pool_nvme_vm/vm-701-disk-0 rbd bench --io-type read --io-size 1M --io-threads 1 --io-total 4G...

Thank you for the test and the output! At this point, this looks more like the Ceph RBD access path on the PVE side than a generic PBS side issue. Before going deeper into tracing, could you please test one non-critical ceph backend VM with `krbd` enabled and then rerun one backp there? If you...

Hi, Thank you for the output! Could you please share the output of `pveversion -v` from Proxmox VE and the output of `proxmox-backup-manager versions --verbose` from the Proxmox Backup Server, and the storage config i.e., `/etc/pve/storage.cfg` from PVE side? Have you tried to boot from the...

Could you please post the output of the following commands: mount df -h /

Hi, Are you logged in as the root user? Have you tried a different browser?

thanks! Most likely the Web UI showed a state `running` state for the VM 109 because corosync or cluster were in no quorum and status updates from pvestatd couldn't propagate. Hard to know/confirm without syslog.

Hi, To investigate more could you please provide syslog when the OOM and split brain happened until you started the 109 VM?

Could you please check the syslog as well?

Hi, Could you please check the `/etc/hosts` file? I would also check our wiki guide on renaming PVE node [0]. [0] https://pve.proxmox.com/wiki/Renaming_a_PVE_node

Hi, You can usually treat KVM guests like regular KVM VMs when migrating to Proxmox VE [0] [0] https://pve.proxmox.com/wiki/Migrate_to_Proxmox_VE