RomanZ

@AetherMichael We already got such requests in the past. Sync checks the integrity of the file when it receives it from other peer (and keeps hash in DB). Although, this won't help you against rotten bits: Sync cannot distinguish if file has changed on local HDD due to drive malfunction - or some software managed to change it without sending notification.

@drego85 1.4 and 2.0 folders have different security base, so it's better for users to convert them explicitly. Some of users may not want to migrate from keys to certificates.

@hiphop03199 I've sent you experimental build. Let me know if it helps.

@nzth, @kewi It might be the same issue, but if @kewi sends logs as well - there are more chances we find the root cause.

@nzth Thanks for the logs, we'll take a look at it! @zeropluszero Sure, we'll be happy to catch this issue in logs.

@pooiyx No, you can't do it. If A has "Read-Write" key and "B" has "Read-Only" key, B will always get the data if there is a connection. The only way to prevent B from syncing changes from A is to removing folder from Sync or - ensuring that B never connects.

@zeropluszero How random is this? Reproduces once a day, week, month? I'd prefer to get debug logs to see the root cause, but if the time from moment it reproduces to moment when you notice that is way too big, it would be hard to capture it in logs.

@zeropluszero Are there any Android devices in your mesh? If yes - does the issue reproduce when they are offline \ sync is off? @rockhill04 This build should not introduce / trigger any OOS issues, I presume it is coincidence. Can I get your debug logs for analysis? @hurik Let me know if it sleeps well. This is an old issue and I want it to get resolved. Our Syno in lab slept well several hours - until other peers awoke it.

@alx49 I've sent you an experimental build to your e-mail box. Let me know your testing results.

@oniamigt Could you please shut down Sync on your Note and check if issue pops up when it is not online? Thanks!

@cadillacace No, it does not support environment variables. The best storage_path can do is a relative path - so yes, putting it to ".\\" (you have to escape backslash in JSON) is going to work - if Sync is allowed to write data there. usually, apps that reside in Program Files are not allowed to write data there, so if you want to keep storage data next to binary - think of locating it outside of Program Files.

@pooiyx As I understand your Computer B needs only to get files and changes from A and never send anything back - even if something extra appears in backup folder. Sync has very similar sync mode. You need to add "Temporary Depository" as read&write folder, then share read-only key to computer B to the same folder. In this case B will receive all the files from A, but will never send them back if they change.

@louis925 Is this in context of iOS operating system? Why do you need to display locked files there - every app is in the sandbox? Also, I suggest debugging the issue when folder not syncs rather than re-adding it. Send us a feedback when it happens and we'll try to help you.

@heehee62, @GreatMarko Sync 1.4 can backup data from ExtSD card on Android 4.4 and newer. It won't try to create any service folders. You should be able to create custom backup pointing to your pics location on Android. Let me know if it is not working by some reason.

@kewi I tried to reproduce it in my lab without success. I wonder if you can provide some debugging information? I'll need debug log from the peer that gets file downloaded to sync folder by firefox and any another peer online. Also, I'll need ProcessMonitor log collected at the same time from machine with Firefox. Thanks!

@Nodefield Patience, my friend. Now it is there

Here is the topic with all details, download links, etc.

Dear community, Sync 1.4.110 is now available on download site. Here is direct link. It is available via auto-update since 2015 Feb 18! Change log - Fixed issue with Sync hanging due to invalid filename characters - Fixed issue with Sync preventing HDD from sleeping on NAS* - Fixed some incorrect localization text - Fixed issue with confusing old and new filenames in history when renaming - Added new advanced parameter for Linux - config_save_interval - Minor fixes and changes - Remove asterisks in return values of “get_prefs” API call - Fixed sporadic Out-Of-Sync issues** * To allow NAS sleeping when Sync is running set folder_rescan_interval, config_refresh_interval and config_save_interval to some significant value, for example - 3600 (seconds). Also fully disable logging by creating "debug.txt" file in storage folder containing "0000" (four zero symbols). ** The "Out-of-Sync" issue has a number of root causes and we know that not all of them are addressed at the moment. Link to the topic dedicated to fixing the issue is below. Full change log history can be found here. Important Notes on Sync 1.4 Downgrade to 1.3 is not possible after installing Sync 1.4. (If you wish to downgrade - please uninstall Sync removing all settings, then install 1.3 and configure all folders from scratch) Important Notes for Sync 1.3 Users Windows XP and Server 2003 clients using Sync 1.3.x will not receive auto-updates to 1.4, but can still update to 1.4 manually. Known issues - UI is tiny on high resolution displays [Workaround] - Sync may continually re-index SMB shares [Discussion] - Checkboxes once selected may move out of alignment on OSX Yosemite [Discussion] - Certain models of Android mobile devices cause deleted files to return with 0-size - Sometimes Sync gets stuck with out-of-sync state [Discussion]

Now fixed.

Dear community, Unfortunately there are some issues with our download server and Sync cannot be downloaded from official download page. Please feel free to use the direct download link below while we fix the problem. Build 1.4.106 direct download We apologize for inconvenience.

@vixster Its rather simple - just click the Sync icon in system tray, choose "Send feedback" and make sure "Send debug info" checkbox is checked. Put your e-mail and a link to this topic so I can understand that logs are coming from you. Do the same on all peers.

@all, Thanks for testing and supplying us your debug logs. The issue is not fixed completely - and we are working hard to provide new and more ubiquitous fix. If anyone still has OOS - send me your logs. Note, that logs need to be collected in debug level and from at least 2 computers and "Out of Sync" message should appear and stay before you collect logs (i.e. the reason which causes OOS is recorded in logs).

@all, Thanks to @finar we've managed to find another issue causing "Out of Sync". Here is another experimental build which contains one more fix comparing to 1.4.10019 and now fixes 2 issues causing "Out of Sync". Build 1.4.10022 [Links removed - build obsolete] Installation instructions (same) You don't need to upgrade. Just shut down Sync, replace the executable file and start Sync again. Installation required for all peers in your mesh. As before, I appreciate your feedback and debug logs even if build fixes OOS issue for you.

@benstrousers We don't have glibc2.3 experimental build - sorry. @aq32 I need logs to understand what's happening there. From both desktop and android. @chubirka The experimental build fixes one (and seems to be the most widespread) issue that causes "Out Of Sync" symptom. Unfortunately this is not the only root cause and you might encounter a different one. If you are willing to help us - I need some debugging infromation (logs from experimental build - or dump from 2.0 crash).

@uffowich See the section #3 here.