On Thu, Nov 20, 2014 at 12:08 PM, tschmid4 <tschmid4 AT utk DOT edu> wrote:
>
> Correct, It's a question, here's another:
> You are correct, the configuration was backing up a dir that was not there.
> However, after removing the entry, it returns the same error.
> What else would cause 'unable to read 4 bytes?'
>

Unable to read 4 bytes is not the same error as:
 "Remote[1]: rsync: change_dir "/systems" failed: No such file or directory (2)"

Unable to read 4 bytes almost always means that your ssh keys are not
correct and you aren't starting the remote rsync at all.   And since
that was working before, it shouldn't happen unless you changed more
than the target directory.

-- 
   Les Mikesell
     lesmikesell AT gmail DOT com

------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/