Folder "Documents_reseau" isn't making progress - check logs for possible root cause. Pausing puller for 1m0s.

Hi,

Sorry for my English.

I have Syncthing running on Debian-7 and Microsoft server 2012R2 and all time, i have this message: Folder “Documents_reseau” isn’t making progress - check logs for possible root cause. Pausing puller for 1m0s.

The folders is synchronize at 8 PM with “rsync”.

I search the logs but i just get it in /home/syncthing/.conf/syncthing/index/LOG I have:

15:42:36.754855 journal@remove removed @14901 15:42:36.765893 table@compaction L0·1 -> L1·22 S·47MiB Q·19343767 15:42:36.999973 table@build created L1@14937 N·11127 S·2MiB “\x00Do…lnk,v19221699”:"\x00Do…pdf,v19243949" 15:42:37.257415 table@build created L1@14938 N·12022 S·1MiB “\x00Do…pdf,v19243951”:"\x00Do…xls,v19343640" 15:42:37.478828 table@build created L1@14939 N·2 S·3MiB “\x00Do…tib,v19343080”:"\x00Do…tib,v19343082" 15:42:37.532149 table@build created L1@14940 N·188 S·104KiB “\x00Do…tib,v19343084”:"\x00Do…xls,v19343772" 15:42:37.991501 table@build created L1@14941 N·49172 S·2MiB “\x01Do…ory,v19195712”:"\x01Do…doc,v19294051" 15:42:38.277007 table@build created L1@14942 N·24719 S·1015KiB “\x01Do…pdf,v19294053”:"\x02Do…xls,d19343688" 15:42:38.625882 table@build created L1@14943 N·50917 S·2MiB “\x02Do…xls,v19343690”:"\x02Do…tib,v17774660" 15:42:39.014641 table@build created L1@14944 N·55429 S·2MiB “\x02Do…tib,v18297939”:"\x02Do…tib,v17926187" 15:42:39.492534 table@build created L1@14945 N·55564 S·2MiB “\x02Do…tib,v18484951”:"\x02Do…tib,v18116152" 15:42:39.970534 table@build created L1@14946 N·55291 S·2MiB “\x02Do…tib,v18674916”:"\x02Do…pst,v17712943" 15:42:40.552748 table@build created L1@14947 N·55157 S·2MiB “\x02Do…pst,v18258217”:"\x02Do…tib,v18008322" 15:42:40.983163 table@build created L1@14948 N·52539 S·2MiB “\x02Do…tib,v18567086”:"\x02Do…tib,v18084446" 15:42:41.297160 table@build created L1@14949 N·48409 S·2MiB “\x02Do…tib,v18643210”:"\x02Do…JPG,v17611595" 15:42:41.724576 table@build created L1@14950 N·47464 S·2MiB “\x02Do…tib,v18070573”:"\x02Do…tib,v17850932" 15:42:42.029466 table@build created L1@14951 N·43928 S·2MiB “\x02Do…tib,v18409696”:"\x02Do…tib,v18073784" 15:42:42.354402 table@build created L1@14952 N·44029 S·2MiB “\x02Do…tib,v18632548”:"\x02Do…xls,v17514082" 15:42:42.666423 table@build created L1@14953 N·43858 S·2MiB “\x02Do…tib,v17828002”:"\x02Do…pdf,v17478443" 15:42:42.970404 table@build created L1@14954 N·42784 S·2MiB “\x02Do…tib,v17978171”:"\x02Do…tib,v18306058" 15:42:43.268517 table@build created L1@14955 N·43550 S·2MiB “\x02Do…tib,v17935732”:"\x02Do…tib,v18483646" 15:42:43.581583 table@build created L1@14956 N·45675 S·2MiB “\x02Do…Zip,v17275335”:"\x02Do…tib,v17998216" 15:42:43.951513 table@build created L1@14957 N·45650 S·2MiB “\x02Do…tib,v18556980”:"\x02Do…tib,v18347317" 15:42:44.287676 table@build created L1@14958 N·45696 S·2MiB “\x02Do…pdf,v16958356”:"\x02Do…tib,v18642715" 15:42:44.614151 table@build created L1@14959 N·45636 S·2MiB “\x02Do…tib,v17767729”:"\x02Do…pdf,v17658877" 15:42:44.975275 table@build created L1@14960 N·42786 S·1MiB “\x02Do…pdf,v16593691”:"\x04Do…ame,v19343767" 15:42:45.033355 table@compaction committed F+1 S-561KiB Ke·0 D·34056 T·8.267360197s 15:42:45.171284 table@compaction L1·1 -> L2·5 S·12MiB Q·19343767 15:42:45.409187 table@build created L2@14961 N·11305 S·2MiB “\x00Do…xls,v17172446”:"\x00Do…xls,v19245817" 15:42:45.717153 table@build created L2@14962 N·13745 S·2MiB “\x00Do…xls,v19245819”:"\x00Do…xls,v19273308" 15:42:45.957929 table@build created L2@14963 N·13559 S·2MiB “\x00Do…xls,v19273310”:"\x00Do…JPG,v19300410" 15:42:46.144505 table@build created L2@14964 N·4382 S·2MiB “\x00Do…db,v19300412”:"\x00Do…EXE,v19309174" 15:42:46.521077 table@build created L2@14965 N·16634 S·2MiB “\x00Do…EXE,v19309176”:"\x00Do…doc,v19342440" 15:42:46.546301 table@build created L2@14966 N·71 S·7KiB “\x00Do…pmi,v19342442”:"\x00Do…xls,v19342582" 15:42:46.610388 table@compaction committed F~ S-1MiB Ke·0 D·12010 T·1.43899537s 15:42:46.610524 table@compaction expanding L1+L2 (F·1 S·104KiB)+(F·2 S·4MiB) -> (F·2 S·3MiB)+(F·2 S·4MiB) 15:42:46.610554 table@compaction L1·2 -> L2·2 S·7MiB Q·19343787 15:42:46.778846 table@build created L2@14967 N·2 S·2MiB “\x00Do…tib,v19343078”:"\x00Do…tib,v19343080" 15:42:46.911098 table@build created L2@14968 N·1056 S·2MiB “\x00Do…tib,v19343082”:"\x00Do…doc,v16205586" 15:42:47.131909 table@build created L2@14969 N·13425 S·2MiB “\x00Do…doc,v16205588”:"\x00Do…doc,v16456750" 15:42:47.288343 table@build created L2@14970 N·5937 S·1MiB “\x00Do…doc,v16456754”:"\x00Do…xls,v16913898" 15:42:47.343233 table@compaction committed F~ S-1KiB Ke·0 D·9 T·732.609709ms 15:42:50.154938 table@remove removed @14936 15:42:50.155713 table@remove removed @14810 15:42:50.156462 table@remove removed @14844 15:42:50.157161 table@remove removed @14920 15:42:50.157639 table@remove removed @14921 15:42:50.158301 table@remove removed @14893 15:42:50.158990 table@remove removed @14896 15:42:50.159659 table@remove removed @14898 15:42:50.160337 table@remove removed @14900 15:42:50.161087 table@remove removed @14903

