Total chaos after wrong ip address

[Martino Rabe]

Hello,

I am currently using two Proxmox nodes. Unfortunately, after performing extended hardware maintenance on node2 and restarting the system, node2 received a different IP address than it had before (despite having set a static IP via its MAC address). This is where the issues began. After restarting, I noticed that node2 was visible in the webinterface but switched between offline and online every 30 seconds. I then configured the DHCP server to assign the old IP address back to the node (and restarted node2), but this behavior persisted, and replication continued to fail. For reference, here is the error message I received during replication:

Last successful sync: 2025-01-08 10:15:53
Next sync try: 2025-01-12 18:50:00
Failure count: 3
Note: The system will now reduce the frequency of error reports, as the job appears to be stuck.
Error:
command 'set -o pipefail && pvesm export zfs-disk:vm-105-disk-0 zfs - -with-snapshots 1 -snapshot __replicate_105-0_1736703300__ -base __replicate_105-0_1736327753__ | /usr/bin/ssh -e none -o 'BatchMode=yes' -o 'HostKeyAlias=redmountain' -o 'UserKnownHostsFile=/etc/pve/nodes/redmountain/ssh_known_hosts' -o 'GlobalKnownHostsFile=none' root@192.168.5.54 -- pvesm import zfs-disk:vm-105-disk-0 zfs - -with-snapshots 1 -snapshot __replicate_105-0_1736703300__ -allow-rename 0 -base __replicate_105-0_1736327753__' failed: exit code 255

Has anyone encountered a similar issue or have any suggestions on what I could check to resolve this problem?

 

[waltar]

root@node2:# ssh 192.168.5.54 # will show you additional info (IP which may be your node1 ?)
Set up your static reserved dhcp IP into your pve nodes !!!

 

[Martino Rabe]

IP address 192.168.5.54 is the IP address for node2.
Node1 has the 192.168.5.42.