ERROR: Cluster join aborted!

plouff

New Member
Nov 10, 2023
3
1
3
Why does node B refuse to join cluster on node A?
Both nodes are on the same LAN
Node b is empty (no vm)
The only thing between the 2 nodes is an hpe switch with IGMP snooping and querier enabled.
There is a pfsense box between isp and proxmox so it should not interfere with cluster.
Proxmox firewall is off, yet udp ports 5404-5412 seem to be closed.


nmap -sU -p 5404-5412 5404/udp closed hpoms-dps-lstn 5405/udp closed netsupport 5406/udp closed systemics-sox 5407/udp closed foresyte-clear 5408/udp closed foresyte-sec 5409/udp closed salient-dtasrv 5410/udp closed salient-usrmgr 5411/udp closed actnet 5412/udp closed continuus
 
thanks Chris,
Correct, empty node B (192.168.55.115) is failing to join already existing cluster node A (192.168.55.114).

here is the output message:
Establishing API connection with host '192.168.55.114' Login succeeded. check cluster join API version No cluster network links passed explicitly, fallback to local node IP '192.168.55.115' Request addition of this node An error occurred on the cluster node: can't add existing node 'pve' TASK ERROR: Cluster join aborted!
 
Last edited:

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!