I don’t understand why they don’t sync.

This log is the database log, which is not very useful. Syncthing logs to stdout, check stdout for clues.

Ok i get it:

[URJT7] 17:21:04 INFO: Puller (folder “Documents_reseau”, file “XXXXXX.xlsx”): shortcut: chtimes /volume1/documents reseau/XXXXXXXX.xlsx: operation not permitted [URJT7] 17:21:04 INFO: Puller (folder “Documents_reseau”, file “YYYYYYYY.xls”): shortcut: chtimes /volume1/documents reseau/YYYYYYYYYYY.xls: operation not permitted

the date in my debian is: lundi 23 mars 2015, 17:11:46 (UTC+0100)

and in my Windows is: lun. 23 mars 2015 17:09:28

I have 2mins of different. It is a problem?

I assume this error is on Debian side, rather than Windows side?

It seems that your volume is mounted without the ability to modify mtimes, which is the core issue. Perhaps its mounted as read only? You can also try using touch somefile; touch -m -t 201503220000 somefile inside the folders location to see if you can manually modify the timestamps.

Ok i’m sorry

I explain. The first configuration was:

Windows server: folder “Docs” = 77103 files (89GiB) and folder Master

Debian server: folder “Docs” = 148755 files (170GiB) and folder not Master

And it’s normal that syncthing don’t want synchronize because, it look more files in slave folder.

The new configuration is:

Windows server: folder “Docs” = 77103 files and folder Master

Debian server: folder “Docs” = 0 file and folder not Master

And now the synchro is up. I will see tomorrow if it worked.

I’m so sorry for my ignorence.