Search the Community

Showing results for tags 'debian'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Resilio Sync
    • Sync General Discussion
    • Sync Troubleshooting
    • Sync for NAS (Network Attached Storage)
    • Sync Stories
    • Developers
    • Feature Requests

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 31 results

  1. Hi all, I'm running resilio on a headless Debian system which act as a seed for another machine. The sync worked fine for a period, but now it fails to sync some files. Looking at the logs I see errors like the following: TF[AB6C] [0x00007fe01df91310][<PATH_TO_FILE>]: state:SEED error: meta:1 conns:1 io:0 Moreover, new files added to the same folder are not synced. I checked with lsof and only resilio is accessing such files. If it my be relevant, the folder is on a encrypted raid5 ext4 volume. Thanks
  2. hi I need to rebuild a machine and would like to retain the sync ID of the original machine. Can I copy from old, then rebuild new and paste back in? If so, what files would I need to retain and replant in new? Cheers, Geoff.
  3. I've created a rslsync encrypted folder on my NAS (QNAP TS119, Marvell Kirkwood SOC) and added the encrypted key to a rslsync folder on a vserver. This setup won't sync apparently due to failing hash checks at the vserver. Syncing to another target (Notebook, Arch Linux, Linux 4.8.11, x86_64, rslsync 2.4.2, r/w key) works in all directions (NAS <-> Laptop, vserver <-> Laptop). I think I've quoted the relevant logfile entries, if not the full logfiles are attached. Many thanks for your support! Setup V-Server: platform: Linux 3.16.0-4-amd64 #1 SMP Debian 3.16.36-1+deb8u2 (2016-10-19) x86_64 version: 2.4.2.708 Nas: platform: Linux 3.16.0-4-kirkwood #1 Debian 3.16.36-1+deb8u2 (2016-10-19) armv5tel version: 2.4.2.708 Logfiles vserver: [20161206 12:20:11.310] TF[B140] [0x00007f2fec00bbe0][/home/rslsync/shares/sync/UPBWW6NDNON4BVATGDQ53XO3QLABMZKYQM3CBHU4FS762DNIFFZ45FIIV62EEXCXA5L563TAI4ZJ4OCHOJ3J3VOXKGRUYYLZXUPB3VA5T5EXSI4RFNFRDW5BFALKZG3GWY6KRAM7WY66XDSPXSTSXTIANQXXGQ53S6IOM5VBTVOWX42DW7RXITYAOMEF52M6RUO6EGA26BTEVLKXLS5AN4KMGE]: state:DOWNLOAD error: meta:1 conns:1 io:0 [20161206 12:20:11.310] PD[B140] [6D82]: Sending ping to "192.168.1.10:60064" [20161206 12:20:11.395] SyncFolderNotify: SyncFolderNotify: "D76B709F276A8B29F9CB7AD9DFF601CB96917C33.!sync", event = "IN_MODIFY" [20161206 12:20:11.395] [OnNotifyFileChange] "/home/rslsync/shares/sync/.sync/D76B709F276A8B29F9CB7AD9DFF601CB96917C33.!sync" [20161206 12:20:11.395] TF[B140] [0x00007f2fec00bbe0][/home/rslsync/shares/sync/UPBWW6NDNON4BVATGDQ53XO3QLABMZKYQM3CBHU4FS762DNIFFZ45FIIV62EEXCXA5L563TAI4ZJ4OCHOJ3J3VOXKGRUYYLZXUPB3VA5T5EXSI4RFNFRDW5BFALKZG3GWY6KRAM7WY66XDSPXSTSXTIANQXXGQ53S6IOM5VBTVOWX42DW7RXITYAOMEF52M6RUO6EGA26BTEVLKXLS5AN4KMGE]: *** PIECE 155 FAILED HASH CHECK [20161206 12:20:11.395] TF[B140] [0x00007f2fec00bbe0][/home/rslsync/shares/sync/UPBWW6NDNON4BVATGDQ53XO3QLABMZKYQM3CBHU4FS762DNIFFZ45FIIV62EEXCXA5L563TAI4ZJ4OCHOJ3J3VOXKGRUYYLZXUPB3VA5T5EXSI4RFNFRDW5BFALKZG3GWY6KRAM7WY66XDSPXSTSXTIANQXXGQ53S6IOM5VBTVOWX42DW7RXITYAOMEF52M6RUO6EGA26BTEVLKXLS5AN4KMGE]: sending bad piece 155 to peer [6D82] nas: [20161206 12:20:11.415] PC[0xb483aab8][0xb3e63360][138.201.92.183:60064:TUNNELL] got bad piece 155 [20161206 12:20:12.313] TF[B140] [0xb3e63360][<< Path to file removed >>]: state:SEED error: meta:1 conns:1 io:0 nas-sync.tar.xz vserver-sync.tar.xz
  4. Hello, I've run into this problem already a couple of times: whenever I re-install a machine (running on Debian or Ubuntu), I first backup all the keys, then re-add all the folder after installation. Kind of tedious, given the fact that the data storage has not changed... I thought, it would be enough to backup /etc/resilio-sync/ /var/lib/resilio-sync/ ... and copy these folders back after re-installation Resilio Sync. Unfortunately, I'm greeted with the first-time installation dialog asking me to create a new user for the web-ui, which indeed does create a new .SyncUserXXXXXXXXXX in /var/lib/resilio-sync/ . I've been really scratching my head on how to just let Resilio Sync pick up the existing profile? Why doesn't it recognize the existing profile and wants to create a new one? I'm aware of this thread, but it didn't help or I didn't understand how it would apply to my situation. Thanks! Additional information: I've not changed any standard storage paths, i.e. /etc/resilio-sync/config.json points to: "storage_path" : "/var/lib/resilio-sync/",
  5. Trying to get sync working on Raspberry Pi 3, running the latest Jessie update (Pixel?) I've gotten it all running and folders syncing, but it will only fill in part of the circle and then it stops syncing and displays the error "Don't have permissions to write to selected folder" History shows a lot of "Finished Syncing file [path/file]" then abruptly switches to "Failed to download [path/file] -WriteToDisk" Both the successfully written to directories and the failed are owned by Pi, and permissions are 777. Also, in Preferences, under Web UI is says "Connection settings overwritten by config" but there is no config file in /opt/resilio/bin, only LICENCE.TXT and a files called rslsync (Presumably the executable) Installed via the instructions here: https://www.resilio.com/blog/official-linux-packages-for-sync-now-available I've no idea how it is launching (config or not, what user it is running under, etc) I should add, I am syncing two calibre libraries, one eBooks, one Audiobooks. The ebook lib has synced 2058 of 14,698 items (combined files and directories) and the Audiobook library has synced 543 or 980 items Help?
  6. Detected another bug ... if I already had folders synced, and I change the { "device_name": "newname" } it will crash the ARM/Linux version of Sync. I changed it back to the old name and at least my VPS sync (2.4.2) doesn't seem to repeatedly crash. My Raspberry Pi sync (2.4.1) crashes about once every few hours even for only two folders synced.
  7. Hi, I recently purchased Sync Pro from Resilio, but it seems to be having issues on my headless Raspberry Pi 3 backup server. My setup is as follows: Raspberry Pi 3 with Raspbian Jessie Lite Resilio Sync 2.4.1 for Linux ARM During the install process, I've created the following Sync configuration file: { "device_name": "Raspberry Pi Backup", "listening_port" : 0, "pid_file" : "/var/run/btsync.pid", "use_upnp" : true, "download_limit" : 0, "upload_limit" : 0, "webui": { "listen" : "0.0.0.0:8888", "login" : "admin", "password_hash" : "MY_HASH_HERE" }, "recv_buf_size" : 64, "send_buf_size" : 64, "max_file_size_for_versioning" : 250 } I've successfully synced a few folders, but now the process seems to die about midway through new folders. The only way to get it back is to reboot the Raspberry Pi because restarting the process asks for a Sync id again rather than using the already existing id. I've read in the forums that Sync has some issues with memory management. Does this mean Raspberry Pi devices should not be used? I thought NAS drives have low memory too, so how come those work? Any information would be helpful. My goal here was to back up the various directories in my Mac user directory to the Raspberry Pi. Thanks,
  8. Hi How might one reduce to amount of logging which accumulates in day-to-day operation of my Pi? My SD card isn't very large, and I'm concerned that the constant activity generated by Sync might consume more that its fair share of storage. I assume thing like log TTL or other variables related to the retention of log files / journals have a variable somewhere. Where would I find this variable in Debian / OSMC? These more granular variables don't seem to appear in the web GUI. Cheers, Geoff.
  9. BTSYNC DESKTOP GUI FOR ARCH, DEBIAN, UBUNTU AND OTHER DERIVED DISTRIBUTIONS If you are using Arch Linux, Ubuntu, Debian, Raspian or other derived distributions based on Debian and you are searching for an easy way to deploy BitTorrent Sync on your systems, this topic is definitively for you. Here you will find information about a family of easy to install packages that offer both a solution for the need of typical server/cloud operators as for interactive users. The desktop gui package is explicitly intended for desktop usage and provide a user experience similar to BitTorrent Sync on Windows or Mac OSX by still giving the user the possibility to customise his installation if he has special needs. This topic covers only the desktop user package. If you are searching for the server package, please look here. THE SOFTWARE AND THE PACKAGES ARE UNOFFICIAL AND NOT THE WORK OF BITTORRENT® INC. PLEASE DO NOT CONTACT THE BITTORRENT® INC. SUPPORT WITH QUESTIONS OR PROBLEMS RELATED TO THE USE OF THE PACKAGES. YOU WILL FIND COMPETENT HELP AND SUPPORT IN THIS FORUM THREAD INSTALLATION ON ARCH LINUX The Arch Linux Package in the AUR is maintained by Martin Wimpress (@flexiondotorg). The package is named btsync-gui and can be installed from the AUR using your favourite package manager. e.g.: if you are using yaourt: sudo yaourt -S btsync-guiWhen you have finished installing, you can skip the next section below and move directly to the USAGE NOTES. INSTALLATION ON DEBIAN, UBUNTU, LINUX MINT, RASPBIAN OR OTHER DEBIAN DERIVATES The most easy and fast way to install the repository is to paste that at a terminal prompt: sh -c "$(curl -fsSL http://debian.yeasoft.net/add-btsync-repository.sh)"The script explains what it will do and then pauses before it does it asking for your permission. If you encounter any problems or prefer to do it manually, please look here. Now update the package index and install btsync-gui by pasting that at a terminal prompt: `which sudo` apt-get update`which sudo` apt-get install btsync-guiOn some systems the AppIndicator library is not available or maybe you do not want to use it. In this case, you may want to install the GTK only version of the BitTorrent Sync GUI instead: `which sudo` apt-get update`which sudo` apt-get install btsync-gui-gtkPlease keep in mind, that this will work only on GTK based desktops. If you install it on other desktops like Unity, btsync-gui-gtk will start but you will see nothing and you have no control over the application! Install btsync-gui-gtk only if you know exactly what you are doing!!! If this happened, you can fix it by installing btsync-gui and rebooting your system. After the successful installation, you have to initially start BitTorrent Sync. You have various possibilities to do this: Log out and log in again. Since BitTorrent Sync GUI is registered in the autostart group, it will start as soon as you log in.Select BitTorrent Sync from the menu or the default application launcher of your desktop.USAGE NOTES The BitTorrent Sync GUI aims to be a clone of the original BitTorrent Sync application on Windows and Mac OSX and to replace on long term the legacy package btsync-user. The GUI provides two modes of operation: Standalone Mode: This is the default mode. When the GUI starts, an underlaying BitTorrent Sync agent is started too providing an overall experience similar to the GUI applications on Windows or Mac OSX.Client Mode: The GUI can be started from the command line with parameters specifying a connection to a remote BitTorrent Sync system. In this case, the GUI does not start a local BitTorrent Sync agent, but connects to an already running agent at a remote location. This will work only, if the remote agent has activated API access by specifying a valid API key in the configuration file.The behaviour of the GUI can be influenced by specifying various options on the command line. There is also a way to make some options persistent across restarts making it superfluous to specify the options each time you start the GUI. You can get detailed help about the command line options by invoking the man page: man btsync-guiHere you find an overview of the available options: usage: btsync-gui [-h] [--log {CRITICAL,ERROR,WARNING,INFO,DEBUG}] [--host HOST] [--port PORT] [--username USERNAME] [--password PASSWORD] [--bindui BINDUI] [--webui] [--savedefaults] [--cleardefaults]optional arguments: -h, --help show this help message and exit --log {CRITICAL,ERROR,WARNING,INFO,DEBUG} Sets the logging level. By default the logging level is WARNING --host HOST Hostname for the connection to BitTorrent Sync. If not specified, a local BitTorrent Sync agent will be launched. --port PORT Optional port number for the connection to BitTorrent Sync. If not specified, port 8888 is taken for a connection to a remote BitTorrent Sync agent or (8999 + uid) is taken when creating a locally lauched agent. This option can be made persistent for local agents with --savedefaults --username USERNAME Optional user name for connecting to a remote BitTorrent Sync agent or username to use when creating a locally launched agent. This option can be made persistent for local agents with --savedefaults --password PASSWORD Optional password for connecting to a remote BitTorrent Sync agent or username to use when creating a locally launched agent. This option can be made persistent for local agents with --savedefaults --bindui BINDUI Optional bind address for the Web UI of a locally created BitTorrent Sync agent. By default the agent binds to 127.0.0.1. If you want the Web UI of the agent to be reachable by other computers, specify one of the available IP addresses of this computer or "all" to bind to all available adapters. This option can be made persistent for local agents with --savedefaults --webui Include the Web UI in the menu. This option can be made persistent with --savedefaults --savedefaults If specified, the optionally supplied credentials, bind address and port will be stored as default in the application preferences and used when launching a local BitTorrent Sync agent. --cleardefaults If specified, all internally stored credentials, bind address and port information will be cleared from the application preferences.The usage of the command line options will be explained by some examples below. STANDALONE MODE By default there is no way to access the Web UI provided by the BitTorrent Sync agent, since the agent itself defines at each start random credentials to protect the system. If you still want to access the Web UI, you can activate an extended menu option by specifying --webui on the command line. You will then have an additional menu item, that invokes a browser and connects you to the Web UI. If you want to make this setting persistent, you can invoke the following command from the console: btsync-gui --webui --savedefaultsFrom now you will not need to specify it again at each start. Sometimes it may happen, that you want to access your running BitTorrent Sync agent from another computer via the Web UI or a btsync-gui in Client Mode. By default this is not possible, because of two reasons: The BitTorrent Sync agent binds the administration interface only to the loopback adapter making it possible to connect only from the same machine (This is a security feature).The BitTorrent Sync agent is started at every time with randomly generated credentials. Without knowing them, it is impossible to access the administration interface of the agent (This is also a security feature).For users that want to access their system from another computer, there is still a possibility to configure the GUI in a way that makes the agent accessible also from other computers. In order to do so, the following parameters must be changed: The BitTorrent Sync agent must bind its administrative interface to all adapters of the system or an adapter reachable from outside.The BitTorrent Sync agent must bind its administrative interface to a well-known port. By default the port is the sum of 8999 and the uid of the user.The credentials must be set to something known.The GUI can be launched in such a mode, by specifying the following parameters: btsync-gui --bindui 0.0.0.0 --port 10888 --username Leopoldo --password SuperSecretThis configures the BitTorrent Sync agent to bind on all interfaces on port 10888 and to be accessible with the user name "Leopoldo" and the password "SuperSecret". Also these settings can be made persistent by adding the option --savedefaults WARNING: as every comfort function, you pay the comfort by lowering the security. Remember: the product of comfort and security is a constant. You cannot increase both. CLIENT MODE In client mode, the GUI can be used to access a remotely running BitTorrent Sync agent. The only prerequisites are that the remote BitTorrent Sync agent is reachable from your computer, you know the credentials and the API access is enabled on the remote agent. You can also use the GUI to connect to another machine where a BitTorrent Sync GUI is running in standalone mode, if you have configured access possibilities like shown in the example above. The connection to a remote BitTorrent Sync agent is done by entering the following command: btsync-gui --host myserver.example.com --port 8888 --username Leopoldo --password SuperSecretIf you are able to access the Web UI of a remote BitTorrent Sync system, you should know everything you need to also launch successfully the GUI. Since the connection to remote systems is slower, you will notice the following limitations: The refresh rate is slower. It adapts dynamically to the overall performance.During the status refreshes, the GUI may be a bit unresponsive.There are no local file system checks, when you add a new folder. You must be sure, that you enter a valid path on the remote machine.Some features are disabled (Pause/resume, Enable/Disable Debug) since they are not feasible on remote systems.COMPATIBILITY The GUI packages are available for the same architectures as released by BitTorrent Inc.: i386 - Intel/AMD 32 Bitamd64 - Intel/AMD 64 Bitarmel - ARM EABIarmhf - ARM hard floatpowerpc - PowerPCThe GUI packages have been tested on the following distributions: Debian Wheezy with Gnome DesktopUbuntu Raring 13.04 with Unity DesktopLinux Mint Petra with Cinnamon DesktopOther users have reported successful installations on: Xubuntu Saucy 13.10 with OpenBox+Tint2Debian Jessie with KDEUbuntu Trusty 14.04 with Cinnamon, MATE and OpenBoxArch Linux with MATEThe GUI package has also been released for other Linux distributions: Arch Linux: Packages can be found in the AURWANTED Maintainers for other Linux distributions beeing able to write a suitable packaging for their favourite distribution: Centos/RHEL (rpm)Fedora (rpm)SLES(rpm)GentooNow it's up to you to test it and give me lots of feedback in order to extend this list. Any related feedback is highly appreciated. BUG REPORTS, CONTRIBUTION AND SOURCES If you want to contribute to the development of the packages or if you are curious how this all works, you may find the current sources, the deployment scripts and packaging on GitHub. If you want to contribute to the localisation by translating changed strings or by adding support for your favourite language, you may join the localisation team on POEditor.com. If you have experienced a reproducible issue that is related to the gui or the packaging and not to BitTorrent Sync itself you are strongly encouraged to open an issue on the project's GitHub Page. Issues related to the native functionality of BitTorrent Sync should instead be discussed by creating a new topic or partecipating to an already existing topic in the BitTorrent Sync Forum.
  10. Hello! I've tried to update from bittorrent sync to resilio sync on my Raspberry Pi today. When I try to install it (using the official instructions https://help.getsync.com/hc/en-us/articles/206178924-Installing-Sync-package-on-Linux), it does not launch, providing the following error: pi@raspberrypi:~ $ /usr/bin/rslsync Illegal instruction I've tried both arch=armhf and default packages. Is it possible to launch the resilio sync on Raspberry Pi?
  11. I've install btsync on a fresh Debian Jessie system (server). Used this documentation for installing: http://help.getsync.com/hc/en-us/articles/207689576-Installing-Sync-on-Linux If I manually run `sudo service btsync start` it starts and works ok. But after the system restarts it doesn't start. Here is what I get from `sudo service btsync status`: Apr 23 17:45:36 serveris systemd[1]: btsync.service: main process exited, code=exited, status=255/n/a Apr 23 17:45:36 serveris systemd[1]: Unit btsync.service entered failed state. Apr 23 17:45:36 serveris systemd[1]: btsync.service start request repeated too quickly, refusing to start. Apr 23 17:45:36 serveris systemd[1]: Failed to start BitTorrent Sync service. Apr 23 17:45:36 serveris systemd[1]: Unit btsync.service entered failed state.
  12. I installed Sync by following the instructions on your guide "Installing Sync on Linux". After installation, btsync failed to start. After some digging I found it the cause: btsync was compiled against glibc 2.16: /usr/bin/btsync: /lib/arm-linux-gnueabihf/libc.so.6: version `GLIBC_2.16' not found (required by /usr/bin/btsync) My system: Raspberry Pi Model B Rev 2 Debian GNU/Linux 7.11 (wheezy) Linux 4.1.19+ armv6l After manually installing the arm-version (not armhf), it worked. I had to edit /etc/init.d/btsync since the parameters where different.
  13. Hi, I made one small tweak to my config yesterday and since then, BTSync (latest official Linux version) no longer starts. Systemd kills it immediately, then retries infinitely, failing constantly. The change I made was the download directory for all the folders, from /path/a/b to /path/b. All paths exist and are accessible. The .sync folders are still present (though I did try deleting them all to see if that was causing an issue). Nothing else has changed. I've removed and purged btsync with apt-get, tried a basic config as well as my normal one. I've even tried the standard example from the installation. Nothing works, and what's weirder is nothing has (to my knowledge) changed on the system (a Pi). I've tried everything and am lost - some logs below, which hopefully someone can diagnose better than me. I think a dependency might be broken though... Thanks for any help! Will Systemd status May 23 18:58:44 raspberrypi systemd[1]: Started BitTorrent Sync service. pi@raspberrypi:~$ sudo systemctl status btsync.service ● btsync.service - BitTorrent Sync service Loaded: loaded (/lib/systemd/system/btsync.service; disabled) Active: inactive (dead) Docs: http://help.getsync.com/ May 23 18:58:25 raspberrypi systemd[1]: Stopping BitTorrent Sync service... May 23 18:58:30 raspberrypi systemd[1]: Stopped BitTorrent Sync service. May 23 18:58:32 raspberrypi systemd[1]: Starting BitTorrent Sync service... May 23 18:58:33 raspberrypi systemd[1]: Started BitTorrent Sync service. May 23 18:58:36 raspberrypi systemd[1]: Stopping BitTorrent Sync service... May 23 18:58:41 raspberrypi systemd[1]: Stopped BitTorrent Sync service. May 23 18:58:43 raspberrypi systemd[1]: Starting BitTorrent Sync service... May 23 18:58:44 raspberrypi systemd[1]: Started BitTorrent Sync service. May 23 18:58:46 raspberrypi systemd[1]: Stopping BitTorrent Sync service... May 23 18:58:50 raspberrypi systemd[1]: Stopped BitTorrent Sync service. pi@raspberrypi:~$ sudo systemctl status btsync.service ● btsync.service - BitTorrent Sync service Loaded: loaded (/lib/systemd/system/btsync.service; disabled) Active: inactive (dead) Docs: http://help.getsync.com/ May 23 18:59:46 raspberrypi systemd[1]: Stopping BitTorrent Sync service... May 23 18:59:51 raspberrypi systemd[1]: Stopped BitTorrent Sync service. May 23 18:59:53 raspberrypi systemd[1]: Starting BitTorrent Sync service... May 23 18:59:53 raspberrypi systemd[1]: Started BitTorrent Sync service. May 23 18:59:55 raspberrypi systemd[1]: Stopping BitTorrent Sync service... May 23 19:00:04 raspberrypi systemd[1]: Stopped BitTorrent Sync service. May 23 19:00:06 raspberrypi systemd[1]: Starting BitTorrent Sync service... May 23 19:00:06 raspberrypi systemd[1]: Started BitTorrent Sync service. May 23 19:00:09 raspberrypi systemd[1]: Stopping BitTorrent Sync service... May 23 19:00:14 raspberrypi systemd[1]: Stopped BitTorrent Sync service. Sync.log (for the standard config) [19:00:52.412] Debug log mask has been set to FFFF [19:00:52.413] Features mask has been set to 0 [20160523 19:00:52.423] Configuration from file "/etc/btsync/config.json" has been applied [20160523 19:00:52.442] ZIP: Can't locate [version] in zip, error -100. [20160523 19:00:52.453] PLC[0x01f321c0] binding on 0.0.0.0:25768 [20160523 19:00:52.453] Socket[0x01f321c0][8] bound listening socket 8 to IP 0.0.0.0:25768 [20160523 19:00:52.454] UDP: bound listening socket 9 to IP 0.0.0.0:25768 [20160523 19:00:52.454] Socket[0x01f32dc0][10] bound listening socket 10 to IP 127.0.0.1:8888 [20160523 19:00:52.458] UPNP: Using IP address 172.16.0.95 [20160523 19:00:52.490] test sha1: AE5BD8EFEA5322C4D9986D06680A781392F9A642 [20160523 19:00:52.490] test sha2: 630DCD2966C4336691125448BBB25B4FF412A49C732DB2C8ABC1B8581BD710DD [20160523 19:00:52.490] test aes: 0A940BB5416EF045F1C39458C653EA5A07FEEF74E1D5036E900EEE118E949293 [20160523 19:00:52.492] Loading config file version 2.3.7, current version 2.3.7 [20160523 19:00:52.492] My PeerID: 10344197918885B006FE520626BBF53C4462DA96 [20160523 19:00:52.493] loaded history: 0 events [20160523 19:00:52.495] setup socket 14 for local peer discovery for 127.0.0.1: success [20160523 19:00:52.495] setup socket 15 for local peer discovery for 172.16.0.95: success [20160523 19:00:52.496] setup socket 16 for local peer discovery for 10.136.1.6: success [20160523 19:00:55.478] Received shutdown request via signal 15 [20160523 19:00:55.483] saved history: 0 events [20160523 19:00:55.503] SyncFolderScanner: shut down [20160523 19:00:55.503] Shutdown. Saving config sync.dat [19:01:02.925] Debug log mask has been set to FFFF [19:01:02.927] Features mask has been set to 0 [20160523 19:01:02.961] Configuration from file "/etc/btsync/config.json" has been applied [20160523 19:01:03.012] ZIP: Can't locate [version] in zip, error -100. [20160523 19:01:03.029] PLC[0x012481c0] binding on 0.0.0.0:31140 [20160523 19:01:03.036] Socket[0x012481c0][7] bound listening socket 7 to IP 0.0.0.0:31140 [20160523 19:01:03.036] UDP: bound listening socket 8 to IP 0.0.0.0:31140 [20160523 19:01:03.037] Socket[0x01248dc0][9] bound listening socket 9 to IP 127.0.0.1:8888 [20160523 19:01:03.038] UPNP: Using IP address 172.16.0.95 [20160523 19:01:03.057] test sha1: AE5BD8EFEA5322C4D9986D06680A781392F9A642 [20160523 19:01:03.057] test sha2: 630DCD2966C4336691125448BBB25B4FF412A49C732DB2C8ABC1B8581BD710DD [20160523 19:01:03.058] test aes: 0A940BB5416EF045F1C39458C653EA5A07FEEF74E1D5036E900EEE118E949293 [20160523 19:01:03.059] Loading config file version 2.3.7, current version 2.3.7 [20160523 19:01:03.060] My PeerID: 10344197918885B006FE520626BBF53C4462DA96 [20160523 19:01:03.060] loaded history: 0 events [20160523 19:01:03.061] setup socket 14 for local peer discovery for 127.0.0.1: success [20160523 19:01:03.062] setup socket 15 for local peer discovery for 172.16.0.95: success [20160523 19:01:03.062] setup socket 16 for local peer discovery for 10.136.1.6: success Sync.log (for my usual config) [20160523 19:06:04.913] SyncFolderNotify: Added path=/home/epistrophy/bt/Will-FileStore/rsyncNEW/home/pi/btsyncOLD with fd=176 [20160523 19:06:05.127] UPnP: Device error "http://172.16.0.221:8060/": (-2) [20160523 19:06:06.129] Received shutdown request via signal 15 [20160523 19:06:06.131] saved history: 0 events [20160523 19:06:08.135] UPnP: Could not map UPnP Port on this pass, retrying. [20160523 19:06:10.163] UPnP: Device error "http://172.16.0.17:9000/TMSDeviceDescription.xml": (-2) [20160523 19:06:10.185] UPnP: Device error "http://172.16.0.137:7676/smp_2_": (-2) [20160523 19:06:10.187] UPnP: Device error "http://172.16.0.137:7676/smp_6_": (-2) [20160523 19:06:10.193] UPnP: Device error "http://172.16.0.125:49153/setup.xml": (-2) [20160523 19:06:10.196] UPnP: Device error "http://172.16.0.150:49153/setup.xml": (-2) [20160523 19:06:10.198] UPnP: Device error "http://172.16.0.137:7676/smp_10_": (-2) [20160523 19:06:10.199] UPnP: Device error "http://172.16.0.137:7676/smp_18_": (-2) [20160523 19:06:10.219] UPnP: Device error "http://172.16.0.17:9000/NMCServerDescription.xml": (-2) [20160523 19:06:10.255] UPnP: Device error "http://172.16.0.36:80/description.xml": (-2) [20160523 19:06:10.440] UPnP: Device error "http://172.16.0.19:49153/description5.xml": (-2) [20160523 19:06:10.623] UPnP: Device error "http://172.16.0.19:49153/description6.xml": (-2) [20160523 19:06:10.851] UPnP: Device error "http://172.16.0.13:8008/ssdp/device-desc.xml": (-2) [20160523 19:06:11.703] UPnP: Device error "http://172.16.0.19:49153/description4.xml": (-2) [20160523 19:06:12.157] UPnP: Device error "http://172.16.0.17:58130/": (-2) [20160523 19:06:12.285] UPnP: Device error "http://172.16.0.53:32469/DeviceDescription.xml": (-2) [20160523 19:06:12.493] UPnP: Device error "http://172.16.0.76:8080/dd.xml": (-2) [20160523 19:06:12.889] UPnP: Device error "http://172.16.0.221:8060/": (-2) [20160523 19:06:14.892] UPnP: Could not map UPnP Port on this pass, retrying. [20160523 19:06:14.892] NAT-PMP: Unable to map port with NAT-PMP. Config { "device_name": "Chuck Berry", "listening_port" : 0, "storage_path" : "/home/pi/btsync/", "pid_file" : "/var/run/btsync/btsync.pid", "sync_trash_ttl": 3, "agree_to_EULA": "yes", "folder_rescan_interval":300, "webui" : { "listen" : "0.0.0.0:1234" }, "shared_folders" : [ { "secret" : "x", "dir" : "/home/a1", "use_relay_server" : true, "use_tracker" : true, "search_lan" : true, "use_sync_trash" : true, "overwrite_changes" : false }, { "secret" : "y", "dir" : "/home/a2/", "use_relay_server" : true, "use_tracker" : true, "search_lan" : true, "use_sync_trash" : true, "overwrite_changes" : false }, { "secret" : "z", "dir" : "/home/a3", "use_relay_server" : true, "use_tracker" : true, "search_lan" : true, "use_sync_trash" : true, "overwrite_changes" : false }, { "secret" : "zz", "dir" : "/home/a4", "use_relay_server" : true, "use_tracker" : true, "search_lan" : true, "use_sync_trash" : true, "overwrite_changes" : false } ] } Systemd service file [Unit] Description=BitTorrent Sync service Documentation=http://help.getsync.com/ After=network.target [Service] Type=forking User=pi Group=pi UMask=0002 Restart=on-failure PermissionsStartOnly=true PIDFile=/var/run/btsync/btsync.pid ExecStartPre=/bin/mkdir -p /var/run/btsync ExecStartPre=/bin/chown -R pi:pi /var/run/btsync ExecStart=/usr/bin/btsync --config /home/pi/.config/btsync/config2.json [Install] WantedBy=multi-user.target
  14. An Unofficial Btsync Ubuntu/Debian Packaging Project Fork Bittorrent Sync is an awesome solution for many problems ranging from synchronizing large amounts of files to certain centralized governing bodies. About three years ago, @tuxpoldo and many other contributors created the unofficial packaging project for Ubuntu/Debian to ease deployments on these systems - the project has since evolved to fill in the missing gaps of the official Sync project and continues to provide packages for legacy Btsync clients. Current features include, but are not limited to: Easy installing and upgrading Generated configuration files (via an easy command line interface) Run as a different user/group Startup/Shutdown scripts Support for multiple instances Custom nice levels A Reboot Unfortunately, after several years of active work, it seems @tuxpoldo has moved on and the unofficial packages got a bit stale. Since all the work is open source I was able to build new packages (with a few tweaks here and there) and since many members of the community used the packages I decided to share my work publicly. An archive of the original post from @tuxpoldo: https://forum.getsync.com/topic/18974-debian-and-ubuntu-server-unofficial-packages-for-bittorrent-sync/ I will be providing continued maintenance for this awesome project and until I am accustomed to this project (or Python for the matter) I can provide support for the btsync and btsync-common packages with new binary versions and bugfixes. I personally use these packages on several headless servers to sync files and will particularly support that use case. Debian and Ubuntu packages can be found under my private repository http://deb.silvenga.com. New versions should be automatically built and published to this location via my build server (found above) when new changelogs are released. These packages should also work for other Ubuntu/Debian derivatives (Mint, LUbuntu, Raspbian, etc.). The source to these packages (e.g. build scripts, changelogs, etc.) can be found in my GitHub fork: https://github.com/Silvenga/btsync-deb. I encourage reporting issues with the packaging to this repository. Cheers! Installing Add my package signing key: apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 992A3C9A3C3DE741 Add the btsync repository: add-apt-repository "deb http://deb.silvenga.com/btsync any main" apt-get update Install btsync apt-get install btsync After following the prompts, open your browser to http://127.0.0.1:8888/gui/ (if using the default configuration). TODO List Log to proper log folder. (log path is now customizable via #6) Setup logrotate. (might not be needed) Fix the formatting of this post. FAQ Adding a new synced folder results in the following error: Make sure the user Btsync is running as has read and write access to the path set when prompted for the "Start path for the web interface". Alternatively, / can be used. You would receive something like the following when running apt-get-repository: Traceback (most recent call last): File "/usr/bin/add-apt-repository", line 167, in <module> sp = SoftwareProperties(options=options) File "/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 105, in __init__ self.reload_sourceslist() File "/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 595, in reload_sourceslist self.distro.get_sources(self.sourceslist) File "/usr/lib/python3/dist-packages/aptsources/distro.py", line 89, in get_sources (self.id, self.codename)) aptsources.distro.NoDistroTemplateException: Error: could not find a distribution template for Raspbian/jessie Raspbian's add-apt-repository seems to be broken under at last Jessie. The following commands will resolve the issues: echo "deb http://deb.silvenga.com/btsync any main" > /etc/apt/sources.list.d/silvenga-btsync-deb.list apt-get update apt-get install btsync Adding signing key fails with the following stacktrace: gpg: requesting key 3C3DE741 from hkp server keyserver.ubuntu.com gpg: no writable keyring found: eof gpg: error reading `[stream]': general error Make sure to run all the above commands as root either by using sudo or switching to the root user.
  15. Hi, I was pleased to see the official Linux packages release last week, but on Debian Jessie (on a Raspberry Pi), the CPU usage is up above 100% and often 150%. It's unusable. Has anyone else seen similar or knows a way around it, or do we have to wait for the Sync team to do a fix? Thanks
  16. BTSYNC PACKAGES FOR DEBIAN, UBUNTU AND OTHER DERIVED DISTRIBUTIONS BitTorrent® Inc. delivers for Linux users only a raw binary file without any deployment concept or setup system. It's up to the user to create a reliable startup and shutdown logic, manage configuration files, internal storage directories and everything else related to file and directory permissions, application update and various other aspects. The BitTorrent Sync Server Package (btsync) is the ideal solution for all users that want to deploy BitTorrent Sync on Linux servers running Debian or other derived distributions like Ubuntu, Raspbian, Linux Mint or similar. THIS SERVER PACKAGE IS UNOFFICIAL AND NOT THE WORK OF BITTORRENT® INC. PLEASE DO NOT CONTACT THE BITTORRENT® INC. SUPPORT WITH QUESTIONS OR PROBLEMS RELATED TO THE USE OF THE PACKAGE. YOU WILL FIND COMPETENT HELP AND SUPPORT IN THIS THREAD TYPICAL USE CASES The BitTorrent Sync Server Package is designed to run one or more BitTorrent Sync background processes (called "instances") on servers where no specific user is usually logged on. Since the server package does not provide any GUI (except for the optional Web UI provided by BitTorrent Sync itself), it can be also installed on headless servers (without any desktop environment). The server version is particularly suitable for the following use cases: BitTorrent Sync is used as a background service, to keep directories in sync between all servers of a distributed infrastructure like a PXE boot system and groups of shared configuration files.Always-on instances of BitTorrent Sync for providing an always available external copy and source of replicated data for other BitTorrent Sync clients.A content distribution network based on shared folders.Customized services built upon the functionality of BitTorrent Sync.This topic covers only the server package. If you are searching for the desktop user package, please look here.INSTALLATION ON DEBIAN, UBUNTU, LINUX MINT, RASPBIAN OR OTHER DEBIAN DERIVATES The most easy and fast way to install the repository with latest stuff is to paste that at a terminal prompt: sh -c "$(curl -fsSL http://debian.yeasoft.net/add-btsync-repository.sh)"If instead you wish to stay on version 1.4, you should paste the following command at a terminal prompt: sh -c "$(curl -fsSL http://debian.yeasoft.net/add-btsync14-repository.sh)"The script explains what it will do and then pauses before it does it asking for your permission. If you encounter any problems or prefer to do it manually, please look here.Now update the package index and install btsync by pasting that at a terminal prompt: `which sudo` apt-get update`which sudo` apt-get install btsyncAfter downloading the packages, the installation begins. The package manager will ask you, if you want a default instance of BitTorrent Sync to be created. If you answer yes, you will be guided through the installation and when finished you will have a fully operational BitTorrent Sync instance maintained by debconf. The configuration can be modified and fine tuned at any time by performing the following command: `which sudo` dpkg-reconfigure btsyncHere you can also choose to delete the default instance by answering no to the initial question.USAGE NOTES The BitTorrent Sync Server Package mainly consists of an init-style startup script that manages every operational aspect of running BitTorrent Sync instances. Instance Configuration Files All operational parameters for BitTorrent Sync instances are configured in configuration files located in the directory /etc/btsync. These configuration files basically are JSON Files and follow a very strict syntax. In addition to the JSON specification, comments are also supported. The support of commented lines permits to specify additional parameters that are not directly parsed by the BitTorrent Sync executable itself but by the init-script. The naming convention for configuration files defining BitTorrent Sync instances is: <instance_name>.confwhere <instance_name> should be a string consisting of alphanumeric characters.The default instance maintained by debconf has also a configuration file that is named debconf-default.conf. This name shall never be used by manually created configuration files, since it may be deleted or overwritten by debconf. This file shall also never be edited manually since it is often rewritten and/or created/deleted by debconf. If you want to manage the default instance, you must always use the command: `which sudo` dpkg-reconfigure btsyncEach configuration file in /etc/btsync defines a separate running BitTorrent Sync instance (that means: a process). When defining more than one instance on a system, there are some rules that must be considered:The listening ports (parameter listening_port) must be unique for each BitTorrent Sync instanceThe internal database path (parameter storage_path) must be unique for each BitTorrent Sync instanceIf the Web UI is enabled, the Web UI bind address and listening port (parameter listen) must be unique for each BitTorrent Sync instanceThe syntax and configuration parameters of a BitTorrent Sync configuration file are partially documented in the example file /etc/btsync/samples/complex.conf and in the official BitTorrent Sync manual which can be also found in /usr/share/doc/btsync-common/BitTorrentSyncUserGuide.pdf.gz.There are additional parameters that are parsed by the init script upon startup and affect many important aspects. These parameters are not parsed directly by BitTorrent Sync and therefore have to be placed in comment lines. In order to improve the readability of configuration files, they should be grouped together and placed at the beginning of the configuration file. The generic syntax of such parameters is: // PARAMETER_NAME=<parameter value>The following parameters are supported:DAEMON_UID: A uid (user id) for specifying the user under which the BitTorrent Sync instance should runDAEMON_GID: A gid (group id) for specifying the group under which the BitTorrent Sync instance should runDAEMON_UMASK: The umask (up to 4 octal digits) for the BitTorrent Sync instance. If omitted the default umask is used.DAEMON_DEBUG: The debug mask (4 hex digits) for the BitTorrent Sync instance. If omitted the init script will not touch potential settings defined manually. If set to 0000, a potential settings file will be deleted. Full detail is set by specifying FFFF. The log file can be found in the directory specified by storage_path and is named sync.logDAEMON_NICE: The niceness level of the BitTorrent Sync instance, which affects the process scheduling. Nicenesses range from -20 (most favorable scheduling) to 19 (least favorable).DAEMON_BIND: This parameter works only in conjunction with the package bind-shim. Please see the specific section below covering the specific interface binding topic.//// DAEMON_UID=jdoe// DAEMON_UMASK=0002//This example will launch the instance running under the credentials of the user "jdoe" using 0002 as umask.By specifying DAEMON_UID and DAEMON_GID it is possible to specify under which credentials the instance runs. In this case it must be assured that the instance is able to read and write all files it must access: The instance must be able to read its own configuration file. Since the configuration file may contain sensitive data (the userame and password for the web interface), it is usually owned by the user under which the instance runs and has the mode 400 (-r--------) in order to limit the access to the specific user. Usually the init script takes care of adjusting the file permissions.The instance must be able to read and write in its storage_path, since all internal control and status files (and the database of file hashes) are kept there. The ideal solution is to keep the storage_path somewhere in the home directory of the user under which the instance will run. Usually the init script takes care of adjusting the file permissions.Obviously the instance must be able to read and write the files and directories that will be synchronized.Some example configuration files are provided under /etc/btsync/samplesModular Configuration Files Sometimes it may be useful to generate configuration files out several separate parts. The typical use case is explained best by forum user Jero: If you want to create a modular configuration file, create a directory in /etc/btsync named like you would name the configuration file, but with an additional .d extension and put the parts of your configuration file in it. The daemon init script will generate a configuration file at every start by joining the parts in alphabetical order. Parts must be text files with the extension .part. Default Startup Parameters The additional configuration file /etc/default/btsync permits to specify some default startup parameters that may affect every configured instance of BitTorrent Sync. The variable AUTOSTART defines which instances are started automatically. It can take the following values: none No instance is started automaticallyall (default) All instances are started automatically<list> Only the specified instances are started automaticallyInstances not started automatically upon system startup can be managed manually from the command line: # start a specific instanceservice btsync start <instance_name># stop a specific instanceservice btsync stop <instance_name>The advanced variable DAEMON_ARGS allows to specify additional command line parameters passed to the daemon. WARNING: Be careful! You should only add things here if you know EXACTLY what you are doing!The variable DAEMON_BIND has the same purpose as the same parameter in the instance configuration files, but in this scope it will be applied by default to all instances. Please see the specific section below covering the specific interface binding topic. The variable DAEMON_INIT_DEBUG permits to enable extended debug output of the init-script. HANDLING OF SSL CERTIFICATES BitTorrent Sync 1.4 supports also SSL connections to the Web UI. The default instance is automatically configured to use a self signed certificate and key created during the installation. The configuration file does not point directly to the self signed certificate but to the following symbolic links: /etc/btsync/debconf-default.crt/etc/btsync/debconf-default.keyThe default instance can be operated also with user provided certificates without tampering with the configuration file by deleting the symbolic links and replacing them with files containing the desired certificate and key. Debconf will detect that the files are not symbolic links and leave them untouched during reconfiguration.The certificate file and key file must be accessible by the BitTorrent Sync daemon. BINDING BITTORRENT SYNC TO A SPECIFIC INTERFACE Unfortunately BitTorrent Sync currently does not support to bind the main service routine to a specific network interface. Currently only the internal web server providing the Web UI and the BitTorrent Sync API can be specifically bound to a specific address. In order to limit the operation of BitTorrent Sync to a specific interface in a multihomed environment, a so called preload shim) can be used. The BitTorrent Sync repository contains a precompiled version of Daniel Ryde's bind.so shim that must be installed with: `which sudo` apt-get install bind-shimThe BitTorrent Sync init script does detect the presence of the library and enables support for the additional parameter DAEMON_BIND that can be specified either in /etc/default/btsync or in instance configuration files.By specifying a valid TCP/IP address assigned to one of the interfaces of the system, the BitTorrent Sync instance will bind only to that specific address. This will affect also the Web UI, if 0.0.0.0 is specified as the bind address. COMPATIBILITY The server packages are available for the same architectures as released by BitTorrent Inc.: i386 Intel/AMD 32 Bitamd64 Intel/AMD 64 Bitarmel ARM EABIarmhf ARM hard floatpowerpc PowerPCSince the packages still have not been tested on every platform, any related feedback is highly appreciated.BUG REPORTS, CONTRIBUTION AND SOURCES If you want to contribute to the development of the packages or if you are curious how this all works, you may find the current sources of the deployment scripts and packaging on GitHub under the following URL: https://github.com/tuxpoldo/btsync-deb If you have experienced a reproducible issue that is related to the packaging and not to BitTorrent Sync itself you are strongly encouraged to open an issue on the project's GitHub Page. Issues related to the native functionality of BitTorrent Sync should rather by creating a new topic or partecipating to an already existing topic in the BitTorrent Sync Forum.
  17. I have a large amount of Sync folders running in Debian instead of running "/etc/init.d/btsync restart" is there a way to specify and restart only one instance?
  18. Hello, I am synchronizing a Debian server with a Synology NAS. It works but it is very slow (10KB/s). I am synchronizing 30 GB and the is about 50 files (300 MB/file). My NAS is behind a 15 Mega ADSL line and my server has a 1G fiber optic. If someone knows from where the problem come from. I am using btsync 2.0 on both. THank you
  19. Would it be possible to create an official .deb package of bittorrent sync? The unofficial (outdated) package can be used as a template and hence the amount of work involved should be minimal.
  20. I have a raspberry pi where I'm attempting to install btsync using the official deb package from here. I downloaded the deb using wget. Ran as sudo dpkg -i http://syncapp.bittorrent.com/2.2.2/bittorrent-sync-pi-server_2.2.2_armhf.debPackage appears to install but the btsync service start silently fails. When I run 'service btsync status' I get 'btsync for USER pi: not running'. When I try and start it via command line with either 'service btsync start' or 'sudo service btsync start' it tries to start but silently fails. Status once again reveals 'btsync for USER pi: not running'. Any ideas of what could be going wrong here?
  21. Hello, I recently installed Bitorent sync on my debian server. It was working perfectly until i tried to reboot my server to see if it restarts or not. I used this tutorial to install my server. http://bernaerts.dyndns.org/linux/75-debian/290-debian-server-btsync-permanent-peer#h5-declare-service-auto-start The autostart script do not work and when i try manually i get this error message: root@sd-41249:/home/btsync# service btsync startJob for btsync.service failed. See 'systemctl status btsync.service' and 'journalctl -xn' for details.If someone has an idea of what is wrong. Thank you,
  22. Currently have a running system between two computers (two Ubuntu servers) running v1.4. I have resisted upgrading to v2.0 until I added my third computer (Debian server) to the mix. That third computer is now functional. I intend to add the third computer with v1.4. After I am sure everything is functioning properly (and the third computer bittorrent directory is populated) then I would upgrade all machines to v2.0. (All computers are non-gui cammand line servers.) Does this computer addition/upgrade sequence seem illogical? Am I overlooking anything?
  23. BTSync 2.0 has been out as a stable release for the better part of a month. So why is the ReadyNAS platform, which is ostensibly supported, still "coming soon"? As I've mentioned in another thread, I have a really hard time coughing up money for the pro version when every update of BTS for ReadyNAS so far has been supplied by a hobbyist from that platform's forums. We saw more timely official updates from the free 1.x line.
  24. *** BREAKING NEWS *** The new full featured BitTorrent Sync GUI for Linux has been released! If you want to switch or are a new user, you should look at this posting. In future btsync-user may be replaced by the new btsync-gui. BTSYNC PACKAGES FOR DEBIAN, UBUNTU AND OTHER DERIVED DISTRIBUTIONS If you are using Ubuntu, Debian, Raspian or other derived distributions based on Debian and you are searching for an easy way to deploy BitTorrent Sync on your systems, this topic is definitively for you. Here you will find information about a family of easy to install deb-packages that offers both a solution for the need of typical server/cloud operators as for interactive users. The desktop user packages are explicitly intended for desktop usage and provide a user experience similar to BitTorrent Sync on Windows or Mac OSX by still giving the user the possibility to customise his installation if he has special needs. The server packages offer full debconf-support for the automated creation and maintenance of an optional default configuration as well as the possibility to manually configure single or multiple BitTorrent Sync instances with highly customised configurations. This topic covers only the desktop user packages. If you are searching for the server packages, please look here. THESE PACKAGES ARE UNOFFICIAL AND NOT THE WORK OF BITTORRENT® INC. PLEASE DO NOT CONTACT THE BITTORRENT® INC. SUPPORT WITH QUESTIONS OR PROBLEMS RELATED TO THE USE OF THE PACKAGES. YOU WILL FIND COMPETENT HELP AND SUPPORT IN THIS THREAD INSTALLATION ON DEBIAN, UBUNTU, LINUX MINT, RASPBIAN OR OTHER DEBIAN DERIVATES The most easy and fast way to install the repository is to paste that at a terminal prompt: sh -c "$(curl -fsSL http://debian.yeasoft.net/add-btsync-repository.sh)"The script explains what it will do and then pauses before it does it asking for your permission. If you encounter any problems or prefer to do it manually, please look here.Now update the package index and install btsync by pasting that at a terminal prompt: `which sudo` apt-get update`which sudo` apt-get install btsync-userAfter the successful installation, you have to initially start BitTorrent Sync. You have different possibilities to do this:Log out and login again. Since BitTorrent Sync is started on logon, it will start automatically.Select BitTorrent Sync from the menu or Unity-LauncherStart it from the terminal prompt by issuing the command:btsync startUSAGE NOTES This package of BitTorrent Sync is explicitly intended for generic desktop usage and provide a user experience similar to BitTorrent Sync on Windows or Mac OSX: When the user logs in, an instance of BitTorrent Sync is automatically launched under the user's credentials and a tray applet is launched to show the status and manage the running instance. By default the user instance has an automatical created configuration file in ~/.config/btsync/btsync-auto.conf and keeps its internal data in the directory ~/.btsync A user specific desktop shortcut to the web UI is installed into the system. Since every user has it's web UI on a different port number, only the desktop shortcut or the indicator applet should be used to invoke the web UI. In order to give more freedom to the advanced user, there is also a possibility to launch BitTorrent Sync with a custom configuration file instead of the automatically created file: the startup routine of BitTorrent Sync checks, if there is a file named btsync-user.conf in the configuration directory ~/.config/btsync of the user. If this file is found, then it is used as configuration file. If not, BitTorrent Sync uses the automatically created default configuration file ~/.config/btsync/btsync-auto.conf that will be recreated on every restart. The most easy way to create a custom configuration file, is to create a copy of the automatically created configuration file and then to edit it according to your needs: cp ~/.config/btsync/btsync-auto.conf ~/.config/btsync/btsync-user.confnano -w ~/.config/btsync/btsync-user.confWhen you are ready with your modifications, you can restart BitTorrent Sync by executing: btsync restarton the command line.In addition to the desktop shortcuts and menu functions in the indicator applet, BitTorrent Sync can also be controlled from the command line using the tool btsync. The tool provides usage instructions by issuing the command: btsync -hMore comprehensive help can be found on the corresponding manpage: man btsyncCOMPATIBILITY The legacy desktop packages are available for the same architectures as released by BitTorrent Inc.: i386 Intel/AMD 32 Bitamd64 Intel/AMD 64 Bitarmel ARM EABIarmhf ARM hard floatpowerpc PowerPCSince the packages still have not been tested with KDE, LXDE, Cinnamon and Linux Mint, any related feedback is highly appreciated.BUG REPORTS, CONTRIBUTION AND SOURCES If you want to contribute to the development of the packages or if you are curious how this all works, you may find the current sources of the deployment scripts and packaging on GitHub under the following URL: https://github.com/tuxpoldo/btsync-deb The full source of the great indicator applet written by Mark Johnson, is also hosted on GitHub and can be found under the following URL: https://github.com/marxjohnson/btsyncindicator If you have experienced a reproducible issue that is related to the packaging and not to BitTorrent Sync itself you are strongly encouraged to open an issue on the project's GitHub Page. Issues related to the indicator should be reported on the indicator's GitHub page. Issues related to the native functionality of BitTorrent Sync should rather by creating a new topic or partecipating to an already existing topic in the BitTorrent Sync Forum.
  25. I've three computers running version 1.3.93 on ubuntu/debian using the appropriate packages. There was a file which was deleted but the !sync file remained on one of the computers and now I'm in update hell as the three computer keep recreate the !sync file after I delete it. I delete the !sync file, restart btsync on all three computers and by magic and from the ether the sync file reappears. The three computers only connect by a predefijned host. Is there a way to manual purge the file from the database or to force a database reset or to do something as it is using bandwidth Any suggestions? Thanks Andy