Syncthing on Synology stops when connected to android phone

TennisTheMennis · August 11, 2018, 11:59pm

Fair warning, I am not at all well versed in console and other behind-the-shiny-GUI-procedures, so teaspoon explanations might be necessary.

I just installed Syncthing on my Synology DS415+ and my Moto G4. Both units are up to date as far as I can tell. After a bit of fiddling about I managed to get them to find each other, added a couple folders from the phone and it started to sync. Then, at some point, the process on the Synology stopped. I am unable to recall if I did anything particular at the time. Tried to run the program again, it starts and then stops. Repeated a few times. It might seem like it stops whenever it manages to connect with the phone. The problem persists after rebooting both the NAS and the phone. In the latest attempt it seemed to be stuck in a crash-restart loop, though the symptoms were similar to earlier attempts (Uptime showing >1m, frequent “does not seem to be running or network problem”-popups). I see that the version I got from the package center is the 14.49 and not the 14.50, however this is also the case for the android app. Is there an estimate for when then new version rolls out to the two platforms? After all, there would as far as I can understand be a chance of an update fixing the problem. Or creating a new one, but that is the way of things.

On a semi-related note, is it possible to change language in the android app interface. Having it in my native language does me no favours when all the help resources are in english.

AudriusButkevicius · August 12, 2018, 9:04am

You should check the logs on the crashing device.

TennisTheMennis · August 12, 2018, 10:10am

I do not know how to do that, apart from the NAS’ GUI log handler which does not give any word of Syncthing. Just to avoid misunderstandings, the program is crashing, not the entire device.

AudriusButkevicius · August 12, 2018, 11:55am

The logs are available from the web ui.

TennisTheMennis · August 12, 2018, 9:50pm

Right. I found the log interface, and it seemed like a good idea to switch on all the debug options before recreating the bug.

From what I can tell, it seems like the service tries to establish a connection to the phone using both IPv4 and IPv6. That is the only sense I was able to make from it all, but I thought it might be worth a mention. Here is the readout from what appears to be a couple of crash-restart loops:

Summary

    2018-08-13 00:37:24 http: GET "/rest/events?since=80": status 200, 3 bytes in 60000.32 ms
2018-08-13 00:37:24 http: GET "/rest/events?since=80": status 200, 3 bytes in 60000.25 ms
2018-08-13 00:37:26 http: GET "/rest/system/log?since=2018-08-13T00%3A37%3A24.365062262%2B03%3A00": status 200, 5930 bytes in 0.59 ms
2018-08-13 00:37:28 http: GET "/rest/system/log?since=2018-08-13T00%3A37%3A24.922850875%2B03%3A00": status 200, 242 bytes in 0.16 ms
2018-08-13 00:37:30 http: GET "/rest/system/log?since=2018-08-13T00%3A37%3A26.422975385%2B03%3A00": status 200, 241 bytes in 0.17 ms
2018-08-13 00:37:32 http: GET "/rest/system/log?since=2018-08-13T00%3A37%3A28.457521416%2B03%3A00": status 200, 240 bytes in 0.17 ms
2018-08-13 00:37:34 http: GET "/rest/system/status": status 200, 1242 bytes in 0.41 ms
2018-08-13 00:37:34 http: GET "/rest/system/discovery": status 200, 3 bytes in 0.13 ms
2018-08-13 00:37:34 http: GET "/rest/system/error": status 200, 21 bytes in 0.14 ms
2018-08-13 00:37:34 http: GET "/rest/system/connections": status 200, 806 bytes in 0.29 ms
2018-08-13 00:37:34 http: GET "/rest/system/log?since=2018-08-13T00%3A37%3A30.49304165%2B03%3A00": status 200, 929 bytes in 0.21 ms
2018-08-13 00:37:34 http: GET "/rest/system/status": status 200, 1242 bytes in 0.38 ms
2018-08-13 00:37:34 http: GET "/rest/system/discovery": status 200, 3 bytes in 0.09 ms
2018-08-13 00:37:34 http: GET "/rest/system/connections": status 200, 805 bytes in 0.27 ms
2018-08-13 00:37:34 http: GET "/rest/system/error": status 200, 21 bytes in 0.08 ms
2018-08-13 00:37:36 http: GET "/rest/system/log?since=2018-08-13T00%3A37%3A34.361226517%2B03%3A00": status 200, 928 bytes in 0.21 ms
2018-08-13 00:37:36 recv 69 bytes from [fe80::d204:1ff:fe3c:bf4c%eth1]:37875
2018-08-13 00:37:36 discover: Received local announcement from [fe80::d204:1ff:fe3c:bf4c%eth1]:37875 for ST4MNKR-ZVPEUOA-55OEXCJ-WJ2EIYX-WVNFC57-6DQIUGU-F5ELASQ-UUBIRQX
2018-08-13 00:37:36 discover: Registering addresses for ST4MNKR-ZVPEUOA-55OEXCJ-WJ2EIYX-WVNFC57-6DQIUGU-F5ELASQ-UUBIRQX
2018-08-13 00:37:36 discover: Reconstructed URL is &url.URL{Scheme:"tcp", Opaque:"", User:(*url.Userinfo)(nil), Host:"[fe80::d204:1ff:fe3c:bf4c%eth1]:22000", Path:"", RawPath:"", ForceQuery:false, RawQuery:"", Fragment:""}
2018-08-13 00:37:36 discover: Replaced address 0.0.0.0 in tcp://0.0.0.0:22000 to get tcp://[fe80::d204:1ff:fe3c:bf4c%25eth1]:22000
2018-08-13 00:37:36 log 81 DeviceDiscovered map[device:ST4MNKR-ZVPEUOA-55OEXCJ-WJ2EIYX-WVNFC57-6DQIUGU-F5ELASQ-UUBIRQX addrs:[tcp://[fe80::d204:1ff:fe3c:bf4c%25eth1]:22000]]
2018-08-13 00:37:36 http: GET "/rest/events?since=80": status 200, 313 bytes in 11967.66 ms
2018-08-13 00:37:36 http: GET "/rest/events?since=80": status 200, 313 bytes in 11941.43 ms
2018-08-13 00:37:36 write udp [::]:47925->[ff12::8384]:21027: sendmsg: network is unreachable on write to [ff12::8384]:21027 lo
2018-08-13 00:37:36 write udp [::]:47925->[ff12::8384]:21027: sendmsg: network is unreachable on write to [ff12::8384]:21027 sit0
2018-08-13 00:37:36 write udp [::]:47925->[ff12::8384]:21027: sendmsg: network is unreachable on write to [ff12::8384]:21027 eth0
2018-08-13 00:37:36 sent 281 bytes to [ff12::8384]:21027 on eth1
2018-08-13 00:37:36 sent 281 bytes to [ff12::8384]:21027 on docker0
2018-08-13 00:37:36 recv 281 bytes from [fe80::211:32ff:fe41:f1cc%eth1]:47925
2018-08-13 00:37:36 sent 281 bytes to [ff12::8384]:21027 on docker7389c40
2018-08-13 00:37:36 recv 281 bytes from [fe80::42:eff:fe6f:64de%docker0]:47925
2018-08-13 00:37:36 recv 281 bytes from [fe80::4843:9dff:fe89:f98d%docker7389c40]:47925
2018-08-13 00:37:36 recv 281 bytes from [fe80::b4b6:aeff:fed0:c02d%docker40ddb22]:47925
2018-08-13 00:37:36 sent 281 bytes to [ff12::8384]:21027 on docker40ddb22
2018-08-13 00:37:36 discover: Received local announcement from [fe80::211:32ff:fe41:f1cc%eth1]:47925 for DOR3545-HAMAAQQ-IDVRPTK-2L2EAD6-ZAJK5KN-N2Z4QCG-7MR55O7-VFZEVAT
2018-08-13 00:37:36 discover: Received local announcement from [fe80::42:eff:fe6f:64de%docker0]:47925 for DOR3545-HAMAAQQ-IDVRPTK-2L2EAD6-ZAJK5KN-N2Z4QCG-7MR55O7-VFZEVAT
2018-08-13 00:37:36 discover: Received local announcement from [fe80::4843:9dff:fe89:f98d%docker7389c40]:47925 for DOR3545-HAMAAQQ-IDVRPTK-2L2EAD6-ZAJK5KN-N2Z4QCG-7MR55O7-VFZEVAT
2018-08-13 00:37:36 discover: Received local announcement from [fe80::b4b6:aeff:fed0:c02d%docker40ddb22]:47925 for DOR3545-HAMAAQQ-IDVRPTK-2L2EAD6-ZAJK5KN-N2Z4QCG-7MR55O7-VFZEVAT
2018-08-13 00:37:36 recv 69 bytes from 192.168.10.195:40441
2018-08-13 00:37:36 discover: Received local announcement from 192.168.10.195:40441 for ST4MNKR-ZVPEUOA-55OEXCJ-WJ2EIYX-WVNFC57-6DQIUGU-F5ELASQ-UUBIRQX
2018-08-13 00:37:36 discover: Registering addresses for ST4MNKR-ZVPEUOA-55OEXCJ-WJ2EIYX-WVNFC57-6DQIUGU-F5ELASQ-UUBIRQX
2018-08-13 00:37:36 discover: Reconstructed URL is &url.URL{Scheme:"tcp", Opaque:"", User:(*url.Userinfo)(nil), Host:"192.168.10.195:22000", Path:"", RawPath:"", ForceQuery:false, RawQuery:"", Fragment:""}
2018-08-13 00:37:36 discover: Replaced address 0.0.0.0 in tcp://0.0.0.0:22000 to get tcp://192.168.10.195:22000
2018-08-13 00:37:36 log 82 DeviceDiscovered map[device:ST4MNKR-ZVPEUOA-55OEXCJ-WJ2EIYX-WVNFC57-6DQIUGU-F5ELASQ-UUBIRQX addrs:[tcp://192.168.10.195:22000]]
2018-08-13 00:37:36 addresses: [1.2.3.255 192.168.10.255 172.17.255.255]
2018-08-13 00:37:36 sent 281 bytes to 1.2.3.255:21027
2018-08-13 00:37:36 recv 281 bytes from 1.2.3.1:37957
2018-08-13 00:37:36 recv 281 bytes from 192.168.10.173:37957
2018-08-13 00:37:36 discover: Received local announcement from 1.2.3.1:37957 for DOR3545-HAMAAQQ-IDVRPTK-2L2EAD6-ZAJK5KN-N2Z4QCG-7MR55O7-VFZEVAT
2018-08-13 00:37:36 discover: Received local announcement from 192.168.10.173:37957 for DOR3545-HAMAAQQ-IDVRPTK-2L2EAD6-ZAJK5KN-N2Z4QCG-7MR55O7-VFZEVAT
2018-08-13 00:37:36 sent 281 bytes to 192.168.10.255:21027
2018-08-13 00:37:36 sent 281 bytes to 172.17.255.255:21027
2018-08-13 00:37:36 recv 281 bytes from 172.17.0.1:37957
2018-08-13 00:37:36 discover: Received local announcement from 172.17.0.1:37957 for DOR3545-HAMAAQQ-IDVRPTK-2L2EAD6-ZAJK5KN-N2Z4QCG-7MR55O7-VFZEVAT
2018-08-13 00:37:36 recv 69 bytes from [fe80::d204:1ff:fe3c:bf4c%eth1]:37875
2018-08-13 00:37:36 discover: Received local announcement from [fe80::d204:1ff:fe3c:bf4c%eth1]:37875 for ST4MNKR-ZVPEUOA-55OEXCJ-WJ2EIYX-WVNFC57-6DQIUGU-F5ELASQ-UUBIRQX
2018-08-13 00:37:36 discover: Registering addresses for ST4MNKR-ZVPEUOA-55OEXCJ-WJ2EIYX-WVNFC57-6DQIUGU-F5ELASQ-UUBIRQX
2018-08-13 00:37:36 discover: Reconstructed URL is &url.URL{Scheme:"tcp", Opaque:"", User:(*url.Userinfo)(nil), Host:"[fe80::d204:1ff:fe3c:bf4c%eth1]:22000", Path:"", RawPath:"", ForceQuery:false, RawQuery:"", Fragment:""}
2018-08-13 00:37:36 discover: Replaced address 0.0.0.0 in tcp://0.0.0.0:22000 to get tcp://[fe80::d204:1ff:fe3c:bf4c%25eth1]:22000
2018-08-13 00:37:36 recv 69 bytes from 192.168.10.195:40441
2018-08-13 00:37:36 discover: Received local announcement from 192.168.10.195:40441 for ST4MNKR-ZVPEUOA-55OEXCJ-WJ2EIYX-WVNFC57-6DQIUGU-F5ELASQ-UUBIRQX
2018-08-13 00:37:36 discover: Registering addresses for ST4MNKR-ZVPEUOA-55OEXCJ-WJ2EIYX-WVNFC57-6DQIUGU-F5ELASQ-UUBIRQX
2018-08-13 00:37:36 discover: Reconstructed URL is &url.URL{Scheme:"tcp", Opaque:"", User:(*url.Userinfo)(nil), Host:"192.168.10.195:22000", Path:"", RawPath:"", ForceQuery:false, RawQuery:"", Fragment:""}
2018-08-13 00:37:36 discover: Replaced address 0.0.0.0 in tcp://0.0.0.0:22000 to get tcp://192.168.10.195:22000
2018-08-13 00:37:36 http: GET "/rest/events?since=81": status 200, 293 bytes in 0.22 ms
2018-08-13 00:37:36 http: GET "/rest/events?since=81": status 200, 293 bytes in 0.20 ms
2018-08-13 00:37:38 http: GET "/rest/system/log?since=2018-08-13T00%3A37%3A34.671439494%2B03%3A00": status 200, 10559 bytes in 0.84 ms
2018-08-13 00:37:40 http: GET "/rest/system/log?since=2018-08-13T00%3A37%3A36.933273248%2B03%3A00": status 200, 243 bytes in 0.15 ms
2018-08-13 00:37:42 http: GET "/rest/system/log?since=2018-08-13T00%3A37%3A38.643943432%2B03%3A00": status 200, 241 bytes in 0.15 ms
2018-08-13 00:37:44 http: GET "/rest/system/status": status 200, 1242 bytes in 0.40 ms
2018-08-13 00:37:44 http: GET "/rest/system/discovery": status 200, 194 bytes in 0.17 ms
2018-08-13 00:37:44 http: GET "/rest/system/connections": status 200, 806 bytes in 0.36 ms
2018-08-13 00:37:44 http: GET "/rest/system/error": status 200, 21 bytes in 0.11 ms
2018-08-13 00:37:44 http: GET "/rest/system/status": status 200, 1242 bytes in 0.39 ms
2018-08-13 00:37:44 http: GET "/rest/system/discovery": status 200, 194 bytes in 0.13 ms
2018-08-13 00:37:44 http: GET "/rest/system/error": status 200, 21 bytes in 0.12 ms
2018-08-13 00:37:44 http: GET "/rest/system/connections": status 200, 805 bytes in 0.26 ms
2018-08-13 00:37:44 http: GET "/rest/system/log?since=2018-08-13T00%3A37%3A40.679878869%2B03%3A00": status 200, 1623 bytes in 0.25 ms
2018-08-13 00:37:46 http: GET "/rest/system/log?since=2018-08-13T00%3A37%3A44.675381286%2B03%3A00": status 200, 241 bytes in 0.15 ms
2018-08-13 00:37:48 http: GET "/rest/system/log?since=2018-08-13T00%3A37%3A44.73296845%2B03%3A00": status 200, 241 bytes in 0.15 ms
2018-08-13 00:37:50 http: GET "/rest/system/log?since=2018-08-13T00%3A37%3A46.782850846%2B03%3A00": status 200, 240 bytes in 0.15 ms
2018-08-13 00:37:52 http: GET "/rest/system/log?since=2018-08-13T00%3A37%3A48.810402743%2B03%3A00": status 200, 241 bytes in 0.16 ms
2018-08-13 00:37:54 http: GET "/rest/system/status": status 200, 1242 bytes in 0.39 ms
2018-08-13 00:37:54 http: GET "/rest/system/discovery": status 200, 194 bytes in 0.16 ms
2018-08-13 00:37:54 http: GET "/rest/system/connections": status 200, 806 bytes in 0.27 ms
2018-08-13 00:37:54 http: GET "/rest/system/error": status 200, 21 bytes in 0.11 ms
2018-08-13 00:37:54 http: GET "/rest/system/status": status 200, 1242 bytes in 0.43 ms
2018-08-13 00:37:54 http: GET "/rest/system/discovery": status 200, 194 bytes in 0.12 ms
2018-08-13 00:37:54 http: GET "/rest/system/connections": status 200, 806 bytes in 0.28 ms
2018-08-13 00:37:54 http: GET "/rest/system/error": status 200, 21 bytes in 0.09 ms
2018-08-13 00:37:54 write udp [::]:47925->[ff12::8384]:21027: sendmsg: network is unreachable on write to [ff12::8384]:21027 lo
2018-08-13 00:37:54 write udp [::]:47925->[ff12::8384]:21027: sendmsg: network is unreachable on write to [ff12::8384]:21027 sit0
2018-08-13 00:37:54 write udp [::]:47925->[ff12::8384]:21027: sendmsg: network is unreachable on write to [ff12::8384]:21027 eth0
2018-08-13 00:37:54 addresses: [1.2.3.255 192.168.10.255 172.17.255.255]
2018-08-13 00:37:54 sent 281 bytes to [ff12::8384]:21027 on eth1
2018-08-13 00:37:54 recv 281 bytes from 1.2.3.1:37957
2018-08-13 00:37:54 sent 281 bytes to [ff12::8384]:21027 on docker0
2018-08-13 00:37:54 sent 281 bytes to [ff12::8384]:21027 on docker7389c40
2018-08-13 00:37:54 sent 281 bytes to [ff12::8384]:21027 on docker40ddb22
2018-08-13 00:37:54 discover: Received local announcement from 1.2.3.1:37957 for DOR3545-HAMAAQQ-IDVRPTK-2L2EAD6-ZAJK5KN-N2Z4QCG-7MR55O7-VFZEVAT
2018-08-13 00:37:54 recv 281 bytes from [fe80::211:32ff:fe41:f1cc%eth1]:47925
2018-08-13 00:37:54 recv 281 bytes from [fe80::42:eff:fe6f:64de%docker0]:47925
2018-08-13 00:37:54 recv 281 bytes from [fe80::4843:9dff:fe89:f98d%docker7389c40]:47925
2018-08-13 00:37:54 sent 281 bytes to 1.2.3.255:21027
2018-08-13 00:37:54 sent 281 bytes to 192.168.10.255:21027
2018-08-13 00:37:54 discover: Received local announcement from [fe80::211:32ff:fe41:f1cc%eth1]:47925 for DOR3545-HAMAAQQ-IDVRPTK-2L2EAD6-ZAJK5KN-N2Z4QCG-7MR55O7-VFZEVAT
2018-08-13 00:37:54 discover: Received local announcement from [fe80::42:eff:fe6f:64de%docker0]:47925 for DOR3545-HAMAAQQ-IDVRPTK-2L2EAD6-ZAJK5KN-N2Z4QCG-7MR55O7-VFZEVAT
2018-08-13 00:37:54 discover: Received local announcement from [fe80::4843:9dff:fe89:f98d%docker7389c40]:47925 for DOR3545-HAMAAQQ-IDVRPTK-2L2EAD6-ZAJK5KN-N2Z4QCG-7MR55O7-VFZEVAT
2018-08-13 00:37:54 recv 281 bytes from 192.168.10.173:37957
2018-08-13 00:37:54 recv 281 bytes from 172.17.0.1:37957
2018-08-13 00:37:54 recv 281 bytes from [fe80::b4b6:aeff:fed0:c02d%docker40ddb22]:47925
2018-08-13 00:37:54 discover: Received local announcement from [fe80::b4b6:aeff:fed0:c02d%docker40ddb22]:47925 for DOR3545-HAMAAQQ-IDVRPTK-2L2EAD6-ZAJK5KN-N2Z4QCG-7MR55O7-VFZEVAT
2018-08-13 00:37:54 discover: Received local announcement from 192.168.10.173:37957 for DOR3545-HAMAAQQ-IDVRPTK-2L2EAD6-ZAJK5KN-N2Z4QCG-7MR55O7-VFZEVAT
2018-08-13 00:37:54 discover: Received local announcement from 172.17.0.1:37957 for DOR3545-HAMAAQQ-IDVRPTK-2L2EAD6-ZAJK5KN-N2Z4QCG-7MR55O7-VFZEVAT
2018-08-13 00:37:54 sent 281 bytes to 172.17.255.255:21027
2018-08-13 00:37:54 http: GET "/rest/system/log?since=2018-08-13T00%3A37%3A50.842620783%2B03%3A00": status 200, 6270 bytes in 0.66 ms

Edit: Post formatting

AudriusButkevicius · August 12, 2018, 10:19pm

Check for panic files in syncthings home directory (you can check where it is by running syncthing on the command line using -paths)

TennisTheMennis · August 12, 2018, 10:40pm

So, I managed to SSH into the NAS, but I have no clue how to progress once I’m in the terminal.

TennisTheMennis · August 12, 2018, 11:02pm

After a bit of googling and departure from my comfort zone, I indeed fount a wall of panic files. Opening the newest one yields this:

Summary

[DOR35] 00:01:47 INFO: syncthing v0.14.49 "Dysprosium Dragonfly" (go1.10.3 linux-amd64) unknown-user@001ec240e008 2018-07-30 21:19:38 UTC
[DOR35] 00:01:47 INFO: My ID: DOR3545-HAMAAQQ-IDVRPTK-2L2EAD6-ZAJK5KN-N2Z4QCG-7MR55O7-VFZEVAT
[DOR35] 00:01:48 INFO: Single thread SHA256 performance is 93 MB/s using minio/sha256-simd (68 MB/s using crypto/sha256).
[DOR35] 00:01:50 INFO: Hashing performance is 81.12 MB/s
[DOR35] 00:01:50 INFO: Ready to synchronize "Kamera C-telefon" (73pv3-fywg5) (sendreceive)
[DOR35] 00:01:50 INFO: Ready to synchronize "C-telefon" (C-telefon) (sendreceive)
[DOR35] 00:01:50 INFO: Ready to synchronize "Andre Bilder C-telefon" (y5p5k-kvu3x) (sendreceive)
[DOR35] 00:01:50 INFO: Overall send rate is unlimited, receive rate is unlimited
[DOR35] 00:01:50 INFO: Rate limits do not apply to LAN connections
[DOR35] 00:01:50 INFO: TCP listener ([::]:22000) starting
...
[DOR35] 00:01:50 INFO: Relay listener (dynamic+https://relays.syncthing.net/endpoint) starting
[DOR35] 00:01:50 INFO: Device DOR3545-HAMAAQQ-IDVRPTK-2L2EAD6-ZAJK5KN-N2Z4QCG-7MR55O7-VFZEVAT is "NyNAS" at [dynamic]
[DOR35] 00:01:50 INFO: Device ST4MNKR-ZVPEUOA-55OEXCJ-WJ2EIYX-WVNFC57-6DQIUGU-F5ELASQ-UUBIRQX is "C-telefon" at [dynamic]
[DOR35] 00:01:50 INFO: Completed initial scan of sendreceive folder "Kamera C-telefon" (73pv3-fywg5)
[DOR35] 00:01:50 INFO: Completed initial scan of sendreceive folder "Andre Bilder C-telefon" (y5p5k-kvu3x)
[DOR35] 00:01:50 INFO: GUI and API listening on [::]:8384
[DOR35] 00:01:50 INFO: Access the GUI via the following URL: http://127.0.0.1:8384/
[DOR35] 00:01:50 INFO: Completed initial scan of sendreceive folder "C-telefon" (C-telefon)
[DOR35] 00:01:51 INFO: Established secure connection to ST4MNKR-ZVPEUOA-55OEXCJ-WJ2EIYX-WVNFC57-6DQIUGU-F5ELASQ-UUBIRQX at 192.168.10.173:45484-192.168.10.195:22000/tcp-client (TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305)
[DOR35] 00:01:51 INFO: Device ST4MNKR-ZVPEUOA-55OEXCJ-WJ2EIYX-WVNFC57-6DQIUGU-F5ELASQ-UUBIRQX client is "syncthing v0.14.49" named "moto x4" at 192.168.10.173:45484-192.168.10.195:22000/tcp-client
[DOR35] 00:01:51 INFO: Adding folder "Andre Bilder C-telefon" (y5p5k-kvu3x)
Panic at 2018-08-13T01:01:51+03:00
panic: cannot start already running folder y5p5k-kvu3x

Edit: Not all the text came, watch for updates. Another edit: The file has 1000 lines, I can paste the rest in the next post.

vincentardern · August 12, 2018, 11:06pm

That most recent file seems ok to me. It’s the normal startup procedure afaik. Are there any panic files that that are much larger in size than other files? You can see sizes with “ls -l” in the terminal.

TennisTheMennis · August 12, 2018, 11:11pm

I had not managed to get all of the text in, the first portion now includes the panic statement.

TennisTheMennis · August 12, 2018, 11:15pm

It appears that it for some reason tries to add a folder twice. I will remove the offending folder and see what happens.

TennisTheMennis · August 12, 2018, 11:31pm

It seems to have done the trick, however it did want to add a folder twice now as well. I had already turned off the auto accept from that unit, since I wanted to customize the paths, so I could choose to ignore the second addition. It is currently syncing up and behaving seemingly nice. I find it peculiar that it wanted to add a folder twice. Could it perchance be related to my pausing it in the android app while I tinkered with the settings on the NAS?

But so far, thank you so much for your help. I really wanted this to work as the program was rather in tune with my own logic. Again, thanks a heap for your pointers.

AudriusButkevicius · August 13, 2018, 6:09am

There is a bug with auto accept that will be fixed in the next version.

system · September 12, 2018, 6:17am

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