Proxmox Cluster over Tinc VPN failed

[YoSiJo]

Hi, I wanted to create a Proxmox cluster and roughly followed this ( myatus.com/p/poor-mans-proxmox-cluster/) procedure.
But I fail because the second node can't join the cluster because Corosync complains.

Node 1 = skuld (10.8.0.1)
Node 2 = urd ( 10.8.0.2 )

root@urd:~# systemctl --stat=failed                                                                                                                                                                               
  UNIT             LOAD   ACTIVE SUB    DESCRIPTION                 
● corosync.service loaded failed failed Corosync Cluster Engine
● pvesr.service    loaded failed failed Proxmox VE replication runner
root@urd:~# systemctl status corosync                                                                                                                                                                             
● corosync.service - Corosync Cluster Engine
   Loaded: loaded (/lib/systemd/system/corosync.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Thu 2018-08-16 18:31:14 CEST; 5s ago
     Docs: man:corosync
           man:corosync.conf
           man:corosync_overview
  Process: 19323 ExecStart=/usr/sbin/corosync -f $COROSYNC_OPTIONS (code=exited, status=20)
 Main PID: 19323 (code=exited, status=20)
      CPU: 251ms

Aug 16 18:31:14 urd corosync[19323]: info    [WD    ] no resources configured.
Aug 16 18:31:14 urd corosync[19323]: notice  [SERV  ] Service engine loaded: corosync watchdog service [7]
Aug 16 18:31:14 urd corosync[19323]: notice  [QUORUM] Using quorum provider corosync_votequorum
Aug 16 18:31:14 urd corosync[19323]: crit    [QUORUM] Quorum provider: corosync_votequorum failed to initialize.
Aug 16 18:31:14 urd corosync[19323]: error   [SERV  ] Service engine 'corosync_quorum' failed to load for reason 'configuration error: nodelist or quorum.expected_votes must be configured!'
Aug 16 18:31:14 urd corosync[19323]: error   [MAIN  ] Corosync Cluster Engine exiting with status 20 at service.c:356.
Aug 16 18:31:14 urd systemd[1]: corosync.service: Main process exited, code=exited, status=20/n/a
Aug 16 18:31:14 urd systemd[1]: Failed to start Corosync Cluster Engine.
Aug 16 18:31:14 urd systemd[1]: corosync.service: Unit entered failed state.
Aug 16 18:31:14 urd systemd[1]: corosync.service: Failed with result 'exit-code'.
r

The problem is already discussed here ( pve.proxmox.com/wiki/Separate_Cluster_Network ), but in my opinion it doesn't fit, as Host's file is configured correctly on both nodes.

root@urd:~# cat /etc/hosts
127.0.0.1       localhost
10.8.0.1        skuld.hn.waimanu.io skuld
10.8.0.2        urd.wg.waimanu.io       urd pvelocalhost
root@skuld:~# cat /etc/hosts
127.0.0.1       localhost
10.8.0.1        skuld.hn.waimanu.io     skuld pvelocalhost
10.8.0.2        urd.wg.waimanu.io urd

omping:

root@skuld:~# omping urd skuld
urd : waiting for response msg
urd : joined (S,G) = (*, 232.43.211.234), pinging
urd :   unicast, seq=1, size=69 bytes, dist=0, time=23.697ms
urd : multicast, seq=1, size=69 bytes, dist=0, time=24.061ms
urd :   unicast, seq=2, size=69 bytes, dist=0, time=23.975ms
urd : multicast, seq=2, size=69 bytes, dist=0, time=24.054ms
urd :   unicast, seq=3, size=69 bytes, dist=0, time=23.737ms
urd : multicast, seq=3, size=69 bytes, dist=0, time=23.773ms

 

[udo]

Hi,
I guess your network latencies are to high for corosync!

Udo

 

[YoSiJo]

What's the maximum I can't take from the documentary?