Re: [rdiff-backup-users] KeyError exception

[Austin Clements]

Quoth myself on Jan 20 at  7:21 pm:
> Quoth Andrew Ferguson on Jan 20 at 11:42 am:
> > I have now changed the writer side of the pipe to flush at more
> > appropriate times. It fixes the testcase for me, and I have committed
> > the change to CVS. I have attached the new backup.py to this email.
> > Simply replace the one in your rdiff_backup directory with this one in
> > order to test the fix.
> 
> Excellent.  I tried it out on the real backup task that originally
> caused this problem and everything worked.

Scratch that.  The initial backup task worked, but the next one failed
with a very similar error involving rorp's, fast processing, and
KeyErrors.  The destination side raised the following exception:

Sending back exception ('home', 'amthrax', '.Xauthority') of type 
exceptions.KeyError: 
  File "/var/lib/python-support/python2.4/rdiff_backup/connection.py", line 
334, in answer_request
    result = apply(eval(request.function_string), argument_list)
  File "/var/lib/python-support/python2.4/rdiff_backup/backup.py", line 236, in 
patch_and_increment
    ITR(diff.index, diff)
  File "/var/lib/python-support/python2.4/rdiff_backup/rorpiter.py", line 280, 
in __call__
    if last_branch.can_fast_process(*args):
  File "/var/lib/python-support/python2.4/rdiff_backup/backup.py", line 513, in 
can_fast_process
    mirror_rorp = self.CCPP.get_mirror_rorp(index)
  File "/var/lib/python-support/python2.4/rdiff_backup/backup.py", line 464, in 
get_mirror_rorp
    except KeyError: return self.get_parent_rorps(index)[1]
  File "/var/lib/python-support/python2.4/rdiff_backup/backup.py", line 446, in 
get_parent_rorps
    raise KeyError(index)

Unfortunately, I've been unable to reproduce this in a controlled
setting so far.  The exception happened very early in the backup
process, in a directory containing only 161 files.  It seems to be
happening only on files that have changed since the last backup,
though that could be coincidental.  I double checked that I've
installed the patch in your last email on both the client and the
server.  Were there any other changes in CVS that might have
interacted with your patch?

The -v8 log is attached (careful, due to buffering, stdout [I think]
all got dumped at the end)

-- 
Austin Clements                                          MIT/'06/CSAIL
address@hidden                         http://web.mit.edu/~amdragon/
       Somewhere in the dream we call reality you will find me,
              searching for the reality we call dreams.

log
Description: Text document