"Out of sync items" doesn't change

Hello!

Not sure if this is a bug or not. On my Synology NAS, after upgrading to 0.14.3, I get “Out of sync items” forever. Prior to the upgrade, I had 5945 items on the synced folder. Now, the out of sync items acount to 5944 items for a total of 5974 items.

Not sure I explain well the problem, but syncing on the Synology NAS seems stuck.

Here’s a screenshot

Thanks for any help! Perhaps the easiest would be to reset somehow the folders on the Synology? If so, how one would do that? I don’t want to lose everything!

edit - I should add that when I modify a file that was present under the 0.13 version, te number of “Out of sync items” drop by one (5943 items, instead of 5944, etc…)

At a guess this seems related to the timestamp issue on android.

Syncing with “Cell”, is it an android device and does it have ignore permissions set?

That’s what I also though at first, but that folder isn’t shared with the two cells ;-). Both devices, with which that folder is shared, are “up to date”.

@Balinus Is the folder perhaps set as master on one or both of the other devices?

It just looks like it’s syncing. Check the logs.

Nope, but I set the folder on “Trash versioning” on device “Ouranos”, after upgrading to 0.14.3. Perhaps that’s the culprit.

I doubt it. The number of out of sync items remain stable (still 5943 items) after 2 full days with both device online.

The folder is not synced with Cell, only “Asus-Marie” and “Ouranos”.


It seems that the only thing I can do to transfer the file for “Out of sync” to “synced item” is to modify one of the 5943 file remaining.


Here’s the log I obtain. N.B. Device “Diskstation” is the Synology NAS.

