Syncthing not running in MacOS Sierra Beta

supermarin · July 15, 2016, 8:04am

Got some more failures:

[AKFMZ] 00:58:53 INFO: TLS handshake (BEP/tcp): read tcp 10.0.1.11:22000->162.216.226.31:42242: read: connection reset by peer
[AKFMZ] 00:58:53 INFO: TLS handshake (BEP/tcp): EOF
[AKFMZ] 01:00:54 INFO: TLS handshake (BEP/tcp): read tcp 10.0.1.11:22000->162.216.226.31:42253: read: connection reset by peer
[AKFMZ] 01:02:54 INFO: Failed to exchange Hello messages with ...omitted... (xxx.xxx.xxx.xx:42257): write tcp 10.0.1.11:22000->162.216.226.31:42257: write: broken pipe
[AKFMZ] 01:02:54 INFO: TLS handshake (BEP/tcp): EOF

calmh · July 15, 2016, 11:11am

To be clear, I consider this a problem with macOS and not Syncthing. I expect Apple to resolve it if you report it to them, as you should as a beta tester. There is nothing we can do from Synching side at the moment, posting logs here doesn’t help.

supermarin · July 15, 2016, 5:50pm

Agreed, discovered it happens on more places than just Syncthing. Posted here only for searchability in case people have a similar problem.

supermarin · July 17, 2016, 12:13am

Just in case someone else reads this, it’s caused by ntpd.

Running sudo launchctl unload /System/Library/LaunchDaemons/org.ntp.ntpd.plist will fix it temporarily.

source: https://forums.docker.com/t/docker-beta-for-mac-does-not-work-and-hangs-frequently-on-macos-10-12/18109/5

calmh · July 17, 2016, 7:12am

Apparently a behavior change in Sierra triggers a Go runtime bug. That bug will be fixed in a Go release quite soon so we’ll be fine then.

calmh · July 18, 2016, 7:36pm

… which should be fixed in Go 1.6.3 released today, meaning that this build of the 0.14.0 release candidate should work fine on Sierra. Do test!

supermarin · July 27, 2016, 5:17pm

works!

krychek · July 28, 2016, 7:02am

I’m getting the same error messages after upgrading to Syncthing 0.14.2 on a DNS-320 NAS (Linux arm-32 2.6.31.8).

[XXXXX] 08:53:09 INFO: Failed to exchange Hello messages with XXXXX-XXXXX-XXXXX-XXXXX-XXXXX-XXXXX-XXXXX-XXXXX (192.168.1.167:50458): EOF
[XXXXX] 08:53:16 INFO: TLS handshake (BEP/tcp): EOF
[XXXXX] 08:53:24 INFO: TLS handshake (BEP/tcp): EOF
[XXXXX] 08:53:46 INFO: Failed to exchange Hello messages with XXXXX-XXXXX-XXXXX-XXXXX-XXXXX-XXXXX-XXXXX-XXXXX (192.168.1.109:51064): EOF
[XXXXX] 08:54:00 INFO: Failed to exchange Hello messages with XXXXX-XXXXX-XXXXX-XXXXX-XXXXX-XXXXX-XXXXX-XXXXX (192.168.1.101:51163): EOF
[XXXXX] 08:54:05 INFO: TLS handshake (BEP/tcp): EOF
[XXXXX] 08:54:11 INFO: TLS handshake (BEP/tcp): EOF

I have no problem an a 64bit Ubuntu 14.04 machine with the same version of Syncthing. Maybe the fix in the Go language hasn’t reached the arm version yet?

AudriusButkevicius · July 28, 2016, 7:34am

Check the other sides logs.

krychek · July 28, 2016, 8:00am

I set STTRACE to upnp,nat,pmp,discovery.

I’m getting a bunch of these messages:

[XXXXX] 2016/07/28 09:53:06.824175 tcp_listen.go:113: INFO: TLS handshake (BEP/tcp): EOF
[XXXXX] 2016/07/28 09:53:08.441473 local.go:176: DEBUG: discover: Received local announcement from 192.168.1.109:61988 for XXXXX-XXXXX-XXXXX-XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
[XXXXX] 2016/07/28 09:53:08.444235 local.go:208: DEBUG: discover: Registering addresses for XXXXX-XXXXX-XXXXX-XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
[XXXXX] 2016/07/28 09:53:08.445084 local.go:242: DEBUG: discover: Reconstructed URL is &url.URL{Scheme:"tcp", Opaque:"", User:(*url.Userinfo)(nil), Host:"192.168.1.109:22000", Path:"", RawPath:"", RawQuery:"", Fragment:""}
[XXXXX] 2016/07/28 09:53:08.445533 local.go:244: DEBUG: discover: Replaced address 0.0.0.0 in tcp://0.0.0.0:22000 to get tcp://192.168.1.109:22000

Do you want me to send more output?

krychek · July 28, 2016, 8:18am

Here is some more:

[XXXXX] 2016/07/28 10:15:47.743355 service.go:179: INFO: Failed to exchange Hello messages with XXXXX-XXXXX-XXXXX-XXXXX-XXXXX-XXXXX-XXXXX-XXXXX (192.168.1.101:52325): EOF
[XXXXX] 2016/07/28 10:15:52.172839 tcp_listen.go:113: INFO: TLS handshake (BEP/tcp): EOF

I had no problem before upgrading to v14. There was no change in the router’s configuration or anywhere else in the network.

(I’m only limited to write 3 posts to this thread as a new user…)

AudriusButkevicius · July 28, 2016, 8:33am

It just looks like you either have a very bad connection, or some firewall gets in the way.

okket · July 29, 2016, 10:54am

I have not tested that exactly build, but homebrew golang-1.6.3 / syncthing-0.14.2 work fine for me the first time on Sierra Beta (16A254g). Earlier versions did not (not tested all of them).

okket · August 1, 2016, 9:09pm

macOS Sierra beta 4 was released a few hours ago and broke go/syncthing again.

calmh · August 2, 2016, 5:48am

Awesome

okket · August 2, 2016, 7:11am

There is a hint of a fix for the current problem.

okket · August 2, 2016, 10:50pm

Looks like there will be a fix soon in Go 1.7 (rc5)

okket · August 3, 2016, 8:57am

Go 1.4 was not updated yet, so bootstrapping with homebrew on macOS Sierra beta 4 / public beta 3 fails. Currently I don’t know a simple/automated way to build / run Syncthing on macOS Sierra, but the Go team promised to update 1.4 when Apple released the final Sierra version.

calmh · August 3, 2016, 9:21am

You don’t need to bootstrap Go. Just downloading 1.7rc5 and building Syncthing should work fine.

okket · August 3, 2016, 9:44am

I meant automated building HEAD with homebrew (brew install syncthing --HEAD) fails because it wants to bootstrap go.

[edit] I see you can skip dependencies with --ignore-dependencies, so manually installing Go (don’t forget to setup $GOPATH) and it should work with homebrew again.

[edit2] Looks like it is not that easy, homebrew likes to keep things separate for good reasons and ignores the user specific environment (./build.sh: line 14: go: command not found). Back to checkout/compile by hand. It’s a beta after all, not complaining.