[rdiff-backup-users] Corrupted MAC on input

[Keith Edmunds]

I'm backing up three directory trees from one system to another. Both
systems are Linux, both running rdiff-backup 0.12.4. This is the first
run of the backup, although I've repeated it a few times, both to the
partially-completed target directory and to an empty target. One source
directory consistently gives the same error; the other two directories
backup just fine. The error is:

rdiff-backup --exclude **.iso* /home backup::/backups/xxxxxx/xxxxx/home
Received disconnect from xxx.xxx.xxx.xxx: 2: Corrupted MAC on input.
Traceback (most recent call last):
  File "/usr/bin/rdiff-backup", line 24, in ?
    rdiff_backup.Main.Main(sys.argv[1:])
  File "/usr/lib/python2.2/site-packages/rdiff_backup/Main.py", line
246, in Main    take_action(rps)
  File "/usr/lib/python2.2/site-packages/rdiff_backup/Main.py", line
219, in take_action    elif action == "backup": Backup(rps[0], rps[1])
  File "/usr/lib/python2.2/site-packages/rdiff_backup/Main.py", line
263, in Backup    backup.Mirror(rpin, rpout)
  File "/usr/lib/python2.2/site-packages/rdiff_backup/backup.py", line
36, in Mirror    DestS.patch(dest_rpath, source_diffiter)
  File "/usr/lib/python2.2/site-packages/rdiff_backup/connection.py",
line 424, in __call__    return apply(self.connection.reval,
(self.name,) + args)  File
"/usr/lib/python2.2/site-packages/rdiff_backup/connection.py", line 344,
in reval    result = self.get_response(req_num)
  File "/usr/lib/python2.2/site-packages/rdiff_backup/connection.py",
line 293, in get_response    try: req_num, object = self._get()
  File "/usr/lib/python2.2/site-packages/rdiff_backup/connection.py",
line 216, in _get    raise ConnectionReadError("Truncated header string
(problem " rdiff_backup.connection.ConnectionReadError: Truncated header
string (problem probably originated remotely)

I'm surprised by the "Corrupted MAC on input" as that seems to imply a
hardware or network configuration problem, but the other two directories
on this machine back up just fine.

Any clues?

Thanks,
Keith