Joshua Parker Ruehlig
Hall of Famer
- Joined
- Dec 5, 2011
- Messages
- 5,949
OK, so syncthing is being started successfully so the plugin middleware works fine. but either the freebsd build syncthing autoupdated to, or your specific data is causing it not to bind to a network socket.The 192.168.1.22 is my syncthing adress from router, and jail DHCP adress.
service syncthing onestatus
syncthing is running as pid 64268.
Ah.. from the jail log, sorry, i have looked on the root folder... my fault, there i have for example, on the newest panic log:
.....
goroutine 65 [select]:
github.com/syncthing/syncthing/lib/ignore.(*Matcher).clean(0xc208fa07d0, 0x68c61714000)
/go/src/github.com/syncthing/syncthing/lib/ignore/ignore.go:161 +0x1c9
created by github.com/syncthing/syncthing/lib/ignore.New
/go/src/github.com/syncthing/syncthing/lib/ignore/ignore.go:53 +0x170
goroutine 67 [select]:
github.com/syncthing/syncthing/lib/ignore.(*Matcher).clean(0xc208659ae0, 0x68c61714000)
/go/src/github.com/syncthing/syncthing/lib/ignore/ignore.go:161 +0x1c9
created by github.com/syncthing/syncthing/lib/ignore.New
/go/src/github.com/syncthing/syncthing/lib/ignore/ignore.go:53 +0x170
Bounch of such infos
this is application specific so I suggest you create a bug on syncthing's github page. you should post the syncthing log there and tell them this happened after an autoupdate.
you can also further try to isolate the issue by installing a second instance of syncthing and updating to the latest version. that will show if it's your specific data or the build they are pushing out.