Hello to the proxmox community,
I looked at my logs because one host of a 2-node cluster (with external quorum device) is not reachable many times but not regular.
There I found this line of syslog (journalctl):
Then I looked at other VMs and CTs and there it is working fine. What means the exit code 255? Is it a known problem / bug whatever?
I look forward that the community can help me here
Answers in German are also good
UPDATE: Maybe the replication errors was because I changed the sshd_config a few months ago to disable ssh-rsa. But there were old ssh-rsa host keys in the /etc/pve/nodes/<nodename>/ssh_known_hosts files...
But the source problem why I started the troubleshooting is that one node is failing again and again. There are no messages in the syslog I think are responsible for that. The memory is working properly, I had run memtest a few weeks ago where also an outage was before...
I hope you have another ideas
I looked at my logs because one host of a 2-node cluster (with external quorum device) is not reachable many times but not regular.
There I found this line of syslog (journalctl):
Code:
got unexpected replication job error - command '/usr/bin/ssh -e none -o 'BatchMode=yes' -o 'HostKeyAlias=dell' -o 'UserKnownHostsFile=/etc/pve/nodes/dell/ssh_known_hosts' -o 'GlobalKnownHostsFile=none' root@192.168.88.254 pvecm mtunnel -migration_network 192.168.34.10/25 -get_migration_ip' failed: exit code 255
Then I looked at other VMs and CTs and there it is working fine. What means the exit code 255? Is it a known problem / bug whatever?
I look forward that the community can help me here
Answers in German are also good
UPDATE: Maybe the replication errors was because I changed the sshd_config a few months ago to disable ssh-rsa. But there were old ssh-rsa host keys in the /etc/pve/nodes/<nodename>/ssh_known_hosts files...
But the source problem why I started the troubleshooting is that one node is failing again and again. There are no messages in the syslog I think are responsible for that. The memory is working properly, I had run memtest a few weeks ago where also an outage was before...
I hope you have another ideas
Last edited: