Search the Community
Showing results for tags '1.3.105'.
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 = "I
I'm using BitTorrent Sync on Linaro Ubuntu running on a Cubietruck (ARM) for quite some time now. I noticed that BTSync uses considerably more CPU lately than it used to. Months ago, it was like 3%@idle. Right now, it's more like 13-20%@idle. Note: idle=devices are connected, but sync is finished BTSync monitors about 9000 files (there used to be more files, like 15000) spread over 11 folders. I'm using the packages "btsync_1.3.1-1_all.deb" and "btsync-common_1.3.105-1_armhf.deb" installed from either ""http://ppa.launchpad.net/tuxpoldo/btsync/ubuntu" (which one is newer for apt). The log
Hello, After updating to version 1.3.105 I get this error message in the logs. Failed to parse folder config. Error: lexical error: invalid char in json text. <!DOCTYPE html PUBLIC "-//W3C/ (right here) ------^Thx