Search the Community
Showing results for tags 'assertion failed'.
BTSync 1.3.105 crashes on startup on Linux x86_64 (Debian stable server). Crash happens when BTSync detects that a file update has been detected in an encrypted RO share. Currently this happens within a second of starting btsync. Here is the terminal output using --nodaemon: SyncFilesController: started periodic scanSyncFilesController [file updated]: Processing file <PATH_TO_HASHED_FILE> 1401206360 603SyncFilesController: Detected updated file "<HASHED_FILE>" (R/O). Checking filehashassert failed ./SyncFilesControllerRO.cpp:365 (16973929)SyncFolderNotify: ".SyncID", event = "IN_CLOSE_WRITE"[OnNotifyFileChange] <PATH_TO_SHARE>/.SyncID, source = NULLAbortedHere is the debug log output: [20140530 14:23:12.809] SyncFilesController: Detected updated file "<HASHED_FILE>" (R/O). Checking filehash[20140530 14:23:12.810] SyncFolderNotify: ".SyncID", event = "IN_CLOSE_WRITE"[20140530 14:23:12.810] [OnNotifyFileChange] <PATH_TO_FOLDER>/.SyncID, source = NULLI have replaced sensitive information above with <EXPLANATION_TEXT>. To isolate the problem, the only other machine that has access to the secret (encrypted RW), which means it has BTSync running, is also a Linux x86_64 machine. BTSync is the same version. BTSync does not crash on this machine which has the encrypted RW version of the same secret. I have tried to delete everything in .sync folder as well as all .SyncID files. Everything is setup via config file, webgui is disabled. This setup has worked for months using previous versions of BTSync. The crash began after updating to 1.3.105, but now going back to previous version does not help. Although I have not tested by deleting all .SyncID files and .sync folder contents prior to going back to an older version.