rdiff-backup-statistics crashed with IOError in open()

Bug #292586 reported by Hew
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
rdiff-backup (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: rdiff-backup

Crash occurred when running rdiff-backup-statistics as a user when rdiff-backup was run as root (so data being analysed has root ownership).

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/rdiff-backup-statistics
InterpreterPath: /usr/bin/python2.5
NonfreeKernelModules: nvidia
Package: rdiff-backup 1.1.16-2
ProcAttrCurrent: unconfined
ProcCmdline: /usr/bin/python /usr/bin/rdiff-backup-statistics /media/terabyte/rdiff-backup/
ProcEnviron:
 SHELL=/bin/bash
 PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_AU.UTF-8
PythonArgs: ['/usr/bin/rdiff-backup-statistics', '/media/terabyte/rdiff-backup/']
SourcePackage: rdiff-backup
Title: rdiff-backup-statistics crashed with IOError in open()
Uname: Linux 2.6.27-7-generic x86_64
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev sambashare video

Tags: apport-crash
Revision history for this message
Hew (hew) wrote :
Changed in rdiff-backup:
importance: Undecided → Medium
Revision history for this message
Andrew Ferguson (adferguson) wrote :

Hew,

Thank you for submitting this bug report. The next version of rdiff-backup-statistics (1.2.3) will now print a more helpful messages when errors like this occur.

Thanks again,
Andrew

Revision history for this message
Hew (hew) wrote :

Thanks for the quick fix. Since you specifically mentioned rdiff-backup-statistics, I should say that the same thing happens when running rdiff-backup as a user on a root backup, so I'm not sure if your fix applies to that as well. I'll test with 1.2.3 when it's released. Thanks again!

Changed in rdiff-backup:
status: New → Triaged
Revision history for this message
Andrew Ferguson (adferguson) wrote :

Hi Hew,

What do you mean by "the same thing happens when running rdiff-backup as a user on a root backup" ? Do you get a traceback, or a human-readable error message?

Obviously, there's nothing that can be done other than printing an error message -- a regular user can't do anything about files owned by root. :-)

Andrew

Revision history for this message
Hew (hew) wrote :

I just meant that I reported the problem occurring with rdiff-backup-statistics, but it also happens with rdiff-backup itself, that's all. It occurs with rdiff-backup when adding an increment as a user, when the backup (and hence the files) were previously done as root. It also occurs when running rdiff-backup-statistics as a user on the backup done as root, as I originally reported. They are very similar issues, if not the same.

I understand that the solution is to print an error message, this is ideal compared to the crash :-)

I have attached the output of each command, which includes the traceback. This is when using 1.1.16-2.

Revision history for this message
Hew (hew) wrote :

Session 1 was run as a user, hence the error only when it reaches session 2.

Revision history for this message
Andrew Ferguson (adferguson) wrote :

Ok, rdiff-backup in CVS will no longer print a traceback if you cannot read the backup destination.

Revision history for this message
Hew (hew) wrote :

Marking Fix Committed since the fix exists in upstream CVS, to be released with rdiff-backup 1.2.3.

Changed in rdiff-backup:
status: Triaged → Fix Committed
Revision history for this message
Hew (hew) wrote :

Marking Fix Released since rdiff-backup 1.2.5-1 is now in Jaunty

Changed in rdiff-backup:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.