Local discovery multiple instances: bind already in use


#21

Hell yes, there is shorewall and shorewall6 running. Yesterday I had ip6tables cleared but I kept the IPv4 tables in as otherwise the VPN won’t work.

In retrospect, I could have connected directly via wifi to that machine and cleared iptables as well.

So: back to .39 and clear all firewalls?


#22

It’s on a Pi/Raspbian. I’d like to run a fat LXD instance on it but I didn’t manage to last time I tried… So no, it’s plain-Jane old brctl stuff.


(Jakob Borg) #23

So firewalls are my prime suspect then. It’s not super clear to me whether the old versions you tested actually worked or just didn’t complain…


#24

Right. I’ll revert to .39 and try without firewalls.


#25

[quote=“calmh, post:23, topic:10730”] It’s not super clear to me whether the old versions you tested actually worked or just didn’t complain…[/quote]

They positively work.


(Jakob Borg) #26

Then it shouldn’t be a firewall issue, so I don’t know what it is.


#27

I’ll crack open another Pi, install a scratch system on it and try to reproduce the issue varying Syncthing and OS versions. Perhaps it is related to kernel compilation flags or?? I’ll post if I find anything. Thanks again for your time!


#28

I give up. For the life of me I can’t get .39 to work either on Raspbian/ARM or Debian/Intel (kvm): I always get IPv6 join foo failed: operation not supported

On the Pi I downgraded the kernel to 4.4.50, on the VM it is 3.16.0. I gave privileges to my users I removed firewalls and bridges I loaded the ipv6 module explicitely with autoconf=1 disable=0 disable_ipv6=0

I’m out of ideas, sorry.


(Jakob Borg) #29

Me too. Maybe someone else can chime in with a positive or negative experience to correlate.


(Audrius Butkevicius) #30

Have we ruled out the Go version?


(Jakob Borg) #31

Might be go version in combination with something, but since it works for me on Linux and stuff so it’s not completely broken.


#32

Jeeze I can’t get this out of my system…

I am quite new to this go thing, but I am slowly getting a hang of it. I took my debian Jessie VM and downloaded former releases. The VM has no bridge and only one routed interface (eth0). There is another dummy one (tap0) just for show. So it is a very simple setup.

This works:

wget https://github.com/syncthing/syncthing/releases/download/v0.14.37-rc.1/syncthing-linux-amd64-v0.14.37-rc.1.tar.gz
[QSYZQ] 2017/10/13 12:47:30.496657 main.go:638: INFO: syncthing v0.14.37-rc.1 "Dysprosium Dragonfly" (go1.8.3 linux-amd64) teamcity@build.syncthing.net 2017-08-19 14:36:56 UTC
[QSYZQ] 2017/10/13 12:47:32.983870 multicast.go:190: DEBUG: IPv6 join lo success
[QSYZQ] 2017/10/13 12:47:32.986446 multicast.go:190: DEBUG: IPv6 join eth0 success
[QSYZQ] 2017/10/13 12:47:32.986697 multicast.go:190: DEBUG: IPv6 join tap0 success

And this does not:

wget https://github.com/syncthing/syncthing/releases/download/v0.14.37-rc.2/syncthing-linux-amd64-v0.14.37-rc.2.tar.gz
[QSYZQ] 2017/10/13 12:50:42.735489 main.go:638: INFO: syncthing v0.14.37-rc.2 "Dysprosium Dragonfly" (go1.9rc2 linux-amd64) teamcity@build.syncthing.net 2017-08-22 06:48:25 UTC
[QSYZQ] 2017/10/13 12:50:45.246453 multicast.go:188: DEBUG: IPv6 join lo failed: operation not supported
[QSYZQ] 2017/10/13 12:50:45.246993 multicast.go:188: DEBUG: IPv6 join eth0 failed: operation not supported
[QSYZQ] 2017/10/13 12:50:45.247447 multicast.go:188: DEBUG: IPv6 join tap0 failed: operation not supported

NB:

[QSYZQ] 2017/10/13 12:50:45.283618 main.go:911: INFO: No automatic upgrades; STNOUPGRADE environment variable defined.
[QSYZQ] 2017/10/13 12:50:45.284409 main.go:918: WARNING: Syncthing should not run as a privileged or system user. Please consider using a normal user account.
cat /proc/cmdline 
BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64 root=UUID=3c0d1922-ee77-44cc-ba0f-8ec9cf1a2657 ro quiet selinux=0 apparmor=0 security=

Besides I overshot v37rc2 and tested rc3: same issue as rc2.

Adding the security-apparmor-selinux disable things did not make any difference.

So, the version of Go seems not something to rule out yet?

HTH


#33

All right. I went to golang.org and got go1.9.1 and go1.8.4

Then I applied your nice build howto

I got this with go1.9.1:

[P5GVV] 2017/10/13 13:19:20.069159 main.go:651: INFO: syncthing v0.14.39+11-gcdbb32d "Dysprosium Dragonfly" (go1.9.1 linux-amd64) pif@dev 2017-10-13 09:24:38 UTC
[P5GVV] 2017/10/13 13:19:22.587931 multicast.go:188: DEBUG: IPv6 join lo failed: operation not supported
[P5GVV] 2017/10/13 13:19:22.588167 multicast.go:188: DEBUG: IPv6 join eth0 failed: operation not supported
[P5GVV] 2017/10/13 13:19:22.588256 multicast.go:188: DEBUG: IPv6 join tap0 failed: operation not supported

yet I got that with go 1.8.4:

[P5GVV] 2017/10/13 13:27:50.110237 main.go:651: INFO: syncthing v0.14.39+11-gcdbb32d "Dysprosium Dragonfly" (go1.8.4 linux-amd64) pif@dev 2017-10-13 09:24:38 UTC
[P5GVV] 2017/10/13 13:27:53.274255 multicast.go:190: DEBUG: IPv6 join lo success
[P5GVV] 2017/10/13 13:27:53.276881 multicast.go:190: DEBUG: IPv6 join eth0 success
[P5GVV] 2017/10/13 13:27:53.277166 multicast.go:190: DEBUG: IPv6 join tap0 success

At least now I now I can rely on compiling from source if I must upgrade :slight_smile:


#34

Hi there. I’m running syncthing on Windows 10 and got the same Problem with the IPv6 join since the upgrade to versions build with go 1.9.

[6GIJ4] 2017/10/28 17:59:14.464425 main.go:651: INFO: syncthing v0.14.39 “Dysprosium Dragonfly” (go1.9 windows-amd64) teamcity@build.syncthing.net 2017-09-25 06:05:21 UTC

[6GIJ4] 2017/10/28 17:59:17.465534 multicast.go:188: DEBUG: IPv6 join Ethernet failed: operation not supported

[6GIJ4] 2017/10/28 17:59:17.465534 multicast.go:188: DEBUG: IPv6 join WLAN failed: operation not supported

[6GIJ4] 2017/10/28 17:59:17.465534 multicast.go:188: DEBUG: IPv6 join Loopback Pseudo-Interface 1 failed: operation not supported

Till then everything worked fine. When I have some time I’m going to build the latest version with go 1.8.4. I’ll tell you if I get it working then.


(system) #35

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