Search results

Hi, I still not have tried that. However, you can try to resolve the IPv6 on both nodes in /etc/hosts i.e., remove the IPv4 from /etc/hosts and add the IPv6.

Hi, We offer support in German and English. Please consider posting in one of these languages for quicker help! Have you managed to resolve your issue?

Hi, Can access from other device? Have you tried to ping the Proxmox VE IP?

Hi, Please post the network config of your Proxmox VE `cat /etc/network/interfaces` and the VM config `qm config <VMID>`.

Hi, During the migrate the VM faced a temporary lock issue on the replication bitmaps as you see above two lines. This can occur if another replication or backup task is holding these resources during migration. So the question is; there is a replication or backup process during the migrateion?

Hi, You have to install and enable the Qemu-Guest-Agent [0] [0] https://pve.proxmox.com/wiki/Qemu-guest-agent

Could you please post the VM config? `qm config 100`

Hi, First, I would check the syslog what to know what happened! Then check the root disk space, you can run `df -h` command to see if the `/var` or/and `/` directory is full. Did you try to restart the failed services? systemctl restart pve-cluster pveproxy pvedaemon pvestatd pvescheduler...

Hi, Do you see anything in the syslog before and after the reboot in 30~ min? FYI, you can get the syslog with specific time/date in the Proxmox VE Web UI by going to `Datacenter -> {NodeName} -> System Log` Or using journalctl CLI e.g.: journalctl --since '2024-10-04 00:00:00' --until...

Hi, Do you see any failed services? You can run the following command to see what failed services: systemctl --failed

Hi, Can you please post the full output of the `qm start 100` command? You can run this command in the SSH or you can post the information included in the task error `Error: start failed: QEMU existed with code 1` in the [Task Log]. Also, verify the configuration of the SMB storage if the...

Hi, To help you better, please provide us with the Proxmox VE network configuration `cat /etc/network/interfaces` and the VM config `qm config <VMID>` replace the `<VMID>` with the ID of the VM mentioned. That can help us to identify if the issue is in the network config or the VM config.

If you want to know what happened exactly and how fixed the issue, you can post more information for the syslog/journalctl!

Glad to hear that you fix the issue yourself! If the old folder not needed, please move it to another path.

Yes. This won't help if the cluster itself loses quorum.

Hi, Could you please tell us which storage type your old Proxmox VE setup was using? e.g., ZFS, Ceph, or something else?

May you try to commit the `search local` in the `/etc/resolv.conf` and test ping google.com or 8.8.8.8?

Hi, Can you please check the `pct enter 101` of the LXC? And did you see other above provided output in the syslog? you can run `journalctl -f` and try to access the LXC Console in the Proxmox VE Web UI.

Ceph needs a MON majority for quorum; losing this halts operations.... An option is to add a lightweight `tiebreaker` node to the cluster, which doesn't need to store data but can maintain quorum. Plus consider using the `noout` flag during maintenance to avoid triggering recovery processes.

By default, a Ceph cluster requires a majority of nodes to maintain quorum! Note, with min_size=1, there is a risk of data loss if only one replica is available during a write operation.