[monitor] 09:12:37 INFO: Starting syncthing [FSIYL] 09:12:37 INFO: syncthing v0.14.3 "Dysprosium Dragonfly" (go1.6.3 linux-amd64) jenkins@build.syncthing.net 2016-07-28 11:15:14 UTC [FSIYL] 09:12:37 INFO: My ID: FSIYLBA-EXU3UVP-A3SIRDQ-DMAEASY-BVVM6KC-OZ5CC2D-F5D35VV-5MLIQAD [FSIYL] 09:12:37 INFO: Single thread hash performance is ~202 MB/s [FSIYL] 09:12:37 INFO: Ready to synchronize ymQQh-hdi6j (readwrite) [FSIYL] 09:12:37 INFO: Ready to synchronize gwXAP-a6j74 (readwrite) [FSIYL] 09:12:37 INFO: Using discovery server https://discovery-v4-1.syncthing.net/v2/?id=SR7AARM-TCBUZ5O-VFAXY4D-CECGSDE-3Q6IZ4G-XG7AH75-OBIXJQV-QJ6NLQA [FSIYL] 09:12:37 INFO: Using discovery server https://discovery-v4-2.syncthing.net/v2/?id=DVU36WY-H3LVZHW-E6LLFRE-YAFN5EL-HILWRYP-OC2M47J-Z4PE62Y-ADIBDQC [FSIYL] 09:12:37 INFO: Using discovery server https://discovery-v4-3.syncthing.net/v2/?id=VK6HNJ3-VVMM66S-HRVWSCR-IXEHL2H-U4AQ4MW-UCPQBWX-J2L2UBK-NVZRDQZ [FSIYL] 09:12:37 INFO: Using discovery server https://discovery-v6-1.syncthing.net/v2/?id=SR7AARM-TCBUZ5O-VFAXY4D-CECGSDE-3Q6IZ4G-XG7AH75-OBIXJQV-QJ6NLQA [FSIYL] 09:12:37 INFO: Completed initial scan (rw) of folder ymQQh-hdi6j [FSIYL] 09:12:37 INFO: TCP listener ([::]:22000) starting [FSIYL] 09:12:38 INFO: Completed initial scan (rw) of folder gwXAP-a6j74 [FSIYL] 09:12:39 INFO: Using discovery server https://discovery-v6-2.syncthing.net/v2/?id=DVU36WY-H3LVZHW-E6LLFRE-YAFN5EL-HILWRYP-OC2M47J-Z4PE62Y-ADIBDQC [FSIYL] 09:12:39 INFO: Using discovery server https://discovery-v6-3.syncthing.net/v2/?id=VK6HNJ3-VVMM66S-HRVWSCR-IXEHL2H-U4AQ4MW-UCPQBWX-J2L2UBK-NVZRDQZ [FSIYL] 09:12:39 INFO: Device FSIYLBA-EXU3UVP-A3SIRDQ-DMAEASY-BVVM6KC-OZ5CC2D-F5D35VV-5MLIQAD is "Linux-Roy" at [dynamic] [FSIYL] 09:12:39 INFO: Device QQJCNUS-52NIUOM-EYYHTXH-I6S3NTB-XNCLY37-5VRKEUQ-LBWMSLR-DU6L3QD is "Laptop-Marie" at [dynamic tcp://philipperoy.ddns.net:22000 tcp://172.98.67.90 tcp://172.98.67.90:22000] [FSIYL] 09:12:39 INFO: Device XIFCPQC-G5JWYMQ-7YF2VTW-IEXC6XL-CNSZUH3-IRZK42R-NDKT2ZE-JSTCAA6 is "DiskStation" at [dynamic tcp://philipperoy.ddns.net:22000 tcp://172.98.67.90 tcp://172.98.67.90:22000 tcp://philipperoy.ddns.net tcp://192.222.251.107:22000] [FSIYL] 09:12:39 INFO: Starting usage reporting [FSIYL] 09:12:39 INFO: GUI and API listening on 127.0.0.1:8384 [FSIYL] 09:12:39 INFO: Access the GUI via the following URL: http://127.0.0.1:8384/ [FSIYL] 09:12:48 INFO: Joined relay relay://64.137.241.167:22067 [FSIYL] 09:12:48 INFO: Detected 0 NAT devices [FSIYL] 09:13:12 INFO: Established secure connection to XIFCPQC-G5JWYMQ-7YF2VTW-IEXC6XL-CNSZUH3-IRZK42R-NDKT2ZE-JSTCAA6 at 192.168.0.237:50511-185.101.218.2:22067 (Relay (Client)) [FSIYL] 09:13:12 INFO: Device XIFCPQC-G5JWYMQ-7YF2VTW-IEXC6XL-CNSZUH3-IRZK42R-NDKT2ZE-JSTCAA6 client is "syncthing v0.14.3" named "DiskStation" [FSIYL] 09:13:12 INFO: Device XIFCPQC-G5JWYMQ-7YF2VTW-IEXC6XL-CNSZUH3-IRZK42R-NDKT2ZE-JSTCAA6 folder "gwXAP-a6j74" is delta index compatible (mlv=6552) [FSIYL] 09:13:19 INFO: Established secure connection to QQJCNUS-52NIUOM-EYYHTXH-I6S3NTB-XNCLY37-5VRKEUQ-LBWMSLR-DU6L3QD at 192.168.0.237:43715-69.164.210.237:22067 (Relay (Client)) [FSIYL] 09:13:19 INFO: Device QQJCNUS-52NIUOM-EYYHTXH-I6S3NTB-XNCLY37-5VRKEUQ-LBWMSLR-DU6L3QD client is "syncthing v0.14.3" named "DESKTOP-58U1DUA" [FSIYL] 09:13:21 INFO: Device QQJCNUS-52NIUOM-EYYHTXH-I6S3NTB-XNCLY37-5VRKEUQ-LBWMSLR-DU6L3QD folder "gwXAP-a6j74" is delta index compatible (mlv=6552)

Sounds like a delta index bug. Summoning @calmh

Yes, looks like a bug of some sort. That doesn’t look like the log from the device the screenshot is taken from though, which is what would be interesting.

Indeed, the log is from the office device “Ouranos” in the first screenshot. I’ll try to get a log tonight from the Synology NAS (which might be complicated). How should I launch syncthing in the NAS? STTRACE = something?

If there is something that looks non-normal in the logs, as in anything that looks like an error, you shouldn’t need to relaunch it at all.

If everything looks normal (apart from as in the screenshot), run it with STTRACE=model for a couple of minutes and save the complete log somewhere. You can post it privately if it contains lots of secret filenames and stuff.

