Hi,
Thank you for the output!
The above entries look normal to me.
The error `err -5 - Input/output error` usually point to the problem of the disk, and since you tested to backup on a different storage and the other VMs backup works well, I would test the `backup mode` on Snapshot or Suspend...
Thank you for the output!
From the output of the corosync-cfgtool I don't see the IP of the px4-pra, is that full output? if yes - can you please check if the Corosync config is the same on all your 4 nodes? Can you also try to restart the corosync service and then provide us with the status...
Hi,
Thank you for the outputs!
To troubleshooting, I would:
- Test a backup on a different storage
- Does the issue only on the 101 VM?
- Could you check if the SSHFS mount is stable and accessible? You can test by manually copying a large file to the `/backup-shared/` and monitoring the...
Since that the `px4-pra` is in a different data center, there could be intermittent network latency or packet loss etc... causing Corosync. I would check the network stability between the nodes, and check if you have a rule for the Firewall.
Hi,
Thank you for the output!
You may have to set VLAN-aware to the `vmbr0` bridge as the following:
bridge-vlan-aware yes
bridge-vids 2-4094
And issue the following command to take the effect:
ifreload -a
Hi,
Can you please check the syslog in your nodes especially the `px4-pra` node. Could you also please share the corosync config and the network config and the output of `ip a` command from the `px4-pra`?
Hi,
The message said that the `enp3s0f1np1.2914` is not valid interface name. Can you please provide us with your network configuration and the VM config?
You can get the network config and the VM config by issuing the following commands:
cat /etc/network/interfaces
qm config <VMID>
Hi, can you please share the ACL for the admin user? you can find the ACL in /etc/pve/user.cfg this can help us to see if the permission you gave to the user is correct or not.
Glad to hear that the issue is fixed by editing the /etc/hosts file!
Regarding the installation of the Proxmox VE, I would try other Proxmox VE ISO as well as re-check the BIOS/Firmware if up-to-date.
Can you please provide us with the syslog since last boot? you can generate the syslog since last boot using `journalctl -b > $(hostname)-syslog.txt` command.
Hi,
Regarding the SSD not visible, can you tell us what Proxmox VE ISO version you tried exactly?
Regarding the access to the Proxmox VE Web UI, can you please provide us with the output of /etc/hosts and the network configuration `/etc/network/interfaces`.
Can you ping/ssh your Proxmox VE...
Hi,
I'm glad to hear that you solved the issue yourself!
I will go ahead and set your thread as [SOLVED] in order to help other people who have the same issue.
Hi,
Does the output of the Proxmox VE? If yes you don't have to use Ubuntu repository, instead you have to use the Proxmox VE respository. to fix that you can go to Web UI `Datacenter -> saocamilo -> Updates -> Repositories` disable and remove all Ubuntu repository and add only the repo related...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.