[SOLVED] Changed node IP and it is now giving a No route to host (595) error.

NotLarry

Active Member
Feb 26, 2019
7
2
43
35
We had to migrate one of our nodes (9 in total) to a new subnet. It's internal network stays the same.
We migrated 6 other nodes in the past with no issues.

After the ip change (vlan on the switch and in /etc/network/interfaces on the node)

No changes were made to corosync.conf (the ip addresses are not on the interface that changed)
No changes were made to /etc/hosts (again, no interfaces in the /etc/hosts file were changed).

/etc/pve is empty and trying to start pve-cluster results in a failure with the following error;

hvcms01pri pveproxy[3825]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1687
 
/etc/pve is empty and trying to start pve-cluster results in a failure with the following error;
seems like corosync is not running or the node cannot see the others (is not quorate) - check the journal for messages from corosync

I hope this helps!
 
<solved>

Did the following;
systemctl stop pve-cluster
systemctl stop corosync
moved /etc/pve to a temporary file
mkdir /etc/pve
/sbin/shutdown -r now

System came back
 
  • Like
Reactions: home-net-admin

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!