bugrdiff-backup - Bugs: bug #23915, rdiff-backup 1.1.5-4 violent crash...

 
 

bug #23915: rdiff-backup 1.1.5-4 violent crash when backup normal ext3 partition over ssh

Submitted by:  Ludolpif <ludolpif>
Submitted on:  Wed 23 Jul 2008 08:40:25 AM UTC  
 
Category: NoneSeverity: 3 - Normal
Item Group: NoneStatus: Invalid
Privacy: PublicAssigned to: None
Open/Closed: Closed

Add a New Comment(Rich Markup)
   

You are not logged in

Please log in, so followups can be emailed to you.

 

Sat 16 Aug 2008 09:12:02 PM UTC, comment #3:

Thanks for the update. Closing bug report.

Andrew Ferguson <owsla>
Project Administrator
Sat 16 Aug 2008 08:30:07 PM UTC, comment #2:

This crash was not a problem from rdiff-backup, and sorry for the post.
The crash disappear when I not use tee to duplicate stdout/err to log, but use '>' and '2>' shell redirection to the log.
Maybe a problem when cron is trying to store plenty of text for an email report... Not yet tested, and it's not for here.
A bit strange...

Ludolpif <ludolpif>
Sat 16 Aug 2008 08:09:13 PM UTC, comment #1:

Yes, I suggest you check the sshd logs or adjust your sshd config to start. This bug is not due to rdiff-backup -- some resource on your system is either exhausted or has timed out. Unfortunately, the rdiff-backup logs are not giving very much helpful information.

Andrew Ferguson <owsla>
Project Administrator
Wed 23 Jul 2008 08:40:25 AM UTC, original submission:

Situation:
2 OVH servers on Debian Etch, with rdiff-backup 1.1.5-4 installed from official deb repo.

A cron task launch a bash script at 5:00 am which start this sequence :
rdiff-backup --remove-older-than ${nb_increments}B ${destinationPath}
rdiff-backup --exclude-other-filesystems --exclude "${DEST_BASE}/*" --preserve-numerical-ids --print-statistics --remote-schema "ssh -p ${destSSHPort} -i ${KEYS} %s rdiff-backup --server --restrict-read-only ${sourcePath}" ${REMOTE_USER}@${servFQDNorIP}::${sourcePath} ${destinationPath}
with variable replacement, of course.
Backup script duplicate rdiff stdout and stderr in a log file by piping to "tee -a".

Each server backup the other. There is multiple partitions to backup and I launch an rdiff per partition, with different cron entry. In one way, it works perfectly (no error for 3 months, daily backup) for every backup.

In the other way, there is on ONE backup that crashes quasi-systematicaly when the script is launched by cron BUT it works systematicaly when the SAME script is launched manually in a root console.

When the crash occurs the entire shell script is destroyed (there is other commands and an echo just after the rdiff-backup call that aren't executed).

I have tried to launch the script by hand (./script.sh in a root console) after adding a '-v9' option in the script, and for the first time, rdiff-backup has crashed when launched manually.

The first error visible in the log is :

Sending back exception [Errno 11] Resource temporarily unavailable of type exceptions.IOError:
File "/var/lib/python-support/python2.4/rdiff_backup/connection.py", line 335, in answer_request
result = apply(eval(request.function_string), argument_list)

There is full log attached.

An additional information : the partition incriminated is local ext3, without other mount points (no NFS and so on). This partition is the biggest to backup, around 25GiB and the backup take more than 45 min in general.

An idea may be : if ssh connexion isn't used for a long period (when build filelist ?) maybe sshd destroy it.

Ludolpif <ludolpif>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach File(s):
   
   
Comment:
   

Attached Files
file #16176:  backup.log.bz2 added by ludolpif (16KiB - application/x-bzip)

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -unavailable- added by owsla (Posted a comment)
  • -unavailable- added by ludolpif (Submitted the item)
  •  

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.

     

    Please enter the title of George Orwell's famous dystopian book (it's a date):

     

     

    Follow 4 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Sat 16 Aug 2008 09:12:02 PM UTCowslaStatusNeed Info=>Invalid
      Open/ClosedOpen=>Closed
    Sat 16 Aug 2008 08:09:13 PM UTCowslaStatusNone=>Need Info
    Wed 23 Jul 2008 08:40:25 AM UTCludolpifAttached File-=>Added backup.log.bz2, #16176

    Back to the top


    Powered by Savane 3.1-cleanup1