I'd be very grateful for any help. Are the commands logged by backuppc after each "Running:" exactly what it executes?
Is it just one command there split over the lines, or is it 2 sequential? Is it as user backuppc? Or as root? I see it's using 'ssh -l root' which is confusing I figured out why there were 3 login errors. Backuppc was trying to ssh to root and there was no passwordless login for it, so I set it up but immediately got the next problem: /bin/tar: option requires an argument -- 'C' Try 'tar --help' or 'tar --usage' for more information. Tar exited with error 16384 () status restore failed: BackupPC_tarCreate failed And I can see from the command that the value of $shareName+ is meant to appear there - or is it $shareName and the '+' is for tar? > One of my hosts died completely and needs replacing, but in the meantime I > had to restorer some of the files to the localhost where backuppc is > running. > > I used the GUI to set up the restore job, but it immediately failed with > the usual suspect: ssh problems. Since I'd had to solve that problem > before, making sure that the passwordless ssh login between host and > client worked. > > In this case, backuppc is trying to ssh to localhost. > > I went back to the command line and set up ssh so that it can now > passwordless-ssh to itself either as root or as backuppc. I tested both > cases with all combinations: > > sudo -u backuppc ssh [email protected] whoami > sudo -u backuppc ssh backuppc@localhost whoami > sudo -u backuppc ssh backuppc@gondor whoami > > and they all work nicely. > > However this seems to have made backuppc's problems worse, and now I get > the error appearing not just once as before, but 3 times as copied from > the log file below: > > Contents of file > /media/adam/WDPassport2T/backuppc/pc/localhost/RestoreLOG.8.z, modified > 2016-10-07 16:34:22 > > Running: /usr/bin/ssh -q -x -l root localhost env LC_ALL=C /bin/tar -x -p > --numeric-owner --same-owner -v -f - -C > Running: /usr/share/backuppc/bin/BackupPC_tarCreate -h fangorn -n 72 -s > /cygdrive/d/Documents -t -r / -p /home/adam/fangorn/ / > Xfer PIDs are now 25659,25660 > No protocol specified > > (ssh-askpass:25663): Gtk-WARNING **: cannot open display: :0.0 > No protocol specified > > (ssh-askpass:25664): Gtk-WARNING **: cannot open display: :0.0 > No protocol specified > > (ssh-askpass:25665): Gtk-WARNING **: cannot open display: :0.0 > Tar exited with error 65280 () status > tarCreate: Unable to write to output file (Connection reset by peer) > restore failed: BackupPC_tarCreate failed > > So has anyone seen this before? Is there some backuppc-foo that I need to > do, or is ssh just not set up properly still? > > Regards > Adam > > > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, SlashDot.org! http://sdm.link/slashdot > _______________________________________________ > BackupPC-users mailing list > [email protected] > List: https://lists.sourceforge.net/lists/listinfo/backuppc-users > Wiki: http://backuppc.wiki.sourceforge.net > Project: http://backuppc.sourceforge.net/ > ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ BackupPC-users mailing list [email protected] List: https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki: http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
