• Content Count

  • Joined

  • Last visited

About scottfrey

  • Rank
  1. I suspect this is not accurate, as Resilio is literally the only application that I have had this problem with, every other install I have done has gottent the correct binary for the different architectures. Even when the install is first setup on the Pi3 and SD card moved tot he Pi Zero, it installs the correct binary for every thing else I have installed and updated. I have had to move to the much slower Syncthing as a reasult of this problem. You've lost any chance of a subscription from me.
  2. I haven't tried launching it with /usr/bin/rslsync --config /etc/resilio-sync/config.json However, manually starting with rslsync works after installing, but after running: sudo systemctl enable resilio-sync it never works again. that has been consistent behavior. It always throws the "start-limit" error after it's been enabled in systemctl once. Even if it is subsequently disabled. I don't have a build with Resilio installed to test right now as I have been trying to get Syncthing to work due to lack of progress on Pi Zeros with Resilio. I'll build up another one and brea
  3. Tried that. Manually launching runs fine, but not after enabling it with Systemctl. Starting with systemctl still throws the same errors. Also, would this bandaid not get undone when running apt-get upgrade?
  4. Hello? Lots of people reading this, no one has any information? @Helen, any thoughts on this? I haven't found anything regarding Pi Zero on Resilio's site other than this post. Is this a new issue or am I just the first person to ever test this?
  5. Following the instructions I am able to install and start successfully on a Pi3. Both old and current builds of JessieMoving the successfully installed SD card to a Pi Zero W, Resilio does not start on boot. manually starting generates the same error as before: Active: failed (Result: start-limit) since Tue 2017-05-09 04:38:42 UTC; 1min 48s ago Docs: does not show any results for "start-limit" nor Pi Zero. Clearly there is something with the Pi Zero hardware that is causing this
  6. I've confirmed that this failure still occurs when using an older Pi Zero (non wireless) and when using 2016-05-27-raspbian-jessie-lite. So, its not a Zero W issue and it's not a new Jessie-lite issue. I'll have to try on a Pi 3 next and see if it is a Zero hardware issue. It would really be a shame if it can't run on a Zero at all
  7. Following the official guide with a completely up to date install of Jessie Lite Using these instructions: after the second run of sudo apt-get update I get back: Reading package lists... Done W: Duplicate sources.list entry resilio-sync/non-free armhf Packages (/var/lib/apt/lists/linux-packages.resilio.com_resilio-sync_deb_dists_resilio-sync_non-free_binary-armhf_Packages) W:
  8. The permissions problem seems to have occurred when using ExFAT and vFAT formatted drives. Files got corrupted by sync, and upon reboot the drive was mounted as read only (and headless, there is no way to tell this occurs). I've successfully synced twice now with EXT4 formatted drives. The downside of EXT4 of course is there is no (stable) way to write to them other than on the Pi itself, So I am totally dependent on sync (no easy pre-seeding of drives) So, don't use ExFAT or vFAT (or likely NTFS or HFS+) format on a Pi running resilio, and this one is solved
  9. 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