Where would be the log file on a Synology NAS (ARM build) ? Can’t find it…

We log to stdout, same as on every platform.

Here’s the log from the Synology NAS.

edit - Initial scan of the faulty folder is still running. I’ll post the log once it’s done. Sorry.

edit2 - Scan of faulty folder is over (log below). Seems like starting syncing manually solved the problem! I’ll see if it stays like that when the Synology NAS reboot and start automatically syncthing.

`[monitor] 20:03:34 INFO: Starting syncthing [XIFCP] 20:03:34 INFO: syncthing v0.14.3 “Dysprosium Dragonfly” (go1.6.3 linux-arm) jenkins@build.syncthing.net 2016-07-28 11:15:14 UTC [XIFCP] 20:03:34 INFO: My ID: XIFCPQC-G5JWYMQ-7YF2VTW-IEXC6XL-CNSZUH3-IRZK42R-NDKT2ZE-JSTCAA6 [XIFCP] 20:03:34 INFO: Single thread hash performance is ~6.9 MB/s [XIFCP] 20:03:37 INFO: Ready to synchronize Camera-phil (readwrite) [XIFCP] 20:03:38 INFO: Ready to synchronize htc_one_m8-photos (readwrite) [XIFCP] 20:03:38 INFO: Ready to synchronize MusiqueCellMarie (readwrite) [XIFCP] 20:03:41 INFO: Ready to synchronize xerje-t3sez (readonly) [XIFCP] 20:03:51 INFO: Ready to synchronize gwXAP-a6j74 (readwrite) [XIFCP] 20:03:52 INFO: Using discovery server https://discovery-v4-1.syncthing.net/v2/?id=SR7AARM-TCBUZ5O-VFAXY4D-CECGSDE-3Q6IZ4G-XG7AH75-OBIXJQV-QJ6NLQA [XIFCP] 20:03:52 INFO: Using discovery server https://discovery-v4-2.syncthing.net/v2/?id=DVU36WY-H3LVZHW-E6LLFRE-YAFN5EL-HILWRYP-OC2M47J-Z4PE62Y-ADIBDQC [XIFCP] 20:03:52 INFO: Using discovery server https://discovery-v4-3.syncthing.net/v2/?id=VK6HNJ3-VVMM66S-HRVWSCR-IXEHL2H-U4AQ4MW-UCPQBWX-J2L2UBK-NVZRDQZ [XIFCP] 20:03:52 INFO: Using discovery server https://discovery-v6-1.syncthing.net/v2/?id=SR7AARM-TCBUZ5O-VFAXY4D-CECGSDE-3Q6IZ4G-XG7AH75-OBIXJQV-QJ6NLQA [XIFCP] 20:03:52 INFO: Using discovery server https://discovery-v6-2.syncthing.net/v2/?id=DVU36WY-H3LVZHW-E6LLFRE-YAFN5EL-HILWRYP-OC2M47J-Z4PE62Y-ADIBDQC [XIFCP] 20:03:52 INFO: Using discovery server https://discovery-v6-3.syncthing.net/v2/?id=VK6HNJ3-VVMM66S-HRVWSCR-IXEHL2H-U4AQ4MW-UCPQBWX-J2L2UBK-NVZRDQZ [XIFCP] 20:03:52 INFO: TCP listener ([::]:22000) starting [XIFCP] 20:03:55 INFO: Completed initial scan (rw) of folder htc_one_m8-photos [XIFCP] 20:03:56 INFO: Completed initial scan (rw) of folder Camera-phil [XIFCP] 20:03:57 INFO: Device XIFCPQC-G5JWYMQ-7YF2VTW-IEXC6XL-CNSZUH3-IRZK42R-NDKT2ZE-JSTCAA6 is “DiskStation” at [dynamic] [XIFCP] 20:03:57 INFO: Device 3KTNVSO-XSGW5WI-XPSWJF5-ZRQMJYB-S5GNTEX-YOAHYHD-MZYNTWX-ABZNJAF is “Cell-Marie” at [dynamic] [XIFCP] 20:03:57 INFO: Device EUN26SZ-JBK5QKG-CWDO6EH-AI2INEC-6IHWVRS-NQJ2OPT-NCHMZCK-V75VPQB is “Cell-Phil” at [dynamic] [XIFCP] 20:03:57 INFO: Device FSIYLBA-EXU3UVP-A3SIRDQ-DMAEASY-BVVM6KC-OZ5CC2D-F5D35VV-5MLIQAD is “Ouranos” at [dynamic tcp://philipperoy.ddns.net:22000] [XIFCP] 20:03:57 INFO: Device QQJCNUS-52NIUOM-EYYHTXH-I6S3NTB-XNCLY37-5VRKEUQ-LBWMSLR-DU6L3QD is “Asus-Marie” at [dynamic] [XIFCP] 20:03:57 INFO: Starting usage reporting [XIFCP] 20:03:57 INFO: GUI and API listening on [::]:7070 [XIFCP] 20:03:57 INFO: Access the GUI via the following URL: https://127.0.0.1:7070/ [XIFCP] 20:03:58 INFO: Completed initial scan (rw) of folder MusiqueCellMarie [XIFCP] 20:04:14 INFO: Established secure connection to FSIYLBA-EXU3UVP-A3SIRDQ-DMAEASY-BVVM6KC-OZ5CC2D-F5D35VV-5MLIQAD at 192.168.1.130:34172-45.62.253.132:22067 (Relay (Client)) [XIFCP] 20:04:14 INFO: Device FSIYLBA-EXU3UVP-A3SIRDQ-DMAEASY-BVVM6KC-OZ5CC2D-F5D35VV-5MLIQAD client is “syncthing v0.14.3” named “Linux-Roy” [XIFCP] 20:04:14 INFO: Device FSIYLBA-EXU3UVP-A3SIRDQ-DMAEASY-BVVM6KC-OZ5CC2D-F5D35VV-5MLIQAD folder “gwXAP-a6j74” is delta index compatible (mlv=6147) [XIFCP] 20:04:16 INFO: Detected 1 NAT device [XIFCP] 20:04:24 INFO: Joined relay relay://45.62.224.243:22067 [XIFCP] 20:11:35 INFO: Completed initial scan (ro) of folder xerje-t3sez [XIFCP] 20:29:07 INFO: Failed to exchange Hello messages with QQJCNUS-52NIUOM-EYYHTXH-I6S3NTB-XNCLY37-5VRKEUQ-LBWMSLR-DU6L3QD ([fe80::2c69:38fb:ee50:ff8%eth0]:65080): EOF [XIFCP] 20:29:10 INFO: TLS handshake (BEP/tcp): EOF [XIFCP] 20:29:16 INFO: Established secure connection to QQJCNUS-52NIUOM-EYYHTXH-I6S3NTB-XNCLY37-5VRKEUQ-LBWMSLR-DU6L3QD at 192.168.1.130:46017-45.62.224.243:22067 (Relay (Server)) [XIFCP] 20:29:16 INFO: Device QQJCNUS-52NIUOM-EYYHTXH-I6S3NTB-XNCLY37-5VRKEUQ-LBWMSLR-DU6L3QD client is “syncthing v0.14.3” named “DESKTOP-58U1DUA” [XIFCP] 20:29:19 INFO: Device QQJCNUS-52NIUOM-EYYHTXH-I6S3NTB-XNCLY37-5VRKEUQ-LBWMSLR-DU6L3QD folder “gwXAP-a6j74” is delta index compatible (mlv=6089) [XIFCP] 20:29:41 INFO: Failed to exchange Hello messages with QQJCNUS-52NIUOM-EYYHTXH-I6S3NTB-XNCLY37-5VRKEUQ-LBWMSLR-DU6L3QD ([fe80::2c69:38fb:ee50:ff8%eth0]:65160): EOF [XIFCP] 20:29:55 INFO: Failed to exchange Hello messages with QQJCNUS-52NIUOM-EYYHTXH-I6S3NTB-XNCLY37-5VRKEUQ-LBWMSLR-DU6L3QD (192.168.1.146:65175): EOF [XIFCP] 20:30:00 INFO: Connection to QQJCNUS-52NIUOM-EYYHTXH-I6S3NTB-XNCLY37-5VRKEUQ-LBWMSLR-DU6L3QD closed: switching connections [XIFCP] 20:30:00 INFO: Connection to QQJCNUS-52NIUOM-EYYHTXH-I6S3NTB-XNCLY37-5VRKEUQ-LBWMSLR-DU6L3QD closed: reading length: EOF [XIFCP] 20:30:00 INFO: Connection to QQJCNUS-52NIUOM-EYYHTXH-I6S3NTB-XNCLY37-5VRKEUQ-LBWMSLR-DU6L3QD closed: switching connections [XIFCP] 20:30:00 INFO: Established secure connection to QQJCNUS-52NIUOM-EYYHTXH-I6S3NTB-XNCLY37-5VRKEUQ-LBWMSLR-DU6L3QD at 192.168.1.130:40849-192.168.1.146:22000 (TCP (Client)) [XIFCP] 20:30:00 INFO: Device QQJCNUS-52NIUOM-EYYHTXH-I6S3NTB-XNCLY37-5VRKEUQ-LBWMSLR-DU6L3QD client is “syncthing v0.14.3” named “DESKTOP-58U1DUA” [XIFCP] 20:30:47 INFO: Device QQJCNUS-52NIUOM-EYYHTXH-I6S3NTB-XNCLY37-5VRKEUQ-LBWMSLR-DU6L3QD folder “gwXAP-a6j74” is delta index compatible (mlv=6089) [XIFCP] 20:30:48 INFO: Connection to QQJCNUS-52NIUOM-EYYHTXH-I6S3NTB-XNCLY37-5VRKEUQ-LBWMSLR-DU6L3QD closed: reading length: read tcp 192.168.1.130:40849->192.168.1.146:22000: use of closed network connection [XIFCP] 20:31:11 INFO: TLS handshake (BEP/tcp): EOF [XIFCP] 20:31:46 INFO: TLS handshake (BEP/tcp): read tcp 192.168.1.130:22000->192.168.1.146:65200: i/o timeout [XIFCP] 20:31:48 INFO: Joining relay session (BEP/relay): read tcp 192.168.1.130:51721->45.62.224.243:22067: i/o timeout [XIFCP] 20:32:24 INFO: TLS handshake (BEP/tcp): EOF [XIFCP] 20:32:41 INFO: Failed to exchange Hello messages with QQJCNUS-52NIUOM-EYYHTXH-I6S3NTB-XNCLY37-5VRKEUQ-LBWMSLR-DU6L3QD (192.168.1.146:65238): EOF [XIFCP] 20:33:18 INFO: Established secure connection to QQJCNUS-52NIUOM-EYYHTXH-I6S3NTB-XNCLY37-5VRKEUQ-LBWMSLR-DU6L3QD at [fe80::211:32ff:fe0a:b994%eth0]:47618-[fe80::2c69:38fb:ee50:ff8%eth0]:22000 (TCP (Client)) [XIFCP] 20:33:18 INFO: Device QQJCNUS-52NIUOM-EYYHTXH-I6S3NTB-XNCLY37-5VRKEUQ-LBWMSLR-DU6L3QD client is “syncthing v0.14.3” named “DESKTOP-58U1DUA” [XIFCP] 20:33:18 INFO: Device QQJCNUS-52NIUOM-EYYHTXH-I6S3NTB-XNCLY37-5VRKEUQ-LBWMSLR-DU6L3QD folder “gwXAP-a6j74” is delta index compatible (mlv=6089) [XIFCP] 20:49:52 INFO: Completed initial scan (rw) of folder gwXAP-a6j74

`

When I launched syncthing manually, I used “sudo”. Perhaps syncthing, when launched automatically didn’t had the right privilege to rehash(?) for version 0.14.x ?

It rehashes no matter what. It looks like you had some sort of permissions problem.

Yes, probably. I’m at the office now and everything is back to normal.

Thanks for your help! Keep up the good work, nice software!

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