[rdiff-backup-users] Truncated header error when rdiff-backup to remote host

[iCy-fLaME]

I have two computers, both on FC6 with the following package installed:

librsync-0.9.7-10.fc6
pylibacl-0.2.1-6.fc6
pyxattr-0.2.1-4.fc6
rdiff-backup-1.0.5-2.fc6

I tried google the issue a bit, it seems a similar issue has been
reported before:
http://lists.gnu.org/archive/html/rdiff-backup-users/2006-07/msg00043.html
but I have yet found a solution to the problem.


Everything works fine if I do:
$ rdiff-backup ~/local_data_dir ~/local_backup_dir


But when I try to backup from local machine to the remote one with:
$ rdiff-backup ~/local_data_dir address@hidden::/remote_backup_dir


I get the following error message:

Traceback (most recent call last): File "/usr/bin/rdiff-backup", line
23, in ? rdiff_backup.Main.Main(sys.argv[1:]) File
"/usr/lib/python2.4/site-packages/rdiff_backup/Main.py", line 285, in
Main take_action(rps) File
"/usr/lib/python2.4/site-packages/rdiff_backup/Main.py", line 255, in
take_action elif action == "backup": Backup(rps[0], rps[1]) File
"/usr/lib/python2.4/site-packages/rdiff_backup/Main.py", line 308, in
Backup backup.Mirror(rpin, rpout) File
"/usr/lib/python2.4/site-packages/rdiff_backup/backup.py", line 38, in
Mirror DestS.patch(dest_rpath, source_diffiter) File
"/usr/lib/python2.4/site-packages/rdiff_backup/connection.py", line
445, in __call__ return apply(self.connection.reval, (self.name,) +
args) File "/usr/lib/python2.4/site-packages/rdiff_backup/connection.py",
line 367, in reval if isinstance(result, Exception): raise result
IOError: [Errno 1] Operation not permitted Traceback (most recent call
last): File "/usr/bin/rdiff-backup", line 23, in ?
rdiff_backup.Main.Main(sys.argv[1:]) File
"/usr/lib/python2.4/site-packages/rdiff_backup/Main.py", line 285, in
Main take_action(rps) File
"/usr/lib/python2.4/site-packages/rdiff_backup/Main.py", line 253, in
take_action connection.PipeConnection(sys.stdin, sys.stdout).Server()
File "/usr/lib/python2.4/site-packages/rdiff_backup/connection.py",
line 352, in Server self.get_response(-1) File
"/usr/lib/python2.4/site-packages/rdiff_backup/connection.py", line
314, in get_response try: req_num, object = self._get() File
"/usr/lib/python2.4/site-packages/rdiff_backup/connection.py", line
230, in _get raise ConnectionReadError("Truncated header string
(problem " rdiff_backup.connection.ConnectionReadError: Truncated
header string (problem probably originated remotely) Exception
exceptions.TypeError: "'NoneType' object is not callable" in <bound
method GzipFile.__del__ of <gzip open file
'/remote_backup_dir/rdiff-backup-data/extended_attributes.2007-06-26T09:54:57+01:00.snapshot.gz',
mode 'wb' at 0xb7cba218 -0x4833e774>> ignored Exception
exceptions.TypeError: "'NoneType' object is not callable" in <bound
method GzipFile.__del__ of <gzip open file
'/remote_backup_dir/rdiff-backup-data/file_statistics.2007-06-26T09:54:57+01:00.data.gz',
mode 'wb' at 0xb7d1f0b0 -0x4833e954>> ignored Exception
exceptions.TypeError: "'NoneType' object is not callable" in <bound
method GzipFile.__del__ of <gzip open file
'/remote_backup_dir/rdiff-backup-data/error_log.2007-06-26T09:54:57+01:00.data.gz',
mode 'wb' at 0xb7d1f068 -0x48340f54>> ignored Exception
exceptions.TypeError: "'NoneType' object is not callable" in <bound
method GzipFile.__del__ of <gzip open file
'/remote_backup_dir/rdiff-backup-data/mirror_metadata.2007-06-26T09:54:57+01:00.snapshot.gz',
mode 'wb' at 0xb7cba1d0 -0x4833e814>> ignored



If I run rdiff-backup again:
$ rdiff-backup ~/local_data_dir address@hidden::/remote_backup_dir

The following message will appear:

Fatal Error: Bad rdiff-backup-data dir on destination side The
rdiff-backup data directory /remote_backup_dir/rdiff-backup-data
exists, but we cannot find a valid current_mirror marker. You can
avoid this message by removing the rdiff-backup-data directory;
however any data in it will be lost. Probably this error was caused
because the first rdiff-backup session into a new directory failed. If
this is the case it is safe to delete the rdiff-backup-data directory
because there is no important information in it.



I have tried to initiate the backup from the remote host, but doesnt
seems to make any difference, I still get a similar error message.

Any helps and suggestions are greatly appreciated.