you haven't given a whole lot of information about how you are setting up your users, so I can't really answer your question
What user is initiating the backup on centos? which user is saving the data on FreeNAS? What is the rsync command being deployed to initiate the file transfer? Also, you say that you just changed /nonexistent to /root, but where? Did you make this change on FreeNAS, through which interface? Or was it on CentOS? I can tell that you are running an rsync based backup application, but other than than i know pretty much nothing about your setup. The error message you gave was pretty straightforward, but without knowing which applications you have configured where, I don't know what the root cause of that error is. On Sun, Nov 24, 2019 at 7:10 PM <mich...@robinson-west.com> wrote: > November 24, 2019 8:52 PM, "Ben Koenig" <techkoe...@gmail.com> wrote: > > > SSH keys are *usually* stored in $HOME/.ssh, and the error you are seeing > > clearly indicates that this folder cannot be created. Since it cannot > > create the folder, it cannot store your public key, and therefore cannot > > authenticate via key pair. I'm fairly new to FreeNAS, but on my box > > /nonexistent/ literally does not exist. > > > > My understanding is that this is a keyword used for users that run > without > > home directories. Which user are you attempting to use on the FreeNAS > end? > > Whatever user it being used to read/write files on your NAS box appears > to > > be configured to run without a $HOME folder, and will be unable to store > a > > public key for authentication. > > > > This is is just a guess but if the BackupPC app runs as a given user, you > > may need to add a home folder for that user. Then you will be able to > > transfer your public key to it. > > -Ben > > > > On Sun, Nov 24, 2019 at 6:12 PM <mich...@robinson-west.com> wrote: > > > >> This is the rsync child about to exec /usr/local/bin/rsync_bpc > >> Could not create directory '/nonexistent/.ssh'. > >> Host key verification failed. > >> rsync_bpc: connection unexpectedly closed (0 bytes received so far) > >> [Receiver] > >> Done: 0 errors, 0 filesExist, 0 sizeExist, 0 sizeExistComp, 0 > filesTotal, > >> 0 sizeTotal, 0 filesNew, 0 sizeNew, 0 sizeNewComp, 2 inode > >> rsync error: error in rsync protocol data stream (code 12) at io.c(226) > >> [Receiver=3.1.2.1] > >> rsync_bpc exited with fatal status 12 (3072) (rsync error: error in > rsync > >> protocol data stream (code 12) at io.c(226) [Receiver=3.1.2.1]) > >> Xfer PIDs are now > >> Got fatal error during xfer (No files dumped for share /) > >> Backup aborted (No files dumped for share /) > >> > >> November 24, 2019 7:59 PM, mich...@robinson-west.com wrote: > >> > >> > https://www.ixsystems.com/community/threads/quickstart-guide-for-backuppc-4-in-a-jail-on-freenas.740 > >> > >> My question is, do I need to import the ssh key for root user on my > CentOS > >> 7 box so I can rsync back up the entire system? > >> I'm trying to trigger a backup from my FreeNAS box using BackupPC4 in a > >> jail. > >> _______________________________________________ > >> PLUG mailing list > >> PLUG@pdxlinux.org > >> http://lists.pdxlinux.org/mailman/listinfo/plug > > > > _______________________________________________ > > PLUG mailing list > > PLUG@pdxlinux.org > > http://lists.pdxlinux.org/mailman/listinfo/plug > > Not certain if I did the right thing, but I changed /nonexistent to > /root. Maybe I should change that to /home/backuppc and set the ownership > to backuppc:backuppc and move the .ssh folder over there. Why by default > is the home directory set to /nonexistent in the first place? > > -- Michael Robinson > _______________________________________________ > PLUG mailing list > PLUG@pdxlinux.org > http://lists.pdxlinux.org/mailman/listinfo/plug > _______________________________________________ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
