Iain Dooley wrote: > hi all, i've been running rdiff-backup for about a year and a half with no > troubles. i use version 1.1.5 on freebsd 6.2R. > > yesterday on two of my systems, i got the error below. other systems are > still running correctly.
> socata# /root/backup.sh > File "/usr/local/lib/python2.4/site-packages/rdiff_backup/Main.py", line > 810, in checkdest_need_check > if not force: curmir_incs[0].conn.regress.check_pids(curmir_incs) > File > "/usr/local/lib/python2.4/site-packages/rdiff_backup/connection.py", line > 448, in __call__ > return apply(self.connection.reval, (self.name,) + args) > File > "/usr/local/lib/python2.4/site-packages/rdiff_backup/connection.py", line > 367, in reval > for arg in args: self._put(arg, req_num) > File > "/usr/local/lib/python2.4/site-packages/rdiff_backup/connection.py", line > 139, in _put > else: self._putobj(obj, req_num) > File > "/usr/local/lib/python2.4/site-packages/rdiff_backup/connection.py", line > 144, in _putobj > self._write("o", pickle.dumps(obj, 1), req_num) > File "/usr/local/lib/python2.4/pickle.py", line 1386, in dumps > Pickler(file, protocol, bin).dump(obj) > File "/usr/local/lib/python2.4/pickle.py", line 231, in dump > self.save(obj) > File "/usr/local/lib/python2.4/pickle.py", line 293, in save > f(self, obj) # Call unbound method with explicit self > File "/usr/local/lib/python2.4/pickle.py", line 614, in save_list > self._batch_appends(iter(obj)) > File "/usr/local/lib/python2.4/pickle.py", line 647, in _batch_appends > save(x) > File "/usr/local/lib/python2.4/pickle.py", line 293, in save > f(self, obj) # Call unbound method with explicit self > File "/usr/local/lib/python2.4/pickle.py", line 737, in save_inst > stuff = getstate() > File "/usr/local/lib/python2.4/site-packages/rdiff_backup/rpath.py", > line 754, in __getstate__ > assert self.conn is Globals.local_connection Iain, The bug you are seeing was fixed in version 1.1.12. Unfortunately, the bug was in the rdiff-backup network protocol, which required that I break the protocol in 1.1.12 in order to fix it. Since you are using rdiff-backup on several computers, you would need to upgrade rdiff-backup to version 1.1.14 on ALL of your computers if you wanted to use the fixed version on one of them. HOWEVER, there is a workaround: You can add the --force option to rdiff-backup, and it will skip the code pathway that leads to this bug. Best, Andrew -- Andrew Ferguson - [EMAIL PROTECTED] _______________________________________________ rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki