Proxmon 4.4 clusters /etc/pve/local/pve-ssl.key: failed to load

[Zunix]

When i add the node with
pvecm add IP

Its saying
"Job for corosync.service failed. See 'systemctl status corosync.service' and 'journalctl -xn' for details.

waiting for quorum..."

I did the journalctl -xn

Appear

/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 1618.

What i did wrong?

 

[MasterTH]

please post ipconfigs of the servers
was the server in the cluster before?

 

[Zunix]

Server installed fresh. There was no any cluster before.
On server 1

lo Link encap:Local Loopback

inet addr:127.0.0.1 Mask:255.0.0.0

inet6 addr: ::1/128 Scope:Host

UP LOOPBACK RUNNING MTU:65536 Metric:1

RX packets:230434 errors:0 dropped:0 overruns:0 frame:0

TX packets:230434 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1

RX bytes:33877570 (32.3 MiB) TX bytes:33877570 (32.3 MiB)
vmbr0 Link encap:Ethernet HWaddr xx:xx:xx:xx:xx:xx
inet addr:129.138.16.182 Bcast:129.138.16.255 Mask:255.255.255.0

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:441630 errors:0 dropped:0 overruns:0 frame:0

TX packets:49232 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:27830603 (26.5 MiB) TX bytes:16015409 (15.2 MiB)

vmbr1 Link encap:Ethernet HWaddr xx:xx:xx:xx:xx:xx

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:0 errors:0 dropped:0 overruns:0 frame:0

TX packets:7 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:0 (0.0 B) TX bytes:618 (618.0 B)


On second server

lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
options=1203<RXCSUM,TXCSUM,TXSTATUS,SW_TIMESTAMP>
inet 127.0.0.1 netmask 0xff000000
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
nd6 options=201<PERFORMNUD,DAD>

en0: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
options=b<RXCSUM,TXCSUM,VLAN_HWTAGGING>
ether xx:xx:xx:xx:xx:xx
inet 192.168.123.64 netmask 0xffff0000 broadcast 192.168.123.255
media: autoselect (1000baseT <full-duplex,flow-control>)
status: active

 

[MasterTH]

find the differnece:
inet 129.138.16.182
inet 192.168.123.64

you will not be able to get multicast working properly on these different subnets right?

 

[Zunix]

There are 2 different server in different subnet. its will not works? but they ping each other.

 

[MasterTH]

ping is not the only thing that has to work for a working cluster

https://pve.proxmox.com/wiki/Multicast_notes
=> Using omping to test multicast

 

[F_B]

I have the same problem.
We have a working cluster with 5 nodes.
Now having bought a new hardware it is not possible to join the cluster.
pveproxy says:
Feb 24 11:38:09 pav02s pveproxy[2378]: starting 1 worker(s)
Feb 24 11:38:09 pav02s pveproxy[6130]: worker exit
Feb 24 11:38:09 pav02s pveproxy[2378]: worker 6138 started
Feb 24 11:38:09 pav02s pveproxy[6137]: /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 1618.

omping and multicast ist working between all nodes including the new one.
Any suggestions what can I do?