dankshit
-
Posts
31 -
Joined
-
Last visited
Posts posted by dankshit
-
-
MacOS 13.4 :
Ventura upgrade (i.e. 12.62 to 13.4) trashed my EXT4 system (I paid for ext4 license) - so gave up on EXT4 - using APFS (encrypted) now - and seeing this error - but I cannot believe you haven't fixed this yet!
Unbelievable!
How am I supposed to figure which file it's missing???
I just upgraded to latest client on your downloads - and SAME ERROR!
Note: also - I also running 2.7.3 on another MBP running Ventura - and that's perfectly okay - not seeing the error there.
HOW DO I FIND OUT WHICH FILE? so I can decide whether I even care?
-
Jeepers - I can't believe they (note I run rsl pro with a license) haven't fixed this yet. Is resilio-sync still being maintained? Is it abandonware now?
I also ran into the false : disk space alert!
And luckily I documented it the first time it happened to me on a Pi Zero running the armel binary :
# change ~/.config/resilio-sync/config.json : # Add this line immediately below starting curly brace "{" on a new inserted line (note terminating comma on line mandatory) # "disk_check_free_space" : false,Hmmm - did another search and found another thread that recommended the Power User preferences under Advanced and changed disk_min_free_space from "0" to 0.125 and that fixed it...
-
Update - Sync is quite possibly the flakiest Android app I've EVER come across... it just completely crashes... every time!
Looks like I'm now in the market for some other solution than with my Resilio Sync pro license...
Note : after several wipes, deleted the folders Sync created on my internal storage, forced it to use SD-Card, added a new sync target from scratch (scanned QR code) - and I see it on my SD-Card when I connect from my PC (running Linux) - and in an Android file browser I can navigate to it on my SD-Card, so "Dude, I found my files" - but - there's hardly any there 'cause the dang app just keeps constantly crashing... My Galaxy S9+ is nothing special, not rooted, stock, latest updates from Samdung (sic). Why so flaky?
-
OK - I've been using RSL 6-7 years - worked a treat for me... loved it so much I bought a pro license in 2018 and use it instead of Dropbox...
Works nearly everywhere, nearly flawlessly... I mostly run Mac or Linux (mostly Linux)... but never had any major issues running it on my previous job's Windows 10 laptop either... Had a few issues with an iPad (3rd gen - yeah! ~4-5 years ago) ... But NO issues running it on my iPad pro 12.9" (2nd gen)... Also running it happily on a few headless ARM Linux machines... works a treat... no complaints (other than a few gripes with how it doesn't play well with SystemD on Pi Zero's - the armhf binary doesn't seem to like those - I have to run the binary manually anyway)...
But - decided to automate syncing music to my android phone, "stock" Galaxy S9+ (not rooted or anything) running Android 10... Ran into a heap of issues... Basically the app would just crash - no feedback.. fire it up... crash... sometimes I get to kill it (or wait)... So - I removed it... re-installed - same issue, it would just crash... If I can't fix this, I'll have to do it manually - which I can probably figure out with a combo of TermUX and rsync - but - I SHOULDN'T have to kludge this!
Troubleshooting for crashing (after my first uninstall/re-install did bupkis) :
1. "Clear cache"
2. "Clear date"
3. uninstall.
Browsed to my SD-Card from my Linux machine (i.e. using MTP over USB) deleted EVERYTHING I could find that looked like RSL stuff (bear in mind - this SD-Card has been cloned, and cloned again, and started life in a Galaxy Note 3, then a Nokia 4.2, before insertion into this Galaxy S9+)...
Powered off.
Re-installed App...
Used QR-scan to grab one of my smaller sync targets ( less than 5 GB)... It took forever to sync, but it finished (and crashed a few times!)... Now I tried to rename it from "old-name (2)" to just "old-name" (that's a place holder for the real name) - but it wouldn't let me - like it already "knew" it had once had a sync folder by that name... So - I decided to rename it to "...BUCKET" - and that worked... But now I cannot rename it back to "old-name"!
And worse than that - I have NO IDEA where on my SD-Card this sync target is located. I can't find it browsing over MTP via USB from my Linux box... Maybe I'll have to power off and insert the SD-Card into a reader on one of my Linux machines? See I don't mind, or care, that the iOS / iPadOS version abstracts direct filesystem access, as I don't need this on my iPad, BUT I WANT it on my Android phone, 'cause it's my music player, and I need to be able to point my (FLAC) music player "Music Folder Player Full" at the location of my sync'd music folder - BUT WHERE IS IT?
I also, really don't want to wipe/format this SD-Card (256 GB)... that's extreme...
-
A pointer where to find this mysterious "database" might be helpful... I've hit the same issue...
Tried to add a new sync folder to my S9+ running Android 10, and it kept hanging... So I removed ALL my sync folders off the device... removed the app..
Re-installed the app, now it just crashes about 5 minutes after I scan a QR code... And the sync folder is called "Music" and somehow, despite removing that sync folder, and Resilio Sync, completely (apart from this mysterious "database"), the folder still shows up on the Android side as Music(1) - which means that RSL has still got some hooks somewhere in my Android system, to that name... And no - I don't want to rename it... Note also - I can't change anything whatsoever in RSL on Android, it pretty much just hangs when I try to sync that folder...
It works pretty much flawlessly everywhere else, my iPad Pro running 15.6, my MacBook Pro M1, both my main Linux desktop machines, and my work MacBook Air (and when I still had a work Windows machine - it all worked swimmingly there too)... Why the glitches on Android?
If I wait a further 10 minutes after it stops responding, Android popups up a thing about unresponsive app and offers to let me kill it, or wait... Makes no difference which I choose, it's UNUSABLE!
-
Still ongoing... Lost power this morning... Noticed my Pi Zero W wasn't on my peer list...
Kill rsl, set it to disabled in systemd...
Run the binary I got else where via shell script "kickitoff.bash" :
cat kickitoff.bash #!/bin/bash ./rslsync --config ./config.json --webui.listen 0.0.0.0:8888Which is also how I run it on my FreeBSD shell account on my FreeNAS (but I also use the RSL plugin that used to be part of FreeNAS 11.x - but no longer listed).
-
It gets worse!!!
In some cases, the backup of the zero byte original file doesn't have the same name...
e.g. in $SHARE/bin/
bashtop (is zero btyes)
The backup in $SHARE/.sync/Archive/bin isn't called "bashtop" - it's called bashtop.2
So I can't just wildcard everything back again - I have to granularly manually locate EVERY F--KING F--KED up file and recover it...
This is complete bullshit... I'm going elsewhere, and whereever I go, I'm giving Resilio Sync ZERO stars out of FIVE stars...
Folks - DO NOT RELY ON THIS PRODUCT - it's not ready for primetime - and you'll get use to it (I've been using Pro for 3 years) then Mr Murphy will come along and F--K YOU OVER GOOD AND PROPER!
In the example above - "bashtop" isn't necessarily "my" shell script - but this example holds true for everything else...
And - it wasn't anything "I did" that zeroed all these files - it was YOUR PRODUCT!
-
This CRAP just happened to me today!
Latest Resilio Sync fresh install onto RPi4 running Kali 21.x (aarch64 - on a fresh install of kali)... I'm using Resilio Sync Pro - I have a pro a license.
So I try and sync connect a share (copy + paste key) after fresh install of RSLSync, client (using web UI to localhost) it tells me "database error" with nothing specific (e.g. WHAT IS THE ERROR?)... I removed it (Resilio Sync) completely (apt purge), rebooted, then re-installed and same issue, so I gave up, powered off the Pi running Kali...
But now ALL my sync files in that share on ALL my OTHER computers are now ZERO bytes in size! This is a MAJOR FLAW and a SERIOUS BUG!
This is on Ubuntu 20.04 x86_64, Raspbian Buster arm64, Ubuntu 21.04 x86_64 and arm64 - and MacOS on Macbook Pro M1!!!
I've been considering shopping around for another self-hosting cloud sync solution - and this might just push me elsewhere...
Note : it's not a "disaster" because the original files are in $SHARE/.sync/Archive - but - this is a REALLY CRAP gotcha... REALLY Annoying too! All my shell scripts I used for work are in that share and now they're ALL ZERO BYTES!
Seriously CRAP result, you get zero stars out of five from me!!! ~/bin is a symlink to a "bin" directory in a shared folder in ~/ResilioSync/ - on my Macbook Pro M1 :
╭─x@methone.local ~/bin ╰─➤ find . -maxdepth 1 -size 0k -ls 43152616 0 -rw-r--r-- 1 x staff 0 16 Sep 16:43 ./pigsies.bash 43152557 0 -rwxr-xr-x 1 x staff 0 16 Sep 16:43 ./unfux.bash 43152544 0 -rw-r--r-- 1 x staff 0 16 Sep 16:43 ./rs-helpoid.bash 43152538 0 -rwxr-xr-x 1 x staff 0 16 Sep 16:43 ./nodoze.bash 43152522 0 -rwxr-xr-x 1 x staff 0 16 Sep 16:43 ./McPasta 43152519 0 -rwxr-xr-x 1 x staff 0 16 Sep 16:43 ./ENIPee.bash 43152527 0 -rwxr-xr-x 1 x staff 0 16 Sep 16:43 ./eggo.bash ... ... 43152518 0 -rw-r--r-- 1 x staff 0 16 Sep 16:43 ./3users.txt 43152540 0 -rwxr-xr-x 1 x staff 0 16 Sep 16:43 ./nuku.bash 43152543 0 -rwxr-xr-x 1 x staff 0 16 Sep 16:43 ./queue.cue 43152517 0 -rw-r--r-- 1 x staff 0 16 Sep 16:43 ./0.0.10.not.finished 43152524 0 -rwxr-xr-x 1 x staff 0 16 Sep 16:43 ./bashtop 43152550 0 -rwxr-xr-x 1 x staff 0 16 Sep 16:43 ./splitmp3.bash 258962 0 -rw-r--r-- 1 x staff 0 6 Feb 2019 ./.stfolder 43152536 0 -rwxr-xr-x 1 x staff 0 16 Sep 16:43 ./neofetch 43152556 0 -rwxr-xr-x 1 x staff 0 16 Sep 16:43 ./tvhead.bash 43152532 0 -rwxr-xr-x 1 x staff 0 16 Sep 16:43 ./mailpdf.bash 43152555 0 -rwxr-xr-x 1 x staff 0 16 Sep 16:43 ./tranny.bash ... 43152552 0 -rwxr-xr-x 1 x staff 0 16 Sep 16:43 ./steamlink-pi.bash 43152545 0 -rwxr-xr-x 1 x staff 0 16 Sep 16:43 ./s3cr3thy.bash 43152534 0 -rwxr-xr-x 1 x staff 0 16 Sep 16:43 ./mcshow.bash 43152615 0 -rwxr-xr-x 1 x staff 0 16 Sep 16:43 ./boris-flood.cue 43152523 0 -rw-r--r-- 1 x staff 0 16 Sep 16:43 ./ZSH.zshrc 43152520 0 -rwxr-xr-x 1 x staff 0 16 Sep 16:43 ./EmPee.bash 43152553 0 -rwxr-xr-x 1 x staff 0 16 Sep 16:43 ./sunzolio.bash 43152542 0 -rwxr-xr-x 1 x staff 0 16 Sep 16:43 ./purvue.bash 43152549 0 -rwxr-xr-x 1 x staff 0 16 Sep 16:43 ./spectre-meltdown-checker.sh 43152546 0 -rw-r--r-- 1 x staff 0 16 Sep 16:43 ./screep.bash 43152533 0 -rwxr-xr-x 1 x staff 0 16 Sep 16:43 ./manual_mailpdf.bash 43152558 0 -rw-r--r-- 1 x staff 0 16 Sep 16:43 ./upgytdl.bash 43152547 0 -rwxr-xr-x 1 x staff 0 16 Sep 16:43 ./shitlist.bash 43152554 0 -rw-r--r-- 1 x staff 0 16 Sep 16:43 ./thou-audiotree.cue 43152541 0 -rwxr-xr-x 1 x staff 0 16 Sep 16:43 ./pastebin.bash 43152525 0 -rwxr-xr-x 1 x staff 0 16 Sep 16:43 ./clockuld.bash 43152529 0 -rw-r--r-- 1 x staff 0 16 Sep 16:43 ./gitfuckery.bash 43152526 0 -rwxr-xr-x 1 x staff 0 16 Sep 16:43 ./docxfind.bash 43152548 0 -rwxr-xr-x 1 x staff 0 16 Sep 16:43 ./slappem.bash 43152539 0 -rw-r--r-- 1 x staff 0 16 Sep 16:43 ./nuku.ascii 43152559 0 -rwxr-xr-x 1 x staff 0 16 Sep 16:43 ./watchtv.bash ... 43152537 0 -rwxr-xr-x 1 x staff 0 16 Sep 16:43 ./nocmur02.bash 43152521 0 -rwxr-xr-x 1 x staff 0 16 Sep 16:43 ./MUZ.bash 43152551 0 -rwxr-xr-x 1 x staff 0 16 Sep 16:43 ./spudchuq.bash 43152535 0 -rwxr-xr-x 1 x staff 0 16 Sep 16:43 ./merdepee.bashRPi4 running "buster" on arm64 :
╭─x@beere253 ~/bin ╰─➤ find . -maxdepth 1 -type f -size 0k -ls 527211 0 -rw-r--r-- 1 x x 0 Sep 16 16:43 ./pigsies.bash 527235 0 -rwxr-xr-x 1 x x 0 Sep 16 16:43 ./pastebin.bash 527246 0 -rwxr-xr-x 1 x x 0 Sep 16 16:43 ./spectre-meltdown-checker.sh 527344 0 -rw-r--r-- 1 x x 0 Sep 16 16:43 ./upgytdl.bash 527355 0 -rwxr-xr-x 1 x x 0 Sep 16 16:43 ./spudchuq.bash 527312 0 -rwxr-xr-x 1 x x 0 Sep 16 16:43 ./neofetch 527204 0 -rw-r--r-- 1 x x 0 Sep 16 16:43 ./0.0.10.not.finished 519542 0 -rwxr-xr-x 1 x x 0 Sep 16 16:43 ./purvue.bash 527283 0 -rwxr-xr-x 1 x x 0 Sep 16 16:43 ./watchtv.bash 527360 0 -rwxr-xr-x 1 x x 0 Sep 16 16:43 ./slappem.bash 527243 0 -rwxr-xr-x 1 x x 0 Sep 16 16:43 ./nocmur02.bash 527455 0 -rwxr-xr-x 1 x x 0 Sep 16 16:43 ./tranny.bash 517982 0 -rw-r--r-- 1 x x 0 Feb 6 2019 ./.stfolder 519143 0 -rw-r--r-- 1 x x 0 Sep 16 16:43 ./thou-audiotree.cue 527255 0 -rwxr-xr-x 1 x x 0 Sep 16 16:43 ./docxfind.bash 520041 0 -rwxr-xr-x 1 x x 0 Sep 16 16:43 ./boris-flood.cue 522009 0 -rw-r--r-- 1 x x 0 Sep 16 16:43 ./screep.bash 519350 0 -rwxr-xr-x 1 x x 0 Sep 16 16:43 ./sunzolio.bash 519124 0 -rw-r--r-- 1 x x 0 Sep 16 16:43 ./rs-helpoid.bash 519142 0 -rwxr-xr-x 1 x x 0 Sep 16 16:43 ./mailpdf.bash 521995 0 -rwxr-xr-x 1 x x 0 Sep 16 16:43 ./queue.cue 527385 0 -rwxr-xr-x 1 x x 0 Sep 16 16:43 ./MUZ.bash 527306 0 -rwxr-xr-x 1 x x 0 Sep 16 16:43 ./eggo.bash 527240 0 -rwxr-xr-x 1 x x 0 Sep 16 16:43 ./unfux.bash 519253 0 -rwxr-xr-x 1 x x 0 Sep 16 16:43 ./tvhead.bash 527314 0 -rwxr-xr-x 1 x x 0 Sep 16 16:43 ./ENIPee.bash ... 519144 0 -rwxr-xr-x 1 x x 0 Sep 16 16:43 ./splitmp3.bash 521997 0 -rw-r--r-- 1 x x 0 Sep 16 16:43 ./gitfuckery.bash 527357 0 -rwxr-xr-x 1 x x 0 Sep 16 16:43 ./bashtop 527358 0 -rwxr-xr-x 1 x x 0 Sep 16 16:43 ./mcshow.bash 527378 0 -rwxr-xr-x 1 x x 0 Sep 16 16:43 ./EmPee.bash 527454 0 -rwxr-xr-x 1 x x 0 Sep 16 16:43 ./merdepee.bash 527266 0 -rwxr-xr-x 1 x x 0 Sep 16 16:43 ./clockuld.bash 527392 0 -rwxr-xr-x 1 x x 0 Sep 16 16:43 ./manual_mailpdf.bash 527248 0 -rwxr-xr-x 1 x x 0 Sep 16 16:43 ./shitlist.bash 526825 0 -rwxr-xr-x 1 x x 0 Sep 16 16:43 ./nuku.bash 527176 0 -rw-r--r-- 1 x x 0 Sep 16 16:43 ./ZSH.zshrc 527380 0 -rw-r--r-- 1 x x 0 Sep 16 16:43 ./nuku.ascii 527323 0 -rwxr-xr-x 1 x x 0 Sep 16 16:43 ./steamlink-pi.bash 527207 0 -rwxr-xr-x 1 x x 0 Sep 16 16:43 ./McPasta 519140 0 -rwxr-xr-x 1 x x 0 Sep 16 16:43 ./s3cr3thy.bash ... 519625 0 -rw-r--r-- 1 x x 0 Sep 16 16:43 ./3users.txt ... 527391 0 -rwxr-xr-x 1 x x 0 Sep 16 16:43 ./nodoze.bashThis is a NIGHTMARE to go and fix now!!! I now have to manually HUNT and PECK through EVERY F--KING FOLDER and figure out what files got ZEROED 'cause not every file got ZEROED - and - some files are SUPPOSED to be ZERO anyway!
Can I even ever trust your product again???
I'm half thinking I might REMOVE that share from Resilio Sync, rebuild that folder tree and files again from scratch/backups, then re-share - but - that's a REAL F--KING PAIN in the @RSE! I have up to 13 computers subscribed to this share...
MAJORLY PISSED OFF disgruntled potentially former user of your (formerly good - but now RUBBISH) product...
-
I've got rslsync installed and running the EXACT same way on Ubuntu 21.04 aarch64/arm64 on a pair of RPi4B...
I've got rslsync installed and running just fine on Ubuntu 20.04 on x86_64 (Ryzen 7 desktop).
Here's the Ryzen 5 laptop (Lenovo E495).
I have to start it manually every time I boot up - even though it's enabled :
Quote╭─x@fenrir ~
╰─➤ uname -a
Linux fenrir 5.11.0-25-generic #27-Ubuntu SMP Fri Jul 9 23:06:29 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux╭─x@fenrir ~
╰─➤ systemctl --user status resilio-sync
● resilio-sync.service - Resilio Sync service
Loaded: loaded (/usr/lib/systemd/user/resilio-sync.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2021-08-09 17:23:59 AWST; 5s ago
Docs: https://help.getsync.com/
Process: 19863 ExecStartPre=/etc/resilio-sync/init_user_config.sh (code=exited, status=0/SUCCESS)
Process: 19866 ExecStart=/usr/bin/rslsync --config /home/x/.config/resilio-sync/config.json (cod>
Process: 19868 ExecStartPost=/bin/sleep 1 (code=exited, status=0/SUCCESS)
Main PID: 19867 (rslsync)
CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/resilio-sync.service
└─19867 /usr/bin/rslsync --config /home/x/.config/resilio-sync/config.jsonAug 09 17:23:58 fenrir systemd[2290]: Starting Resilio Sync service...
Aug 09 17:23:59 fenrir systemd[2290]: Started Resilio Sync service.Anyone have any ideas what I should be looking for? The only other problems I've had with rslsync pro over the last 3-4 years is getting it to run on a Pi Zero (some issue with the binary)
This 21.04 started "life" as 20.04 and was upgraded... There's nothing "special" about it - it does have "/" encrypted with ZFS - but - that happens WAY before any user stuff should be starting (e.g. my "old" Dell Latitude laptop running 20.04 has LUKS "/" and never had issues with ResilioSync on it)...
-
I run it (2.6.3) via the included jail/plugin on my FreeNAS...
But I also run the FreeBSD "binary" (2.6.2 - I guess I should update it - but it works) on its own, in my shell account on my FreeNAS - something like :
./rslsync --config ./rsl-config.json --webui.listen 0.0.0.0:8888I only have one sync folder with this method for my shell account, that's my shell scripts I use nearly everywhere, that fit nearly everywhere (e.g. in 4 GB NAND SBC's running debian).
-
20 hours ago, Andy+ said:
For such cases a FTP Server would be good.
Amen... would make things heaps easier for me... for now - I'd rather keep running 2.6 series on all my devices... because for now my NAS (FreeNAS) seems to be "locked" at 2.6.3 - instead of having to "reformat" those URL's for each platform, and hoping to get the filename right - being able to FTP / HTTP browse the files would make it SO MUCH easier!
-
@Andy+ yes - for 2.6.3...
All the links (for DEB and RPM) for the original post now point to 2.7.2...
-
Hi,
All the DEB (and RPM) links are for 2.7.2 not 2.6.3.
Can we get links to download DEB packages (for all platforms - i.e. arm64/aarch64, armel, armhf, amd64, i386)?
-
On 10/20/2018 at 5:29 AM, ghoff said:
I see the same error using resilio-sync_2.6.1-1_armel.deb on a Pi Zero. I downgraded to 2.5.13-1 and that resolved the problem.
Been hunting for the last 4 hours for an older deb file for armhf I can install - because on my Pi Zero W running "buster" the installer installs a binary that won't run - at all - from systemd - I got past this issue by manually copying the binary rslsync from the armhf tar file - but the Pi Zero W install is complaining about "Not enough free space on the drive." - when it's running on a 128 GB SD card :
Filesystem Size Used Avail Use% Mounted on /dev/root 117G 1.4G 111G 2% /rslsync will create the directory structure of my sync folder, but it's just a stack of empty folders...
I've tried adding/appending this to my ~/.conf/resiliosync/config.json file :
{ "disk_check_free_space": false }and it won't even start (and various combinations of the above) - so I removed that...
Pi Zero W details :
x@frambo:~/.config/resilio-sync $ uname -a Linux frambo 5.4.72+ #1356 Thu Oct 22 13:56:00 BST 2020 armv6l GNU/LinuxWhere did you @ghoff find a copy of 2.6.1-1? Because I only seem to be able to download 2.7x versions...
Probably going to log a ticket as I'm paying for pro version...
Note also : I've got rslsync running perfectly on 5 x Ubuntu 20.04 desktops, and 3 RPi 4B (one running aarch64, two running armhf), plus 2 x NTC CHIP (Jessie) and 1 x Oracle Pi+2E (running Armbian Xenial), plus my work's Windows 10 laptop...
-
Hi,
I'm running Resilio Sync (pro license) just fine on a bunch of stuff :
- Via the "jail" plugin on my FreeNAS (11.2)
- 6 x installs on Ubuntu 20.04 (Intel and AMD and laptops and desktops)
- 4 x installs on Raspbian Buster on RPi 3 and 4B (running either armhf or aarch64)
- 1 x install on Armbian (Xenial) on an Orange Pi+ 2E
- 2 x install on Debian Jessie on NTC CHIP (including PocketCHIP)
- 1 x install on Windows 10 "corporate" laptop
But I'm stumped if I can get it working on Raspbian Buster on a Pi Zero W...
First snag I hit was the binary / systemd backend wouldn't even start (issue with binary "rslsync") - so I did the workaround (got the armhf tar file and cp'd the binary to /usr/bin/rslsync). That got me over one hurdle.
But now EVERY time I try to setup a sync folder - I get status : "Not enough free space on the drive." - I've got a sh!tload of free space, it's headless debian on a 128 GB SDcard! I've seen (via google-fu) other uses have the same problem on Raspbian (some on Zero, some on 3B board), but this ONLY happens to me on Raspbian buster armhf running on Pi Zero W (I've gone the whole route of flashing a new image twice now - and hit the same wall). This is my first Pi Zero board...
Anyone know a fix for this?
-
Hi,
I'm running Resilio Sync (pro license) just fine on a bunch of stuff :
- Via the "jail" plugin on my FreeNAS (11.2)
- 6 x installs on Ubuntu 20.04 (Intel and AMD and laptops and desktops)
- 4 x installs on Raspbian Buster on RPi 3 and 4B (running either armhf or aarch64)
- 1 x install on Armbian (Xenial) on an Orange Pi+ 2E
- 2 x install on Debian Jessie on NTC CHIP (including PocketCHIP)
- 1 x install on Windows 10 "corporate" laptop
But I'm stumped if I can get it working on Raspbian Buster on a Pi Zero W...
First snag I hit was the binary / systemd backend wouldn't even start (issue with binary "rslsync") - so I did the workaround (got the armhf tar file and cp'd the binary to /usr/bin/rslsync). That got me over one hurdle.
But now EVERY time I try to setup a sync folder - I get status : "Not enough free space on the drive." - I've got a sh!tload of free space, it's headless debian on a 128 GB SDcard! I've seen (via google-fu) other uses have the same problem on Raspbian (some on Zero, some on 3B board), but this ONLY happens to me on Raspbian buster armhf running on Pi Zero W (I've gone the whole route of flashing a new image twice now - and hit the same wall). This is my first Pi Zero board...
Anyone know a fix for this?
-
Hi,
I'm running Resilio Sync (pro license) just fine on a bunch of stuff :
- Via the "jail" plugin on my FreeNAS (11.2)
- 6 x installs on Ubuntu 20.04 (Intel and AMD and laptops and desktops)
- 4 x installs on Raspbian Buster on RPi 3 and 4B (running either armhf or aarch64)
- 1 x install on Armbian (Xenial) on an Orange Pi+ 2E
- 2 x install on Debian Jessie on NTC CHIP (including PocketCHIP)
- 1 x install on Windows 10 "corporate" laptop
But I'm stumped if I can get it working on Raspbian Buster on a Pi Zero W...
First snag I hit was the binary / systemd backend wouldn't even start (issue with binary "rslsync") - so I did the workaround (got the armhf tar file and cp'd the binary to /usr/bin/rslsync). That got me over one hurdle.
But now EVERY time I try to setup a sync folder - I get status : "Not enough free space on the drive." - I've got a sh!tload of free space, it's headless debian on a 128 GB SDcard! I've seen (via google-fu) other uses have the same problem on Raspbian (some on Zero, some on 3B board), but this ONLY happens to me on Raspbian buster armhf running on Pi Zero W (I've gone the whole route of flashing a new image twice now - and hit the same wall). This is my first Pi Zero board...
Anyone know a fix for this?
-
Resilio Sync "pro" (pro 5 user license)
I've got a sync source on my FreeNAS Resilio Sync "master" (using the plugin jail)...
Every single time I setup a new "destination" to sync from my master source - I get this (see screenshot).
It's not a show stopper - but it's annoying, I can "ignore" sure - but I'd like to get rid of it permanently. I cannot find that file in the Resilio Sync "jail" running on my FreeNAS server...
When I originally would have copied that file there - it was a mistake - it's a 20+ GB OVA of a Windows 7 VM (VirtualBox), and I would have realised this, at the time, and removed it, and this would have been in 2018..
But something thinks it's still there. How do I tell it that file's no longer there and to stop Resilio Sync blabbering on about it?
Any ideas?
-
Thanks so much @alex - that solved it for me!
Just port forward allowed TCP port to NAT rule on my router then translate to listening port number on the RSL jail on my FreeNAS box!
Cheers mate!
-
I just thought about this again, and I don't think some sorta NAT thingie will work :
SOURCE TCP-Port -> DESTINATION:PORT -> NAT-DEST:NAT-Port desktop 30400 -> myhost.dynds.com:30400 -> home-PC:60870Anyone have any ideas? Am I going about this all wrong?
-
Product Resilio Sync Pro 2.6.3 (1340)
Pro - as in 5 user license/subscription.
Platform(s) : Ubuntu 19.10, Ubuntu 18.04, FreeNAS 11.2 (but also a Win10 laptop at work - happy to leave this out of the equation).
Okay - I've done various searches but unable to find more specific information I'm looking for.
Everything was working "tickety-boo" in 2018, till my employer started blocking a "vast" range of anything to anywhere TCP/UDP ports... I'm on good terms with one of the Network administrators, and he gave me a list of TCP ports open to "anywhere", e.g. armed with this information I can now ssh to my Raspberry Pi from my desk at work, with a NAT rule on my router.
Currently I've implemented a "kludge" - I keep my main home computer (Dell Laptop running 19.10) connected/sync'd via my employer's VPN (horrible Checkpoint SSL product), and I've got "Predefined Hosts" pointing to the IP address of my work Laptop running 19.10, using port 60870. This works.
Another even "kludgier" workaround I was using was to insert a 256 GB thumb drive into a BananaPi (M1, running Armbian), running on a LiPo battery, sync everything to there from "home", plonk it on my desk (got a dumb Gbit switch on my desk) and get it sync'd, but the Pi ethernet NIC is a bit "dodgy", had to keep rebooting it (pulling power and pressing power button) - i.e. take it into work, and home again, everyday...
So - given this information :
Work will let me
SOURCE DESTINATION TCP PORT office anywhere 30400 office anywhere 31400 office anywhere 32400 office anywhere 4020 office anywhere 4022 office anywhere 4023 office anywhere 5671 office anywhere 5672i.e. no UDP it seems, and not "ranges of ports" unless e.g. 5671-5672... Also - I'm using one of these for my SSH NAT rule to my RPi.
Here's my "Predefined Hosts" settings for one of my shares, from the Ubuntu machine @home that I keep VPN'd to the office :
"tenrji-wk" is an /etc/hosts file entry, pointing to the DCHP leased IP address of my work Ubuntu laptop... I have to edit /etc/hosts if my work computer gets a new DHCP lease.
Armed with this information, could I perhaps :
Setup (at least one) of my work Resilio Clients to send out on TCP port 30400 to my NoIP dynamic hostname, with my broadband router having a NAT rule to send this traffic to some "port" (e.g. 60870) on one of my home computers.
e.g. :
SOURCE TCP-Port -> DESTINATION:PORT -> NAT-DEST:NAT-Port desktop 30400 -> myhost.dynds.com:30400 -> home-PC:60870 -
@aarona : I'm using the Jail plugin on FreeNAS 11.2 - and it just kinda "worked" out of the box.
What I did initially have trouble with was getting it to also run in the main FreeNAS O/S as my user account on there...
Basically - created ~/sbin in my home dir on the actual NAS (i.e. in the shell of the main O/S of the NAS, not a jail)
Unzipped the binary for rslsync in there...
Created a config in ~/sbin/rsl-config.json (don't have access to a copy here - but basically I changed the "127.0.0.1" to "0.0.0.0").
Then changed to ~/sbin (i.e. cd ~/sbin)
Ran "./rslsync --config ./rsl-config.json --webui.listen 0.0.0.0:8888" (pretty sure it's probably ignoring the "rsl-config.json file - with my "--webui.listen" argument - i.e. redundant - but it worked).
Then connected browser to IP address of my NAS : e.g. "http://10.0.0.10:8888/" and add new sync folder keys... My Resilio Sync jail on the NAS has a different IP address than the main O/S of the NAS.
Note : that rslsync jail is not the same one in my original post - I had to rebuild my NAS again from scratch - had a hard drive fail in it - and when I went to replace with a new 4 TB drive - the FreeNAS GUI tools confused me such that I added the replacement drive as a stripe member instead of "data + parity" member - so had to dash out - buy a 6 TB USB HDD - back EVERYTHING up - then rebuild as a new FreeNAS instance, with a new RSL jail... but the new Resilio Sync plugin jail install was painless...
Also - my wifi/router does DHCP - once I saw what IP address the RSL Plugin / Jail was getting - I set it to dedicated/permanent lease... but there's also an option in the Jail configurator to set a static IP address...
-
Happily running sync on following platforms :
FreeNAS 11.x (using the jail plugin - actually installed it from 3000 km away about 12-14 months ago) - HP NL40 microserver 8 GB RAM 12 TB storage
- Raspberry Pi 3b Stretch (x 2)
- Ubuntu 18.04 (x 4 physical hosts, AMD desktop, 2 x Dell i7 laptops, plus a Gigabtye Brix)
- BananaPi m1 running Armbian 5.6
- iPad Pro 12.9
- Windows 10 laptop
-
Here's my problem - I've got two laptops at my work desk, my "main" one runs Ubuntu 18.04 which I bring from home (it's my personal laptop, but most days leave it at work because I can't be bothered lugging it during my daily commutie), the other runs Windows 10 supplied by work (pretty much just use it for skype 4 business and couple of nasty proprietary windows only "service desk" applications)...
The Ubuntu host NEVER seems to sync with my stuff at home when located at the office - but strangely enough, sometimes the Windows 10 sync does get updates "over the cloud" from my home network.
So - I bought a "tiny" 256 GB USB 3.1 thumb drive - and inserted it into my Banana Pi (m1) running Armbian. I've soldered battery terminals and a LIPO onto the board. This is the "original" Banana Pi (model 1?) A20 dual core, 1 GB RAM, pretty much running headless...
I take that home every day and bring it back into work the next day - and (Resilio Sync) sync over ethernet in both cases (work's wifi is flakier than my home wifi and the Banana doesnt have wifi anyway)... Battery (2700 mah?) drops to 63% capacity during my 45-60 minute commute... so I reckon I'd probably get 3 hours out of it if pushed...
So - no mattter what corporate firewall rules are in place - my data is sync'd ... it's nearly all just a subset of my music collection, documents and shell scripts... I've got a license for Sync Pro, but I don't use selective sync, just three separate sync folders (shell scripts, documents, Music)...
Can't download file
in Sync Troubleshooting
Posted
Fourth time trying this - still getting "Can't download file" but not telling me which file!
Gave up...
Reformatted drive again - used a Linux host (instead of my FreeNAS, and when that failed I tried another MacOS M1 MBP and same deal) to copy a sync link... and it's now working - but CAN'T you fix this so it can tell use which file it couldn't copy? I know there's a list somewhere, but sometimes it's like 1000 files below the most recent entry... It's not re-assuring... Makes me not want to trust your product...