** Description changed:
Binary package hint: sbackup
A month ago simple-backup stopped working for me.
Now, nothing happens on schedule. If I initiate a manual backup, the process
is launched but becomes defunct after a few seconds; no backup.
If I run
sudo sbackup
from the command line, I get:
I: Securing permissions at: ssh://user:[EMAIL
PROTECTED]:/home/cpbl/private/backup/2006-11-13_14.00.47.563916.cpbl-laptop.inc
Traceback (most recent call last):
File "/usr/sbin/sbackupd", line 404, in ?
upgrader.upgrade_target( target, purge )
File "/usr/sbin/upgrade_backups.py", line 60, in upgrade_target
self.upgrade_tdir( target+"/"+adir )
File "/usr/sbin/upgrade_backups.py", line 78, in upgrade_tdir
v = self.openfile( tdir + "/ver" )
File "/usr/sbin/upgrade_backups.py", line 307, in openfile
return gnomevfs.open( uri, 1 )
gnomevfs.NotFoundError: File not found
despite the fact that in the setup GUI, when I click on TEST for the
remote target, I get a green light.
Ah -- the problem is that the directory mentioned in the error is empty.
I do not know why it is empty -- a failed backup in the past? But this
should NOT cause sbackup to crash.
That is, when an old dated backup directory is empty, it should be
deleted rather than crashing sbackup.
Secondly, there should be some report when sbackup crashes! An email must go
to the admin, or something.
I get no word of an error unless I run sbackup by hand.
-
- (((Am I the only one filing bugs on this sbackup thing? I consider it a
- most basic desktop system feature. What else could I be using?)))
--
Empty past backup directory causes simple-backup to fail silently
https://launchpad.net/bugs/78349
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
