** Changed in: sbackup (Ubuntu)
Status: Fix Committed = Fix Released
--
gnomevfs.NotFoundError even when the test works in remote backup site
https://bugs.launchpad.net/bugs/67814
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
Hi,
I guess sbackup error report is confusing and I am aware of that. I
think your problem is really about connection limitation. but actually
Sbackud (in simple-backup-config ) report and error about writability
for any problem that occurs and prevent it to write (or even access the
target ).
I use version sbackup_0.10.4~beta12_all.deb on feisty, but it doesn't
work at all:
first try:
[EMAIL PROTECTED]:~$ sudo sbackupd
Traceback (most recent call last):
File /usr/sbin/sbackupd, line 593, in module
do_backup_finish()
File /usr/sbin/sbackupd, line 280, in do_backup_finish
HI,
apparently, gnomevfs couldn't login to your web site , I suspect that
the ftp is configured to just get 1 connection at a time and that
gnomevfs is trying to open another one.
do you know if there is a user connections limitation on your ftp ?
--
gnomevfs.NotFoundError even when the test
i tried to connect via browser and gftp and nautilus... and this is what
i got:
530 Sorry, the maximum number of clients (2) from your host are already
connected.
so - this is the problem? i started sbackup again and got following
error:
[EMAIL PROTECTED]:~$ sudo sbackupd
E: Target directory
Hi, just wanna say, with the last .deb, sbackup_0.10.4~beta12_all.deb,
it works perfectly for me. Using ssh (with pass) remote backups. Thanks
a lot! :)
--
gnomevfs.NotFoundError even when the test works in remote backup site
https://bugs.launchpad.net/bugs/67814
You received this bug
Changing status to Fix committed as it's fixed upstream.
Please feel free to reopen if there is any problem concerning that bug.
** Changed in: sbackup (Ubuntu)
Status: In Progress = Fix Committed
--
gnomevfs.NotFoundError even when the test works in remote backup site
Hi
Backup works! :-)
Just before running the beta11 version I noticed that the ver file on
the server was empty. I did some cleaning up (deleted old backups) and
now it works. I've tried both full and incremental backup.
Thank you very much!
Not sure about restore tho'...! I get the following
OOhh, That's scary !
You're right :-/
The good thing is the problem comes from Restore (but the backup is
valid )
As for the cleaning up you have done , the beta 11 new code would have,
somehow, done it . Itwouldn't have deleted the whole snapshot dir but
the ver file so that next time it
Fixed .
Could you please test it ?
** Attachment added: sbackup_0.10.4~beta12_all.deb
http://librarian.launchpad.net/7839957/sbackup_0.10.4%7Ebeta12_all.deb
--
gnomevfs.NotFoundError even when the test works in remote backup site
https://bugs.launchpad.net/bugs/67814
You received this bug
Restore works now!
A couple of things could make it a bit more pretty.
1) When I restored an empty dialog box appeared
2) When I chose to restore to an alternative destination (Restore As...) the
console output showed the original path. Thought for a moment I had overwritten
some files.
HI,
Please fill another bug in for those .
You can add in it that Simple-restore-gnome is very slow when restoring too .
Idea for the bug title : Request for simple-restore-gnome improvement .
Thank you
--
gnomevfs.NotFoundError even when the test works in remote backup site
Hi,
Can I set this one as fix committed ?
--
gnomevfs.NotFoundError even when the test works in remote backup site
https://bugs.launchpad.net/bugs/67814
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Hi
I'm trying to make an incremental backup of /home to a remote ftp site
and I experienced the same errors as described above.
I've just tested 0.10.4-beta10 and get the following error:
[EMAIL PROTECTED]:~$ sudo simple-backup-config
Traceback (most recent call last):
File
should be fixed.
Could you please test this ?
It should still print the error for Info.
** Attachment added: sbackup_0.10.4~beta11_all.deb
http://librarian.launchpad.net/7834733/sbackup_0.10.4%7Ebeta11_all.deb
--
gnomevfs.NotFoundError even when the test works in remote backup site
The post above seems to describe a problem that happened repeatably over a
wireless connection but not so far wired. I don't know why, but maybe the
connection was intermittent and sbackup does not catch breaks in the
connection.
So I don't claim this is a problem that has been introduced
** Attachment added: sbackup_0.10.4~beta10_all.deb
http://librarian.launchpad.net/7730478/sbackup_0.10.4%7Ebeta10_all.deb
--
gnomevfs.NotFoundError even when the test works in remote backup site
https://bugs.launchpad.net/bugs/67814
You received this bug notification because you are a member
** Attachment removed: sbackup_0.10.4~beta10_all.deb
http://librarian.launchpad.net/7730478/sbackup_0.10.4%7Ebeta10_all.deb
** Attachment added: sbackup_0.10.4~beta10_all.deb
http://librarian.launchpad.net/7731001/sbackup_0.10.4%7Ebeta10_all.deb
--
gnomevfs.NotFoundError even when the test
The post above seems to describe a problem that happened repeatably over a
wireless connection but not so far wired. I don't know why, but maybe the
connection was intermittent and sbackup does not catch breaks in the connection.
So I don't claim this is a problem that has been introduced in
Fixed.
Thank you for your help in bug report. :-)
** Attachment added: sbackup_0.10.4beta9_all.deb
http://librarian.launchpad.net/7614886/sbackup_0.10.4beta9_all.deb
--
gnomevfs.NotFoundError even when the test works in remote backup site
https://bugs.launchpad.net/bugs/67814
You received
WARNING :
ssh://cpb:@gcra-ubc.com:/home/cpbl/private/backup/2007-04-12_10.00.27.151010.cpbl-laptop.ful/ver
doesn't exist ! Deleting the incomplete snapshot
I: Upgrading to v1.4:
ssh://cpb:@gcra-ubc.com:/home/cpbl/private/backup/2007-04-11_10.00.29.252716.cpbl-laptop.inc
WARNING :
This may be a separate bug, but it's worse... [again, I wonder, am I the
only one trying to use this as my remote backup solution?!]:
when I run sbackup from the command line, it SILENTLY fails to finish the
backup. That is, an incomplete .tgz file is written.
After only a couple of minutes, it
If I already sent this privately, it didn't make it to the launchpad.
This version still doesn't work for me over remote backup site:
..remote site:/._10.00.27.151010.cpbl-laptop.ful/ver doesn't exist ! Deleting
the incomplete snapshot
Traceback (most recent call last):
File
sudo sbackupd
ERROR : Unexpected Exception : gnomevfs.Handle.read() takes exactly 1 argument
(0 given)
ERROR : Unexpected Exception : gnomevfs.Handle.read() takes exactly 1 argument
(0 given)
ERROR : Unexpected Exception : gnomevfs.Handle.read() takes exactly 1 argument
(0 given)
ERROR :
Nice :-D
That is what I was thinking . All my tests were made locally , so I
didn't use the right function for remote backups . I'll work on that
one .
Thank you
Question : is this backup a good one ? Do you want to keep it ?
2007-04-10_10.00.19.825976.cpbl-laptop.inc
cause, since there is no
Fixed version ( tested over ssh :-) )
Format: 1.7
Date: Thu, 10 May 2007 22:01:42 +0200
Source: sbackup
Binary: sbackup
Architecture: source all
Version: 0.10.4beta8
Distribution: feisty
Urgency: low
Maintainer: Aigars Mahinovs [EMAIL PROTECTED]
Changed-By: Ouattara Oumar Aziz (alias wattazoum)
S0 far so good. Sbackup ran last night without having to move any old
backups. Of course only time will tell as it usually takes a month of
backups before it stops working, but backing up to a folder full of old
ones is a good sign.
--
gnomevfs.NotFoundError even when the test works in remote
Thanks, Ouattara!!
It's great that someone is finally able to help this poor piece of software.
But how do I know that your new version is not stealing my passwords (which,
btw, for the ssh feature are stored in text format in sbackup and even EMAILED
in open text to the root user (which then
Okay, that was a stupid question -- sbackup is written in Python.
However, I ran it and get the following error now: this is new to me.:
sudo sbackupd
Traceback (most recent call last):
File /usr/sbin/sbackupd, line 426, in module
upgrader.upgrade_target( target, purge )
File
hello,
well, actually I have never used sbackup for backups requiring password . If
it just keeps your password in clear, this might be another bug to fill up.
As for the code, since sbackup is open source you can see it there :
http://sbackup.svn.sourceforge.net/viewvc/sbackup/
(you've
Here is a mod with the second point solved (so that I can have more
information on the first one ) . could you please retry with this one ?
** Attachment added: sbackup_0.10.4beta7_all.deb
http://librarian.launchpad.net/7595163/sbackup_0.10.4beta7_all.deb
--
gnomevfs.NotFoundError even when
Hi,
please try with the file given there :
https://bugs.launchpad.net/ubuntu/+source/sbackup/+bug/82992/comments/4
I believe we have fix the problem. It would be nice if you could confirm that
it's fixed (or not :-) ).
so that I'll work on that one.
--
gnomevfs.NotFoundError even when the
My bad, the bug wasn't fixed.
To reproduce, just erase the ver file from one snapshot. and launch
simple-restore-gnome.
What has been done was to pass the error silently in upgrade_backup.py
The fix will be to erase every snapshot that doesn't contain the ver
file . The existance of this file
** Changed in: sbackup (Ubuntu)
Status: In Progress = Fix Committed
--
gnomevfs.NotFoundError even when the test works in remote backup site
https://bugs.launchpad.net/bugs/67814
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
here is the version fixed
** Attachment added: sbackup_0.10.4beta4_all.deb
http://librarian.launchpad.net/7586096/sbackup_0.10.4beta4_all.deb
--
gnomevfs.NotFoundError even when the test works in remote backup site
https://bugs.launchpad.net/bugs/67814
You received this bug notification
I also see the same problem:
[EMAIL PROTECTED]:~$ sudo /usr/sbin/sbackupd
Password:
I: Securing permissions at: ssh://jamesbond:[EMAIL
PROTECTED]/home/jamesbond/backup/2007-04-10_13.30.09.934802.jamesbond-laptop.ful
Traceback (most recent call last):
File /usr/sbin/sbackupd, line 404, in
** Changed in: sbackup (Ubuntu)
Importance: Undecided = Medium
--
gnomevfs.NotFoundError even when the test works in remote backup site
https://launchpad.net/bugs/67814
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Changed in: sbackup (Ubuntu)
Status: Unconfirmed = Confirmed
--
gnomevfs.NotFoundError even when the test works in remote backup site
https://launchpad.net/bugs/67814
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I have the identical problem. It broke for me in Dec 06. Fiesty's
0.10.3-0.1 version has the same problem. Version 0.9-1 has a different,
likely similar problem. 0.8-1 seems to be working ok, possibly because
it does not need to do the work that upgrade_backups.py is performing.
Haven't looked
39 matches
Mail list logo
