[Nssbackup-team] [Bug 577296] Re: Crash, with "%d format: a number is required, not str"
A fix for this problem is already committed to the 0.2 series branch and will be included in the next release (the final 0.2.0 release) in short time. The error is triggered if not enough free disk space is available for the current backup. In such cases an error message is printed, and this message is errorneous. Due to this fact, the problem vanished for you after you've deleted old backups. -- Crash, with "%d format: a number is required, not str" https://bugs.launchpad.net/bugs/577296 You received this bug notification because you are a member of NSsbackup team, which is subscribed to NSsbackup. ___ Mailing list: https://launchpad.net/~nssbackup-team Post to : nssbackup-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~nssbackup-team More help : https://help.launchpad.net/ListHelp
[Nssbackup-team] [Bug 577296] Re: Crash, with "%d format: a number is required, not str"
Update from me: I just deleted the old sbackup's archives from my stick and ran nssbackup to make backups from scratch and everything worked well. No more "TypeError: %d format: a number is required, not str" for me so far. I'll keep you posted if there are any more errors in this regard when my auto-backup is done tomorrow evening. Frank -- Crash, with "%d format: a number is required, not str" https://bugs.launchpad.net/bugs/577296 You received this bug notification because you are a member of NSsbackup team, which is subscribed to NSsbackup. ___ Mailing list: https://launchpad.net/~nssbackup-team Post to : nssbackup-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~nssbackup-team More help : https://help.launchpad.net/ListHelp
[Nssbackup-team] [Bug 550261] Re: After upgrade to Lucid backups cannot be started through the GUI
Jean-Peer, I'm not sure if it could be help, but in http://ubuntu-virginia.ubuntuforums.org/showthread.php?p=9287012 we have a "provisional" solution. it work from the terminal ~$ sudo sbackupd I have tested in lucid 64 bits, and works nice -- After upgrade to Lucid backups cannot be started through the GUI https://bugs.launchpad.net/bugs/550261 You received this bug notification because you are a member of NSsbackup team, which is subscribed to sbackup in ubuntu. ___ Mailing list: https://launchpad.net/~nssbackup-team Post to : nssbackup-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~nssbackup-team More help : https://help.launchpad.net/ListHelp
[Nssbackup-team] [Bug 577296] Re: Crash, with "%d format: a number is required, not str"
Jean-Peer, the same happened to me just now, too ("TypeError: %d format:
a number is required, not str"). Do you want/need the output from my
nssbackup.log as well?
Another "problem" (not a real problem for me, though) is, that I wanted
nssbackup to make additional backups to existing ones already made with
sbackup. I get a warning which reads:
2010-05-17 21:45:30,190 - WARNING in BackupManager.makeBackup(308):
There are snapshots with old snapshot format. Please upgrade them if you
want to use them.
So, how to upgrade them? It's not a problem in my case to start the
backups from scratch with nssbackup. I just noticed the warning and
wondered how to "upgrade" existing ones. There may be other users who
can't simply backup from scratch, so they may get into trouble when
switching from sbackup to nssbackup. Btw, the backup did not perform due
to having not enough space left on my backup stick (8 GB stick) as
nssbackup wanted to start a full backup which obviously is related to
the old archive format already on the stick.
Thanks, Frank
--
Crash, with "%d format: a number is required, not str"
https://bugs.launchpad.net/bugs/577296
You received this bug notification because you are a member of NSsbackup
team, which is subscribed to NSsbackup.
___
Mailing list: https://launchpad.net/~nssbackup-team
Post to : nssbackup-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~nssbackup-team
More help : https://help.launchpad.net/ListHelp
[Nssbackup-team] [Bug 550261] Re: After upgrade to Lucid backups cannot be started through the GUI
** Changed in: sbackup Assignee: Jean-Peer Lorenz (peer.loz) => (unassigned) -- After upgrade to Lucid backups cannot be started through the GUI https://bugs.launchpad.net/bugs/550261 You received this bug notification because you are a member of NSsbackup team, which is subscribed to sbackup in ubuntu. ___ Mailing list: https://launchpad.net/~nssbackup-team Post to : nssbackup-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~nssbackup-team More help : https://help.launchpad.net/ListHelp
[Nssbackup-team] [Bug 526544] Re: Bug "préc isement à..."
I confirm there is still a problem when defining a custom cron expression in 0.2-RC9. I've committed a fix for this. ** Changed in: nssbackup Status: Incomplete => Fix Committed ** Changed in: nssbackup/0.2 Status: Incomplete => Fix Committed -- Bug "précisement à..." https://bugs.launchpad.net/bugs/526544 You received this bug notification because you are a member of NSsbackup team, which is subscribed to NSsbackup. ___ Mailing list: https://launchpad.net/~nssbackup-team Post to : nssbackup-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~nssbackup-team More help : https://help.launchpad.net/ListHelp
[Nssbackup-team] [Bug 577112] Re: nssbackup crashes with: GtkWarning: could not open display warnings.warn(str(e), _gtk.Warning)
[log] file = /var/log/nssbackup.log level = 20 [places] prefix = /usr [schedule] [dirconfig] /media/ = 0 /var/cache/ = 0 /var/ = 1 /home/ = 1 /var/spool/ = 0 /var/tmp/ = 0 /usr/local/ = 1 /etc/ = 1 [general] splitsize = 0 target = ftp://:@domain.local/array1/backup format = none mountdir = /mnt/nssbackup purge = 60 maxincrement = 30 lockfile = /var/lock/nssbackup.lock [report] from = NSsbackup Daemon [exclude] regex = /home/[^/]+?/\.thumbnails/,/home/x/Mail/,/home/[^/]+?/\.local/share/Trash/,/home/[^/]+?/\..+/[cC]ache,/home/[^/]+?/\.gvfs/,/home/[^/]+?/\.m2/,/home/[^/]+?/Private/ I disabled scheduling for now. -- nssbackup crashes with: GtkWarning: could not open display warnings.warn(str(e), _gtk.Warning) https://bugs.launchpad.net/bugs/577112 You received this bug notification because you are a member of NSsbackup team, which is subscribed to NSsbackup. ___ Mailing list: https://launchpad.net/~nssbackup-team Post to : nssbackup-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~nssbackup-team More help : https://help.launchpad.net/ListHelp
[Nssbackup-team] [Bug 577112] Re: nssbackup crashes with: GtkWarning: could not open display warnings.warn(str(e), _gtk.Warning)
> Does this happen if you run as root or user? I run it as root user > Would you post your configuration? I will attach it > Backups manually triggered or scheduled? Scheduled hourly. > Is something special on your software setup (libraries deinstalled...)? No. > Do you have your root account enabled? No. > Are you logged in while the backup starts? Yes. > Do manuell backups (as user/as root) work for you? From terminal/from GUI? > Can you post a full log of the issue with debug loglevel enabled? Comes later. -- nssbackup crashes with: GtkWarning: could not open display warnings.warn(str(e), _gtk.Warning) https://bugs.launchpad.net/bugs/577112 You received this bug notification because you are a member of NSsbackup team, which is subscribed to NSsbackup. ___ Mailing list: https://launchpad.net/~nssbackup-team Post to : nssbackup-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~nssbackup-team More help : https://help.launchpad.net/ListHelp
Re: [Nssbackup-team] [Bug 576460] Re: nssbackup crashes with: IOError: Given copy source '/tmp/nssbackup/files.snar' does not exist.
Martin Schaaf wrote: > The backup destination is a ftp server. The expected full backup size is > between 50 and 80 GB. It tries to make a full backup and don't end. I > never come to the point where incremental backups are made. I use the > latest version from the PPA. Not sure if this helps, but I've had the experience writing large files to an ftp sever (DVD image in that case), where the write performance seemed to decrease very slowly, but exponentially (!). Could this be the case for you? Can you check progress of your seemingly non-ending backup by monitoring the file size of the tgz file on the ftp server, to confirm that it is getting progressively slower? -- Groetjes, Anton _ ___ | | | | _ _ ___,| K. Anton Feenstra | | / \ / \'| | | IBIVU/Bioinformatics - Free University Amsterdam | |( | )| | | De Boelelaan 1083A - 1081 HV Amsterdam - Netherlands | | \_/ \_/ | | | Tel +31 20 59 87783 - Fax +31 20 59 87653 - Room P136 | | | feens...@few.vu.nl - www.few.vu.nl/~feenstra/ | | | "Pump Up the Volume Along With the Tempo" (Jazzy Jeff)| |_|___| -- nssbackup crashes with: IOError: Given copy source '/tmp/nssbackup/files.snar' does not exist. https://bugs.launchpad.net/bugs/576460 You received this bug notification because you are a member of NSsbackup team, which is subscribed to NSsbackup. ___ Mailing list: https://launchpad.net/~nssbackup-team Post to : nssbackup-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~nssbackup-team More help : https://help.launchpad.net/ListHelp
[Nssbackup-team] [Bug 573733] Re: nssbackup does not prevent itself from running in parallel.
I meant nssbackupd rather than sbackupd. I'm a bit confused about the naming currently. -- nssbackup does not prevent itself from running in parallel. https://bugs.launchpad.net/bugs/573733 You received this bug notification because you are a member of NSsbackup team, which is subscribed to NSsbackup. ___ Mailing list: https://launchpad.net/~nssbackup-team Post to : nssbackup-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~nssbackup-team More help : https://help.launchpad.net/ListHelp
[Nssbackup-team] [Bug 573733] Re: nssbackup does not prevent itself from running in parallel.
Brief update: I've made a quick check and for me it works: I've executed sbackupd from terminal and started another sbackupd process after a short period of time. The second process was aborted with the (expected) error 'nssbackup already running'. Conclusion: not easy to reproduce for me -> I need more information about your settings etc. P.S.: Did you tried to run a simple test backup locally in order to exclude problems related to FTP connection? This question holds for any of your reported bugs. Thanks. -- nssbackup does not prevent itself from running in parallel. https://bugs.launchpad.net/bugs/573733 You received this bug notification because you are a member of NSsbackup team, which is subscribed to NSsbackup. ___ Mailing list: https://launchpad.net/~nssbackup-team Post to : nssbackup-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~nssbackup-team More help : https://help.launchpad.net/ListHelp
[Nssbackup-team] [Bug 577112] Re: nssbackup crashes with: GtkWarning: could not open display warnings.warn(str(e), _gtk.Warning)
Hi Martin, some more questions: Do you have your root account enabled? Are you logged in while the backup starts? Do manuell backups (as user/as root) work for you? From terminal/from GUI? Can you post a full log of the issue with debug loglevel enabled? I'm out of ideas so far. The only issue I'm seeing is this: https://bugs.launchpad.net/nssbackup/+bug/330646. But it does not crash. I'd really like to fix this issue but I need a hint. Could this somehow be related with https://bugs.launchpad.net/sbackup/+bug/294104 you've fixed in sbackup (dbus related)? I'm sorry for your trouble and thanks for your help. -- nssbackup crashes with: GtkWarning: could not open display warnings.warn(str(e), _gtk.Warning) https://bugs.launchpad.net/bugs/577112 You received this bug notification because you are a member of NSsbackup team, which is subscribed to NSsbackup. ___ Mailing list: https://launchpad.net/~nssbackup-team Post to : nssbackup-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~nssbackup-team More help : https://help.launchpad.net/ListHelp
[Nssbackup-team] [Bug 526544] Re: Bug "préc isement à..."
@Frederic ROBIN: Does your original problem still exists for you when using latest PPA version (RC9)? I've fixed the issue you've described in the latest version. -- Bug "précisement à..." https://bugs.launchpad.net/bugs/526544 You received this bug notification because you are a member of NSsbackup team, which is subscribed to NSsbackup. ___ Mailing list: https://launchpad.net/~nssbackup-team Post to : nssbackup-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~nssbackup-team More help : https://help.launchpad.net/ListHelp
[Nssbackup-team] [Bug 581539] Re: Aucun processus , aucun résultat
** Changed in: sbackup (Ubuntu) Status: New => Incomplete -- Aucun processus, aucun résultat https://bugs.launchpad.net/bugs/581539 You received this bug notification because you are a member of NSsbackup team, which is subscribed to sbackup in ubuntu. ___ Mailing list: https://launchpad.net/~nssbackup-team Post to : nssbackup-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~nssbackup-team More help : https://help.launchpad.net/ListHelp
[Nssbackup-team] Re : [Bug 526544] Re: Bug "p récisement à..."
hi, Settings are : custom, daily, exactly at... No compression, no split, Use custom local backup directory Full backup every 5 days purging : simple cutoff every 7 days Best regards De : Jean-Peer Lorenz À : robin_...@yahoo.fr Envoyé le : Sam 15 mai 2010, 16h 51min 53s Objet : [Bug 526544] Re: Bug "précisement à..." Thank you for reporting this issue. Can you provide some more information how to trigger this bug? What type of schedule did you choose? Simple or custom cron definition. What did you define? Do daily backups work for you? Thanks. ** Changed in: nssbackup Status: Fix Released => Incomplete ** Changed in: nssbackup/0.2 Status: Fix Released => Incomplete -- Bug "précisement à..." https://bugs.launchpad.net/bugs/526544 You received this bug notification because you are a direct subscriber of the bug. Status in Not So Simple Backup suite: Incomplete Status in NSsbackup 0.2 series: Incomplete Bug description: Bonjour à l'équipe et merci pour votre fabuleux travail !!! Je met ma pierre à l'édifice. J'ai trouvé un petit bug qui existe dans la version nssbackup_0.2-0rc8.2.tar.gz et qui existait dans les versions précédentes. Ce bug a été constaté sur les versions serveur 8.04Lts et 9.10 d'Ubuntu : Dans la planification, si on sélectionne 'Précisement à...", tout les jours, la sauvegarde ne s'effectue pas. Pour corriger, il faut modifier le source 'ConfigManager.py' Remplacer la ligne: execline = "if [ -x '/usr/local/share/nssbackup' ]; then /usr/local/share/nssbackup; fi;" Par: execline = "if [ -x '/usr/local/share/nssbackup/nssbackup' ]; then /usr/local/share/nssbackup/nssbackup; fi;" Merci de vos retours Frédéric ROBIN To unsubscribe from this bug, go to: https://bugs.launchpad.net/nssbackup/+bug/526544/+subscribe -- Bug "précisement à..." https://bugs.launchpad.net/bugs/526544 You received this bug notification because you are a member of NSsbackup team, which is subscribed to NSsbackup. ___ Mailing list: https://launchpad.net/~nssbackup-team Post to : nssbackup-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~nssbackup-team More help : https://help.launchpad.net/ListHelp
