Thank you for testing!
Could you please run the following command on the `rsthost2` node and provide us with the output?
grep -r "192.168.165.22" /etc/
I would also check the the Corosync on which IP uses `rsthost2` node you can run `ss` as the following command:
ss -tulpn | grep corosync...
Thank you for the logs, could you please disable the firewall temporary to see if the issue related to the firewall config, especially for the Corosync traffic UDP ports 5404 and 5405.
Have you restarted the `systemctl restart pveproxy.service pvestatd.service`?
Do you still can't SSH to the another node from the hostname even after you modified the /etc/hosts?
Could you please provide us with the syslog from the `rsthost2`?
Hi,
Did you read our wiki guide about migrate to Proxmox VE [0]?
If you have a specific question, feel free to ask to give you more advice
[0] https://pve.proxmox.com/wiki/Migrate_to_Proxmox_VE
Hi,
Can you please check if the `net.ipv4.ip_forward=1` on the Proxmox VE node? you can run the following command to check:
sysctl net.ipv4.ip_forward
If not you may have to set it e.g.:
sysctl -w net.ipv4.ip_forward=1
Hello,
Proxmox VE is based on Debian, this means if your box can run the Ubuntu and Debian the Proxmox VE should run on it. As far as I know the `i5-4590T` supports Intel VT-x, this means the KVM should work as well.
Yes, we are looking for the issue. For a workaround you can create the user with its password in the same command e.g.:
proxmox-backup-manager user create <foo>@pbs --password <bar>
Hi,
pvestatd [0] daemon, this responsible for collecting and updating real-time infos on CPU, memory, disk and network usage.
[0] https://pve.proxmox.com/pve-docs/pvestatd.8.html