Search the Community

Showing results for tags 'debian'.

  • 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 21 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 SM
  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 .SyncUser
  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 overwritte
  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",
  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. 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?
  10. 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 r
  11. 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.
  12. 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 e
  13. 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 up
  14. 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
  15. 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?
  16. 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
  17. 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.
  18. 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
  19. 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
  20. 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?
  21. 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.