First off topic - I miss the chat! Am I the only one?
Second - I finally have my Synology DS1019+ and want to migrate from my Raspberry Pi3… So my idea was (and I remembered it from chat) to make sure Docker is running on the Synology (done), I also enabled SSH and created a user who is part of admin group so I can login.
Created a specific folder etc.
Now: I then looked in the old chat for rsync and tried a bit with it to copy the files while the node is still running. (As in doing it once to get most stuff, then again to get the latest ones. Then stop node and doing it once more to have it all). Then restart the node on the Synology.
So here’s my problem, I tried it from both sides (pi to synology and vice verca) but somehow I don’t get it correct with the rights or so:
sudo rsync -rtuvP username@192.168.x.x:/home/pi/DROBO /volume1/Storj/
pi@192.168.x.x's password:
receiving incremental file list
rsync: opendir "/home/pi/DROBO/storage" failed: Permission denied (13)
rsync: send_files failed to open "/home/pi/DROBO/kademlia": Permission denied (13)
rsync: send_files failed to open "/home/pi/DROBO/revocations.db": Permission denied (13)
So I do understand that as on the pi itself to access the files I need to ‘sudo ls’ so to speak.
Now if I go to the pi3 and do it from there:
sudo rsync -rtuvP home/pi/DROBO username@192.168.x.x:/volume1/Storj/
username@192.168.x.x's password:
Permission denied, please try again.
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(235) [sender=3.1.2]
As I’m also a N00b I always run into these wonderful problems. My interpretation for case 1 is: Right issue hence rsync can’t read it.
For the 2 case it might be that I either have an right issue on the Synology or something with rsync doesnt work?
The problem could be the permissions. Docker creates the files as root so you might have problems copying them as username.
You should do this first: sudo chown -R username 192.168.x.x:/volume1/Storj/
Thanks - I had it enabled already but this might do the trick now, I didnt check the box and added an account (I though it takes the ones already created). Let’s see…
I don’t know whether it’s related to your problem, but you need the trailing / on the source AND destination. Otherwise you copy the folder DROBO into the destination and not only the content of that folder.
Furthermore you should also use the --delete option to delete the files from the destination which don’t exist in the source anymore.
I cancelled it … and then changed command to --delete-after
At the moment it’s looking better:
sudo rsync -rtuvP --delete-after /home/pi/DROBO/ tankmann@192.168.2.119:/volume1/Storj/
tankmann@192.168.2.119's password:
Could not chdir to home directory /var/services/homes/tankmann: No such file or directory
building file list ...
169393 files to consider
kademlia
262,144 100% 41.54MB/s 0:00:00 (xfr#1, to-chk=169388/169393)
storage/
storage/info.db
336,223,344 14% 4.35MB/s 0:07:20
Not sure why the info.db copies so slow but at least I’m copying stuff.
Let’s see when files should be deleted later in case they’re ot at the source any longer - I still feel there’s a permission problem somehow.
YAY. Just was able to move the Node to the Synology… it’s running fine as well, only problem now is, it has been paused one or two days ago I assume from the logs on the pi3