Hide Forgot
Description of problem: Exception: -- Current session's log messages -- Feb 03 01:46:35 :: INFO : fwbackups administrator started Feb 03 01:46:53 :: INFO : Starting automatic backup operation of set `kravica.no-ip.org..home' Feb 03 01:47:02 :: INFO : Using tar.bz2: Must backup all paths at once - Progress notification will be disabled. Feb 03 10:58:33 :: WARNING : There was an error while performing the backup! Feb 03 10:58:33 :: ERROR : Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/fwbackups/operations/backup.py", line 713, in start self.deleteListFiles(pkgListfiles) File "/usr/lib/python2.6/site-packages/fwbackups/operations/backup.py", line 180, in deleteListFiles os.remove(file) OSError: [Errno 2] No such file or directory: '<fdopen>' Feb 03 10:58:33 :: INFO : Canceling the current operation! Feb 03 10:58:33 :: INFO : Finished automatic backup operation of set 'kravica.no-ip.org..home' Version-Release number of selected component (if applicable): 1.43.4 How reproducible: I just ran the normal backup Steps to Reproduce: Actual results: Exception thrown. Expected results: No exception thrown. Additional info: Backup config available upon request.
Are you running this backup as root?
Yes, I am.
Hi! I do get the same error with version 1.43.4 on Fedora 14, as root and as normal user. Since I'm trying to bachup an older set (created with fwbackups perhaps two years ago) I suspected that existing Backup Set as the reason for the error. I created a new (more or less similar) Backup Set with current fwbackups GUI. That one works without problems. Comparing the very few differences in the .conf files I found the exact reason: [Options] DiskInfoToFile = 1 lets the crash occur, while DiskInfoToFile = 0 does work. Regards Christian
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
I tried the same with Fedora 15 (fwbackups-1.43.4-2) now. The crash seems to be no longer reproducable for me, even with forced "DiskInfoToFile = 1" Christian
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.