MartijnHinderdael

I managed to catch the moment when the transfers stop..at least I hope so: On the receiver: I also noted that just browsing through some settings menus (the main preferences menu, not the per-peer one) triggered a restart of the transfer process. I have no clue what is happening here....any thoughts on this?

I have disabled "use UPNP Port mapping" on both the sender (mediahub) and the receiver (the AMD machine) just to see what that would change. First, files started transferring again; This is the log during those few minutes: You can see the transfer start after some time. Then, transferring files stopped again, this is what the debug log on the receiver looks like then: This is what the log file looks like when re-commencing the transfer by enabling the "use tracker server" checkbox: Transferring stopped after a minute or so.

I have updated, hoping that the info in the log is indeed accurate. Thank you!

I have two linux machines running btsync 2.0.93 (the debian packages by Yeasoft) and they refuse to sync. One is a Ubuntu machine on an AMD X64 processor The other one is a debian machine on an ARM processor (a linksys Mediahub on which I managed to install Debian linux instead of the linksys OS). The problem is: They don't sync. If I change a setting (any of the settings I can change per sync connection) one or two files are synced, then the process stops again. Unchecking a box that was previously checked, and it runs again. When it stops, I uncheck the box and it runs again. Both machines connected by wired network to the same gbit LAN. Debug log from the AMD machine: The 192.168.1.31 IP is the linksys mediahub No debug log from the mediahub: I get the following message when clicking the log link: So...I don't know what to make of it. Any thoughts on this? Apologies for two posts quickly after eachother in one topic: I found that the Mediahub was not producing a log file simply because debug logging was turned off...... To make things more clear: The logs from both machines during the 21:30 time interval. AMD Machine: Mediahub during the same time frame: To clarify further: The Mediahub is holding a few 100GB of files which are shared "read only" to the AMD machine. Files should only be transfered from the mediahub to the AMD machine.

I have noticed that the 2.0 sync program now has an update available . Before I upgrade: are there any "downgrades" or functionality reductions compared to the 2.0 version? I have been very disappointed when upgrading from 1.4 to 2.0 with the 10-folder limit and do not like to be surprised with such an experience again.

Any thoughts from BTSync on this subject here? My settings (input using debconf, I am using the Debian packages by Tuxpoldo): -Do you want to define a default BitTorrent Sync instance: yes -BTSync is running as user "btsync" -Nice value of the daemon: 19 (I have used other values up to -20 with zero impact) -Web interface bind to IP address: 0.0.0.0 -Web interface listen port: 8888 -Should BTSync allow only SSL connections to the Web UI? No. -Start path for the web interface folder browser: <no input> -Bittorrent Sync API Key: <no input> -Do you want to configure folder defaults: yes -Should old version of file be preserved by default?: yes -Should Bittorrent Sync use DHT by default: yes (setting this to no had no impact) -Should Bittorrent Sync use LAN Broadcasts by defautl: yes (I have not experimented with this value) -Should Bittorent Sync use external relay servers when needed: yes (I think require this as I do some syncing with machines outside my LAN -Should Bittorrent Sync use external tracker servers by default? yes (I think require this as I do some syncing with machines outside my LAN -Default known hosts list for new shared folders: <no input> -Do you want to configure advanced parameters: yes -Umask value to set for the daemon: <no input> -External port number reported to the tracker: 0 -Should BitTorrent Sync perform disk operations with low priority?: Yes (setting this to no makes no difference) -Should Bittorrent Sync encrypt data on the local network: no -Should Bittorrent Sync apply speed limits also in local networks: no -Fall back folder rescan interval in seconds: 86400 (once very day instead of every 10 mins) -Maximum file size difference for patching: <no input> -Maximum file size for versioning: <no input> -Send buffer size: 5MB (20 or 10MB makes no difference) -Receive buffer size: 5MB (20 or 10MB makes no difference) -Maximum time difference between divices: <no input> -Maximum time to live for versioned copies: <no input> -Debug logfile size in MB: 10 -Peer expiration days: 14

The permissions trick works Disadvantage is that I basically had to grant write rights to everyone in the etc folder, or choose to make btsync part of the group "root" I figured that the last option was the riskiest, so I chose to give everyone permissions to write in /etc but not in it's contents.

Can I get around this by allowing BTSync write access to the shared folder but not to it's contents?

I have a 1GBit wired lan in my home (CAT5E cabling), running a variety of linux machines (1-3) and a windows laptop: -Machine 1: A Dual Core AMD 64Bit something MHz with 4GB of RAM -Machine 2: A Via Epia 1GHz with Intel GBit NIC -Machine 3: A Linksys NMH300 Mediahub (ARM V5/400MHz/64MB Ram) running Debian Linux -Machine 4: My Lenovo Laptop/4GB RAM/SSD running windows 8.x with a GBit NIC. When speed testing the raw data transfer rates I get to the following values between the three: With NC: Machine 1-2: ~600MBit Machine 1-3: ~350MBit Over SMB/Cifs with stock settings from machine 4: Machine 1: ~50MB/s reading and writing I guess Machine 2: Reading ~30MB/s, writing ~20MB/s Machine 3: Reading ~16MB/s, writing ~12MB/s Large files transfer over the network without any problems. Over BTSync: Machine 1-2: 2MB/s Machine 1-3: 2MB/s Machine 1-4: ~5MB/s (over WiFi, this is a reasonable value for my house). All BTSync traffic in my LAN is non-encrypted, read and write buffers set to 10MB, other settings are stock settings. Machines 2 and 3 require full CPU Load to get to about 2 MB/s. The transfer rates mentioned are the ones read from the bottom of the web interface, not the ones displayed next to the transfers. This transfer is the only one running while performing the test. The speed mentioned at the bottom of the web interface matches roughly with the throughput of my NIC's measured by IPTRAF. The speed displayed next to the transfers is far off this value, usually 2-10 times the thoughput IPTRAF measures on my NIC. Now I have the following problems: -The value of the throughput (both read and write) displayed by the BTSync web interface next to the transfers is very wrong, both on 3 linux machines, as well as on a windows 8.1 and a windows Vista machine. -Both of my more energy efficient linux machines are basically limited at about 2MB/s. They seem to be almost equally fast. Sometimes rates up to 2.2MB, sometimes only 1.5MB. Now I know these two aren't speed monsters, but 2MB/s seems a bit slow even for these boys. I'm also surprised by seeing two machines who have a factor 2 between them when it comes to SMB speed are equally slow when using BTSync. What could be the problem here? The BTSync build used is 1.4.103 BETA on all machines by the way.

I am setting up btsync on several machines in my house. BTSync will sync folders that need to be backed up to my NAS. The NAS will then make a backup to a different machine from time to time. One of the things I'd like to back up is the "/etc" directories on some linux machines and the "users" directory on windows machines. BTSync refuses to do this, as the BTSYNC user has no write permissions in that directory. The thing is, I don't want BTSync to write in those directories at all. I want BTSync to just read them and serve them to another machine. Is there a way to do this without permitting btsync to write in those directories?