Syncthing on Arch-RaspberryPi

Support
1

First of all, thanks to all the people who put their effort into this. It looks really really promising. Unfortunately I did not manage to get it running on my pi yet.

I installed it by modifying a PKGBUILD in the AUR, so that it would install the armv6 version of syncthing.

However, after starting it in systemd, the admin interface keeps stating that I should restart syncthing - starting it directly from the console leads to the following messages, after setting the appropriate STTRACE variables (“mc”)

mc: 23:41:52.241631 beacon.go:53: trying interface "lo"

mc: 23:41:52.250563 beacon.go:53: trying interface "ifb0" mc: 23:41:52.259772 beacon.go:53: trying interface "ifb1" mc: 23:41:52.267816 beacon.go:53: trying interface "eth0" mc: 23:41:52.278817 beacon.go:85: write udp4: network is unreachable

which would suggest the interface not being up. I am ssh-ing into the Pi, and eth0 is up:

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500         inet 192.168.2.50  netmask 255.255.255.0  broadcast 192.168.2.255         inet6 2003:58:4f00:5900:ba27:ebff:fe4b:ae44  prefixlen 64  scopeid 0x0         inet6 fe80::ba27:ebff:fe4b:ae44  prefixlen 64  scopeid 0x20         ether b8:27:eb:4b:ae:44  txqueuelen 1000  (Ethernet)         RX packets 11817  bytes 919242 (897.6 KiB)         RX errors 0  dropped 2  overruns 0  frame 0         TX packets 10183  bytes 1523747 (1.4 MiB)         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536         inet 127.0.0.1  netmask 255.0.0.0         inet6 ::1  prefixlen 128  scopeid 0x10         loop  txqueuelen 0  (Local Loopback)         RX packets 863  bytes 436570 (426.3 KiB)         RX errors 0  dropped 0  overruns 0  frame 0         TX packets 863  bytes 436570 (426.3 KiB)         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Any suggestions?

Thanks!

2

I doubt that’s related; that’s most likely from trying to announce on the ifb0 or ifb1 interfaces, whatever those are. What does the full startup look like, sans debugging options?

3

Ok, you’re right. Syncthing seems to run just fine, the problem was, that I had deactivated JavaScript - A reminder to activate it would be nice here.

Ok, so now I have connected two nodes. I exposed both hosts on 22000. So now, when I change a file on my desktop, the Pi gets some information but tells me:

11:36:14.976: Connection to desktop closed: unexpected EOF

It seems to be working though.

Well, I guess I can live with that. Thanks for your feedback!

4

That shouldn’t happen during normal operations. There is probably an error on the other side, or you restarted syncthing?

5

I hope it’s okay to hijack this thread. I have a similar setup, Arch Linux on a Raspberry Pi. My network configuration is fairly simple and works, but when I start syncthing I get the following log:

[FIXZT] 2014/05/13 22:48:11 INFO: syncthing v0.8.5 (go1.2.2 linux-arm) jb@jborg-mbp 2014-05-11T18:46:09Z
[FIXZT] 2014/05/13 22:48:11 INFO: My ID:     XXXXXXX
[FIXZT] 2014/05/13 22:48:11 INFO: Starting web GUI on http://127.0.0.1:8080/
[FIXZT] 2014/05/13 22:48:11 INFO: Populating repository index
[FIXZT] 2014/05/13 22:48:14 INFO: No UPnP IGD device found, no port mapping created (read udp4 0.0.0.0:40455: i/o timeout)
[FIXZT] 2014/05/13 22:48:14 INFO: Sending local discovery announcements
[FIXZT] 2014/05/13 22:48:14 INFO: Sending global discovery announcements
[FIXZT] 2014/05/13 22:48:14 OK: Ready to synchronize default (read-write)
mc: 22:48:14.711964 beacon.go:94: write udp4: network is unreachable

Then nothing more happens. Any ideas how to fix this?

6

Nothing more, as in it fails to connect to any configured peers and so on? The first step would be to check for firewalls, perhaps hard code an IP address for a peer to see if the problem is discovery or connectivity.

7

For me it turned out syncthing was running all along and I just had to configure it correctly to make it work properly.

8