Okay so here is the full error log. full backup started for directory /cygdrive/g/ptree (baseline backup #46) Running: /usr/bin/ssh -o ServerAliveInterval=300 -p 222 -q -x -l Administrator [DOMAIN] /usr/bin/rsync --server --sender --numeric-ids --perms --owner --group -D --links --hard-links --times --block-size=2048 --recursive --checksum-seed=32761 --rsh=\\\'ssh\\\ -p222\\\' --ignore-times . /cygdrive/g/ptree/ Xfer PIDs are now 29452 Got remote protocol 30 Negotiated protocol version 28 Checksum caching enabled (checksumSeed = 32761) Remote[1]: rsync: change_dir "/cygdrive/g/ptree" failed: No such file or directory (2) Xfer PIDs are now 29452,29462 Read EOF: Tried again: got 0 bytes Can't write 4 bytes to socket Child is aborting Done: 0 files, 0 bytes Got fatal error during xfer (aborted by signal=PIPE) Backup aborted by user signal Not saving this as a partial backup since it has fewer files than the prior one (got 0 and 0 files versus 0)
As far as the command goes I'm not sure why the -rsh is there. That's just what backuppc is doing on the localhost and was set that way prior to me even getting here and working on this server. It had been working for a long time that way. Even so I removed that option and still got the same error as the one above. The logs say nothing about a "protocol version mismatch". It's also not a key issue problem as I'm able to log right in as root from the backuppc user without any problems. ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- "On Fri, Oct 24, 2014 at 12:35 PM, HAL9000 <backuppc-forum < at > backupcentral.com> wrote: "Does anyone here know how to correct this? yes, simply not do it. What on earth are you trying to do? You have no apparent problem, except that you don't speak the rsync protocol (which is not really a problem - you don't have to). " lol. But there is too an issue. This is the command backuppc is trying to tun to do the backup. If your backuppc xfer logs say something about protocol version mismatch, it is almost always because something else ran first at the remote end and sent some output. The normal rsync binary can deal with that, but the perl implementation in backuppc can't. However if you only saw that error when you started rsync at one end only with your own ssh command it is probably what you should expect. " /usr/bin/ssh -o ServerAliveInterval=300 -p 222 -q -x -l Administrator [DOMAIN] /usr/bin/rsync --server --sender --numeric-ids --perms --owner --group -D --links --hard-links --times --block-size=2048 --recursive --checksum-seed=32761 --rsh=\\\'ssh\\\ -p222\\\' --ignore-times . /cygdrive/g/ptree/ " I don't understand why you are passing the --rsh comand option to the remote while you are already remotely running it. My ubuntu server won't run the command while a CentOS server backing up the same device will. That sounds more like an error in ssh key setup. " +---------------------------------------------------------------------- |This was sent by [email protected] via Backup Central. |Forward SPAM to [email protected]. +---------------------------------------------------------------------- ------------------------------------------------------------------------------ _______________________________________________ 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/
