Re: [rdiff-backup-users] Error

[Dominic Raferd]

prateekmoturi wrote:
> Hi i am getting the following error messages when i am trying to backup.
> I am using the rdiff-backup 1.2.8.
> Can anyone please help me to find the solution for the following error...
>
>
> Traceback (most recent call last):
>   File "/usr/bin/rdiff-backup", line 30, in ?
>     rdiff_backup.Main.error_check_Main(sys.argv[1:])
>   File "/usr/lib/python2.4/site-packages/rdiff_backup/Main.py", line 304, in 
> error_check_Main
>     try: Main(arglist)
>   File "/usr/lib/python2.4/site-packages/rdiff_backup/Main.py", line 324, in 
> Main
>     take_action(rps)
>   File "/usr/lib/python2.4/site-packages/rdiff_backup/Main.py", line 280, in 
> take_action
>     elif action == "backup": Backup(rps[0], rps[1])
>   File "/usr/lib/python2.4/site-packages/rdiff_backup/Main.py", line 337, in 
> Backup
>     backup_final_init(rpout)
>   File "/usr/lib/python2.4/site-packages/rdiff_backup/Main.py", line 501, in 
> backup_final_init
>     checkdest_if_necessary(rpout)
>   File "/usr/lib/python2.4/site-packages/rdiff_backup/Main.py", line 920, in 
> checkdest_if_necessary
>     dest_rp.conn.regress.Regress(dest_rp)
>   File "/usr/lib/python2.4/site-packages/rdiff_backup/regress.py", line 71, in 
> Regress
>     for rf in iterate_meta_rfs(mirror_rp, inc_rpath): ITR(rf.index, rf)
>   File "/usr/lib/python2.4/site-packages/rdiff_backup/regress.py", line 197, in 
> iterate_meta_rfs
>     for raw_rf, metadata_rorp in collated:
>   File "/usr/lib/python2.4/site-packages/rdiff_backup/rorpiter.py", line 100, 
> in Collate2Iters
>     try: relem2 = riter2.next()
>   File "/usr/lib/python2.4/site-packages/rdiff_backup/metadata.py", line 274, 
> in iterate
>     for record in self.iterate_records():
>   File "/usr/lib/python2.4/site-packages/rdiff_backup/metadata.py", line 283, 
> in iterate_records
>     next_pos = self.get_next_pos()
>   File "/usr/lib/python2.4/site-packages/rdiff_backup/metadata.py", line 266, 
> in get_next_pos
>     newbuf = self.fileobj.read(self.blocksize)
>   File "/usr/lib/python2.4/gzip.py", line 225, in read
>     self._read(readsize)
>   File "/usr/lib/python2.4/gzip.py", line 273, in _read
>     self._read_eof()
>   File "/usr/lib/python2.4/gzip.py", line 309, in _read_eof
>     raise IOError, "CRC check failed"
> IOError: CRC check failed
>   
This is what Andrew Ferguson (maintainer of rdiff-backup) wrote in 
response to a similar problem a couple of years ago:

"Given this error, and especially since one client is failing and three
are working, I would be suspicious of the failing client's hardware
(probably RAM or hard disk). Are all of your clients backing up to one
server? What is the setup here?

CRC is the Cyclic Redundancy Check and is a way of checking the
integrity of a data stream.

Were there any other messages logged from rdiff-backup? Perhaps in the
rdiff-backup-data/error_log files?"

And here is what someone else wrote about this error:

"This problem has come up many times on the mailing list, and so far there 
is not a good fix for it... usually it appears when one of the .gz files was 
incomplete.  Try this:

find rdiff-backup-data/ -name '*.gz" | while read a; do
       echo -n "$a:"
       gzip --test "$a"
done

This will tell you which files are bad.  In our case, we had a problem 
with the mirror_metadata files.  Search the archive for specifics, but 
basically I copied a good mirror_metadata over the bad mirror_metadata and 
crossed my fingers.  It worked for us, though I do not know the 
implications here.  After doing this surgery, you might try a restore of 
the past few backup dates and make sure it is successful.  Worst case, you 
rm-rf rdiff-backup-data, though you will loose your increments."

HTH, Dominic