Cluster disconnected/out of sync, all devices appear disconnected for most of the time


#1

Have a cluster of 5 devices, one sync of 30 gigabytes is taking far too long, all devices appear disconnected, and it seems that from time to time one of them randomly connects, exchanges a few data (making some progress), then disconnect again for hours. Each device is behind different network setups but I never had any problem until this one, here are logs from one of them.

> 2018-02-08 09:27:51 Renewing TCP 0.0.0.0:22000 -> EXTERNAL:60258 mapping on 9f0865b3-f5da-4ad5-85b7-7404637fdf37
> 2018-02-08 09:27:51 Renewed TCP 0.0.0.0:22000 -> EXTERNAL:60258 mapping on 9f0865b3-f5da-4ad5-85b7-7404637fdf37
> 2018-02-08 09:27:51 Acquiring TCP 0.0.0.0:22000 mapping on NAT-PMP@192.168.1.1
> 2018-02-08 09:27:51 Error getting new lease on NAT-PMP@192.168.1.1 read udp 192.168.1.100:59400->192.168.1.1:5351: recvfrom: connection refused
> 2018-02-08 09:27:51 Error getting new lease on NAT-PMP@192.168.1.1 read udp 192.168.1.100:36103->192.168.1.1:5351: recvfrom: connection refused
> 2018-02-08 09:27:51 Error getting new lease on NAT-PMP@192.168.1.1 read udp 192.168.1.100:47901->192.168.1.1:5351: recvfrom: connection refused
> 2018-02-08 09:27:51 Error getting new lease on NAT-PMP@192.168.1.1 read udp 192.168.1.100:36670->192.168.1.1:5351: recvfrom: connection refused
> 2018-02-08 09:27:51 Error getting new lease on NAT-PMP@192.168.1.1 read udp 192.168.1.100:47392->192.168.1.1:5351: recvfrom: connection refused
> 2018-02-08 09:27:51 Error getting new lease on NAT-PMP@192.168.1.1 read udp 192.168.1.100:43287->192.168.1.1:5351: recvfrom: connection refused
> 2018-02-08 09:28:01 Error getting new lease on NAT-PMP@192.168.1.1 Timed out trying to contact gateway
> 2018-02-08 09:28:01 Error getting new lease on NAT-PMP@192.168.1.1 read udp 192.168.1.100:43540->192.168.1.1:5351: recvfrom: connection refused
> 2018-02-08 09:28:01 Error getting new lease on NAT-PMP@192.168.1.1 read udp 192.168.1.100:46371->192.168.1.1:5351: recvfrom: connection refused
> 2018-02-08 09:28:01 Error getting new lease on NAT-PMP@192.168.1.1 read udp 192.168.1.100:58675->192.168.1.1:5351: recvfrom: connection refused
> 2018-02-08 09:28:01 Failed to acquire TCP 0.0.0.0:22000 mapping on NAT-PMP@192.168.1.1
> 2018-02-08 09:47:10 kcp://0.0.0.0:22020 stun keepalive on stun.voipbuster.com:3478: failed to contact (<nil>)
> 2018-02-08 09:47:15 kcp://0.0.0.0:22020 stun addr resolution on stun.xten.com:3478: lookup stun.xten.com on 192.168.1.1:53: read udp 192.168.1.100:57751->192.168.1.1:53: read: connection refused
> 2018-02-08 09:47:20 kcp://0.0.0.0:22020 stun addr resolution on stun.counterpath.com:3478: lookup stun.counterpath.com on 192.168.1.1:53: read udp 192.168.1.100:49574->192.168.1.1:53: read: connection refused
> 2018-02-08 09:47:25 kcp://0.0.0.0:22020 stun addr resolution on stun.ideasip.com:3478: lookup stun.ideasip.com on 192.168.1.1:53: read udp 192.168.1.100:38064->192.168.1.1:53: i/o timeout
> 2018-02-08 09:47:25 kcp://0.0.0.0:22020 stun addr resolution on stun.voipstunt.com:3478: lookup stun.voipstunt.com on 192.168.1.1:53: read udp 192.168.1.100:46020->192.168.1.1:53: read: connection refused
> 2018-02-08 09:47:30 kcp://0.0.0.0:22020 stun addr resolution on stun.schlund.de:3478: lookup stun.schlund.de on 192.168.1.1:53: read udp 192.168.1.100:58903->192.168.1.1:53: read: connection refused
> 2018-02-08 09:52:40 kcp://0.0.0.0:22020 resolved external address kcp://81.242.116.140:22020 (via stun.voip.aebc.com:3478)
> 2018-02-08 09:58:01 Renewing TCP 0.0.0.0:22000 -> EXTERNAL:60258 mapping on 9f0865b3-f5da-4ad5-85b7-7404637fdf37
> 2018-02-08 09:58:01 Renewed TCP 0.0.0.0:22000 -> EXTERNAL:60258 mapping on 9f0865b3-f5da-4ad5-85b7-7404637fdf37
> 2018-02-08 09:58:01 Removing NAT port mapping: external TCP address 81.242.115.254:60258, NAT 9f0865b3-f5da-4ad5-85b7-7404637fdf37 is no longer available.
> 2018-02-08 09:58:01 New NAT port mapping: external TCP address 81.242.116.140:60258 to local address 0.0.0.0:22000.
> 2018-02-08 09:58:01 Acquiring TCP 0.0.0.0:22000 mapping on NAT-PMP@192.168.1.1
> 2018-02-08 09:58:01 Error getting new lease on NAT-PMP@192.168.1.1 read udp 192.168.1.100:56805->192.168.1.1:5351: recvfrom: connection refused
> 2018-02-08 09:58:01 Error getting new lease on NAT-PMP@192.168.1.1 read udp 192.168.1.100:34510->192.168.1.1:5351: recvfrom: connection refused
> 2018-02-08 09:58:01 Error getting new lease on NAT-PMP@192.168.1.1 read udp 192.168.1.100:32951->192.168.1.1:5351: recvfrom: connection refused
> 2018-02-08 09:58:01 Error getting new lease on NAT-PMP@192.168.1.1 read udp 192.168.1.100:37924->192.168.1.1:5351: recvfrom: connection refused
> 2018-02-08 09:58:01 Error getting new lease on NAT-PMP@192.168.1.1 read udp 192.168.1.100:43458->192.168.1.1:5351: recvfrom: connection refused
> 2018-02-08 09:58:01 Error getting new lease on NAT-PMP@192.168.1.1 read udp 192.168.1.100:58806->192.168.1.1:5351: recvfrom: connection refused
> 2018-02-08 09:58:11 Error getting new lease on NAT-PMP@192.168.1.1 Timed out trying to contact gateway
> 2018-02-08 09:58:11 Error getting new lease on NAT-PMP@192.168.1.1 read udp 192.168.1.100:50349->192.168.1.1:5351: recvfrom: connection refused
> 2018-02-08 09:58:11 Error getting new lease on NAT-PMP@192.168.1.1 read udp 192.168.1.100:53097->192.168.1.1:5351: recvfrom: connection refused
> 2018-02-08 09:58:11 Error getting new lease on NAT-PMP@192.168.1.1 read udp 192.168.1.100:51280->192.168.1.1:5351: recvfrom: connection refused
> 2018-02-08 09:58:11 Failed to acquire TCP 0.0.0.0:22000 mapping on NAT-PMP@192.168.1.1

(Audrius Butkevicius) #2

These logs are of NAT mappings which is not immensely useful. You should provide full logs (perhaps with connections debug facility enabled) from the two devices that fail to connect.


(system) #3

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.