[rdiff-backup-users] KeyError exception again

[Thomas Rehn]

Hi everybody,

until yesterday my backup process with rdiff-backup had worked flawlessly but 
tonight I've experienced a KeyError exception and none of the suggestions 
mentioned in the January thread has helped me. The problem occured with 
Ubuntu 7.10 and rdiff-backup 1.1.14, but a freshly built 1.1.15 shows the 
same error:

Exception '('users', '11042')' raised of class '<type 'exceptions.KeyError'>':
  File "/var/lib/python-support/python2.5/rdiff_backup/Main.py", line 302, in 
error_check_Main
    try: Main(arglist)
  File "/var/lib/python-support/python2.5/rdiff_backup/Main.py", line 322, in 
Main
    take_action(rps)
  File "/var/lib/python-support/python2.5/rdiff_backup/Main.py", line 278, in 
take_action
    elif action == "backup": Backup(rps[0], rps[1])
  File "/var/lib/python-support/python2.5/rdiff_backup/Main.py", line 344, in 
Backup
    backup.Mirror(rpin, rpout)
  File "/var/lib/python-support/python2.5/rdiff_backup/backup.py", line 38, in 
Mirror
    DestS.patch(dest_rpath, source_diffiter)
  File "/var/lib/python-support/python2.5/rdiff_backup/backup.py", line 216, 
in patch
    for diff in rorpiter.FillInIter(source_diffiter, dest_rpath):
  File "/var/lib/python-support/python2.5/rdiff_backup/rorpiter.py", line 177, 
in FillInIter
    for rp in rpiter:
  File "/var/lib/python-support/python2.5/rdiff_backup/backup.py", line 103, 
in get_diffs
    for dest_sig in dest_sigiter:
  File "/var/lib/python-support/python2.5/rdiff_backup/backup.py", line 166, 
in get_sigs
    for src_rorp, dest_rorp in cls.CCPP:
  File "/var/lib/python-support/python2.5/rdiff_backup/backup.py", line 306, 
in next
    source_rorp, dest_rorp = self.iter.next()
  File "/var/lib/python-support/python2.5/rdiff_backup/rorpiter.py", line 103, 
in Collate2Iters
    for relem1 in riter1:
  File "/var/lib/python-support/python2.5/rdiff_backup/rorpiter.py", line 348, 
in next
    del self.cache_dict[self.cache_indicies[0]]

Has anybody got an idea how to tackle or solve this problem?

Best,
 Thomas.