[Nssbackup-team] [Bug 1087872] Re: Backup to Remote PC Freezes
OK, thanks. Marking bug as invalid. For future reference, I think it is a bad idea to have two different schedules and/or users back up to the same backup location, and it actually seems to be not supported. It would be nice if this was signalled and reported back to the user in a more transparent way. Off-topic, gnome-schedule is a graphical front end for user cron jobs. Likely, that cron job still persists, verify with 'cron -l', and check further actions with 'man cron' ;-) ** Changed in: sbackup Status: New => Invalid -- You received this bug notification because you are a member of Simple Backup Maintainers, which is subscribed to sbackup. https://bugs.launchpad.net/bugs/1087872 Title: Backup to Remote PC Freezes To manage notifications about this bug go to: https://bugs.launchpad.net/sbackup/+bug/1087872/+subscriptions ___ 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 1087872] Re: Backup to Remote PC Freezes
*** CANCEL *** I believe that this bug report can be CANCELLED. As a result of continued experimentation, there appears to be a workaround. So far the workaround has NOT failed. But testing has been less than 24 hours. **Workaround: The ADMINSTRATIVE version is set to backup to an external USB device once per-day. smb://rt-n56u/AiDisk_a1/AltairBackup The USER version is set to backup to another directory on the internal hard drive. (A separate partition from home) /var/backups **Remaing Issue: I had loaded Gnome-Schedule to intiate the automated backups. My computer "crashed" for whatever reason. Anyway, after restoring my computer, it turned out that the USER version of Sbackup keeps running every hour. I have removed/reinstalled Gnome-Schedule, but I have been unable to stop the USER vesion Sbackup from running every hour. But that is NOT an issue with Sbackup, since the workaround is working. Please CANCEL this bug report. -- You received this bug notification because you are a member of Simple Backup Maintainers, which is subscribed to sbackup. https://bugs.launchpad.net/bugs/1087872 Title: Backup to Remote PC Freezes To manage notifications about this bug go to: https://bugs.launchpad.net/sbackup/+bug/1087872/+subscriptions ___ 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 1087872] Re: Backup to Remote PC Freezes
The automated backup worked for a while then stopped. It appears that the ADMINISTRATIVE version is the one that hangs, since I have to enter a password to cancel it. Unforutantley it won't let me cancel the job for some reason. I am looking a the the /etc/sbackup.conf file and the .config/sbackup/sbackup.conf file to see if I can eliminate the apparant conflict. One alternative may be changing the backup location for the USER version. -- You received this bug notification because you are a member of Simple Backup Maintainers, which is subscribed to sbackup. https://bugs.launchpad.net/bugs/1087872 Title: Backup to Remote PC Freezes To manage notifications about this bug go to: https://bugs.launchpad.net/sbackup/+bug/1087872/+subscriptions ___ 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 1087872] Re: Backup to Remote PC Freezes
I can confirm, today, that executing the ADMINISTRATIVE vesion manually resulted in both versions runnng. The manual execution was succesful. I have revised both the ADMINISTRATIVE and USER versions so that they do not backup the same files. I hypothesise that there may be a conflict when both version sare automatically initiated at the same time. I will have to wait an see how that works out. -- You received this bug notification because you are a member of Simple Backup Maintainers, which is subscribed to sbackup. https://bugs.launchpad.net/bugs/1087872 Title: Backup to Remote PC Freezes To manage notifications about this bug go to: https://bugs.launchpad.net/sbackup/+bug/1087872/+subscriptions ___ 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 1087872] Re: Backup to Remote PC Freezes
I have actually done that (changed the permissions), or to be more precise - I believe that I have done that. To follow-up on what you say, I have "root" privileges. So I am both ADMINISTRATOR and USER at the same time. 1. Through my "root" privileges I can schedule the Administrative version to run at specific times. 2. Both the ADMINISTRATIVE version and USER version have slightly different default profiles. I may be misunderstanding how the default profiles should be set-up between the two versions. 3. When the ADMINISTRATIVE version has a scheduled back-up, I am unclear as to whether the USER version should also be executing. It appears that it does, so there may be a conflict. I have "root" privileges and I am also am the USER at the same time. By coincidence, as I am writing this, I received the error message below from "cron". Also see #4 below. The error message would seem to imply that the ADMINISTRATIVE version was "rejected" from executing. --- "Backup is not being started. "Another application instance is already running. " -- 4. The current back-up (from #3) appears stuck at 98.6% for the past 2 hours. Based on the incomplete log generated so far, it would appear that the USER version executed, but that is now "stuck". I will let it run and see what happens. That would seem to imply that the error message mentioned in #3 fro, "cron" would apply to rejecting the ADMINISTRATIVE version from running. On Sat, Dec 29, 2012 at 4:29 AM, Anton wrote: > Just chiming in with a suggestion here, not sure if it will help. > > Could it be that when you run the backup as user, it fails to be able to > read the contents of the backup file because they are owned by root, > because (one of) the previous backup(s) was (were) made by root? And > this read-error is not caught? > > If you can check dir and file ownerships and permissions in your backup > location, you could fix it with chown and try again to see if that > solves it for you. > > Jean-Peer any chance you could get these .desktop file patches that make > the root sbackup appear different from the user ones, pushed into the > repositories? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1087872 > > Title: > Backup to Remote PC Freezes > > Status in sbackup: > New > > Bug description: > Using Ubuntu 12.10 attempting to backup to a remote WindowsXP computer > Have AMD-64 bit Ubuntu > sbackup-gtk 0.11.4-0ubuntu4 > installed from Ubuntu directly > > String to access remote computer: smb://sabre/Storage/Backup_Altair > > manually the backups seems to work correctly > However the automated mackup using Gnome Shcduler only works > sporadically. > > I just received error message "File access manager not initialized" > Aslo get an error message that Ubuntu has had an "internal error". > Then Ubuntu asks if I am attempting to connect to a remote computer, > which I am. > sbacckup "freezes" stays stuck in assembling files. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/sbackup/+bug/1087872/+subscriptions > -- You received this bug notification because you are a member of Simple Backup Maintainers, which is subscribed to sbackup. https://bugs.launchpad.net/bugs/1087872 Title: Backup to Remote PC Freezes To manage notifications about this bug go to: https://bugs.launchpad.net/sbackup/+bug/1087872/+subscriptions ___ 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 1087872] Re: Backup to Remote PC Freezes
Just chiming in with a suggestion here, not sure if it will help. Could it be that when you run the backup as user, it fails to be able to read the contents of the backup file because they are owned by root, because (one of) the previous backup(s) was (were) made by root? And this read-error is not caught? If you can check dir and file ownerships and permissions in your backup location, you could fix it with chown and try again to see if that solves it for you. Jean-Peer any chance you could get these .desktop file patches that make the root sbackup appear different from the user ones, pushed into the repositories? -- You received this bug notification because you are a member of Simple Backup Maintainers, which is subscribed to sbackup. https://bugs.launchpad.net/bugs/1087872 Title: Backup to Remote PC Freezes To manage notifications about this bug go to: https://bugs.launchpad.net/sbackup/+bug/1087872/+subscriptions ___ 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 1087872] Re: Backup to Remote PC Freezes
I finally separated the logs for the Administrator verson from the User version. This error log is from the User version. The Adminstration version worked. I have been wondering if having the two version creates a confilct PS: I have moved the back-up destination to a an external USB device attached to a router, the backup program succesfully writes a backup (when it wrorks). --- SBackup 'Default Profile' Logger == 2012-12-27 22:00:05,586 - INFO in ConfigManager.__create_logger(757): Log output for [Default Profile] is directed to file '/var/log/sbackup/UserVersion/sbackup.2012-12-27_22.00.05.584857.log'. 2012-12-27 22:00:05,586 - DEBUG in ConfigManager.validateConfigFileOpts(806): Validating config file. 2012-12-27 22:00:05,588 - INFO in ConfigManager.__init__(331): Profile settings are being read from file '/home/steve/.config/sbackup/sbackup.conf'. 2012-12-27 22:00:05,588 - DEBUG in backupproc.__init__(119): Simple Backup Suite 0.11.4 2012-12-27 22:00:05,593 - DEBUG in profile_handler.__init__(87): Instance of BackupProfileHandler created. 2012-12-27 22:00:05,594 - INFO in profile_handler.prepare(90): Preparation of backup process 2012-12-27 22:00:05,595 - DEBUG in pathparse.set_and_parse_uri(216): UriParser: Display name: smb://rt-n56u/AiDisk_a1/AltairBackup URI scheme: smb eff. scheme: smb Hostname: `rt-n56u` Path: `/AiDisk_a1/AltairBackup` Port: None Username: `None` Password: `None` 2012-12-27 22:00:05,596 - DEBUG in pathparse.set_and_parse_uri(216): UriParser: Display name: smb://rt-n56u/AiDisk_a1/AltairBackup URI scheme: smb eff. scheme: smb Hostname: `rt-n56u` Path: `/AiDisk_a1/AltairBackup` Port: None Username: `None` Password: `None` 2012-12-27 22:00:05,596 - INFO in _gio_fam.initialize(100): Initializing GIO File Access Manager. 2012-12-27 22:00:05,597 - DEBUG in pathparse.query_mount_uri(253): get_mount_uri: smb://rt-n56u/AiDisk_a1/AltairBackup 2012-12-27 22:00:05,597 - DEBUG in _gio_utils.mount(258): Mount path: smb://rt-n56u/AiDisk_a1/AltairBackup 2012-12-27 22:00:05,623 - DEBUG in _gio_utils._is_local(217): Given path is not local 2012-12-27 22:00:05,721 - DEBUG in pathparse.query_mount_uri(253): get_mount_uri: smb://rt-n56u/AiDisk_a1/AltairBackup 2012-12-27 22:00:05,727 - DEBUG in _gio_utils._set_mount_flag(244): Path_mount_info: Path: `smb://rt-n56u/AiDisk_a1/AltairBackup` Eff. path: `None` Mounted: True 2012-12-27 22:00:05,727 - DEBUG in _gio_utils._mount_done_cb(366): quit loop 2012-12-27 22:00:05,727 - DEBUG in _gio_utils._mount_done_cb(371): Calling additional callback 2012-12-27 22:00:05,728 - INFO in profile_handler.__check_target(336): Backup destination: smb://rt-n56u/AiDisk_a1/AltairBackup 2012-12-27 22:00:05,729 - DEBUG in pathparse.query_mount_uri(253): get_mount_uri: smb://rt-n56u/AiDisk_a1/AltairBackup 2012-12-27 22:00:05,738 - DEBUG in pathparse.query_mount_uri(253): get_mount_uri: smb://rt-n56u/AiDisk_a1/AltairBackup 2012-12-27 22:00:05,739 - INFO in _gio_utils._test_path(849): Perform tests at specified location 2012-12-27 22:00:05,740 - DEBUG in _gio_utils._test_path(852): test specified path for existence using GIO 2012-12-27 22:00:05,743 - DEBUG in _gio_utils._test_path(859): Test testdir: smb://rt-n56u/AiDisk_a1/AltairBackup/sbackup-dir-1356663605.74-1f6f2912-63e3-4749-aae7-39c6f96bd7a3.tmp 2012-12-27 22:00:05,748 - DEBUG in _gio_utils._test_path(865): Create testdir 2012-12-27 22:00:05,754 - DEBUG in _gio_utils._test_path(870): Test testfile for existence 2012-12-27 22:00:05,758 - DEBUG in _gio_utils._test_path(877): Create file 2012-12-27 22:00:11,492 - DEBUG in _gio_utils._test_path(879): Write buffer: `Some arbitrary content: bb528961-4e93-4f9e-9593-e9ebb4501aba` to file 2012-12-27 22:00:12,310 - DEBUG in _gio_utils._test_path(884): Re-read test file 2012-12-27 22:00:12,326 - DEBUG in _gio_utils._test_path(891): Some arbitrary content: bb528961-4e93-4f9e-9593-e9ebb4501aba 2012-12-27 22:00:12,327 - DEBUG in _gio_utils._test_path(896): Remove file 2012-12-27 22:00:12,333 - DEBUG in _gio_utils._test_path(898): Remove dir 2012-12-27 22:00:12,338 - DEBUG in pathparse.query_mount_uri(253): get_mount_uri: smb://rt-n56u/AiDisk_a1/AltairBackup 2012-12-27 22:00:12,339 - DEBUG in pathparse.query_mount_uri(253): get_mount_uri: smb://rt-n56u/AiDisk_a1/AltairBackup 2012-12-27 22:00:12,339 - INFO in UpgradeManager.need_upgrade(145): Checking for snapshots stored in old formats 2012-12-27 22:38:13,934 - ERROR in backupproc.except_hook(66): Uncaught exception: Application was terminated by signal 15. 2012-12-27 22:38:13,935 - ERROR in backupproc.except_hook(67): Traceback (most recent call last): File "/usr/bin/sbackup", line 42, in retc = main(sys.argv) File "/usr/share/sbackup/sbackup/backupproc.py", line 581, in main exitcode = sbackup_app.run() File "/usr/share/sbackup/sbackup/backup
[Nssbackup-team] [Bug 1087872] Re: Backup to Remote PC Freezes
For a couple of days it seemed to work. Today it froze. When I tried to clsoe it, it said that it could not be done. I could not find a way to kill sbackup. It did not show-up as an active process. Below is the log. When you look at the last line, there is no indication of failure or completion. So I assume that sbackup "froze" at that point. The progress bar, stays frozen on "backup being prepared". --- SBackup 'Default Profile' Logger == 2012-12-21 17:00:06,520 - INFO in ConfigManager.__create_logger(757): Log output for [Default Profile] is directed to file '/var/log/sbackup.2012-12-21_17.00.06.518966.log'. 2012-12-21 17:00:06,521 - DEBUG in ConfigManager.validateConfigFileOpts(806): Validating config file. 2012-12-21 17:00:06,523 - INFO in ConfigManager.__init__(331): Profile settings are being read from file '/home/steve/.config/sbackup/sbackup.conf'. 2012-12-21 17:00:06,523 - DEBUG in backupproc.__init__(119): Simple Backup Suite 0.11.4 2012-12-21 17:00:06,578 - DEBUG in profile_handler.__init__(87): Instance of BackupProfileHandler created. 2012-12-21 17:00:06,579 - INFO in profile_handler.prepare(90): Preparation of backup process 2012-12-21 17:00:06,580 - DEBUG in pathparse.set_and_parse_uri(216): UriParser: Display name: smb://sabre/Storage/Backup_Altair URI scheme: smb eff. scheme: smb Hostname: `sabre` Path: `/Storage/Backup_Altair` Port: None Username: `None` Password: `None` 2012-12-21 17:00:06,581 - DEBUG in pathparse.set_and_parse_uri(216): UriParser: Display name: smb://sabre/Storage/Backup_Altair URI scheme: smb eff. scheme: smb Hostname: `sabre` Path: `/Storage/Backup_Altair` Port: None Username: `None` Password: `None` 2012-12-21 17:00:06,581 - INFO in _gio_fam.initialize(100): Initializing GIO File Access Manager. 2012-12-21 17:00:06,582 - DEBUG in pathparse.query_mount_uri(253): get_mount_uri: smb://sabre/Storage/Backup_Altair 2012-12-21 17:00:06,582 - DEBUG in _gio_utils.mount(258): Mount path: smb://sabre/Storage/Backup_Altair 2012-12-21 17:00:06,608 - DEBUG in _gio_utils._is_local(217): Given path is not local 2012-12-21 17:00:07,113 - DEBUG in pathparse.query_mount_uri(253): get_mount_uri: smb://sabre/Storage/Backup_Altair 2012-12-21 17:00:07,119 - DEBUG in _gio_utils._set_mount_flag(244): Path_mount_info: Path: `smb://sabre/Storage/Backup_Altair` Eff. path: `None` Mounted: True 2012-12-21 17:00:07,119 - DEBUG in _gio_utils._mount_done_cb(366): quit loop 2012-12-21 17:00:07,119 - DEBUG in _gio_utils._mount_done_cb(371): Calling additional callback 2012-12-21 17:00:07,121 - INFO in profile_handler.__check_target(336): Backup destination: smb://sabre/Storage/Backup_Altair 2012-12-21 17:00:07,121 - DEBUG in pathparse.query_mount_uri(253): get_mount_uri: smb://sabre/Storage/Backup_Altair 2012-12-21 17:00:07,130 - DEBUG in pathparse.query_mount_uri(253): get_mount_uri: smb://sabre/Storage/Backup_Altair 2012-12-21 17:00:07,131 - INFO in _gio_utils._test_path(849): Perform tests at specified location 2012-12-21 17:00:07,132 - DEBUG in _gio_utils._test_path(852): test specified path for existence using GIO 2012-12-21 17:00:07,135 - DEBUG in _gio_utils._test_path(859): Test testdir: smb://sabre/Storage/Backup_Altair/sbackup-dir-1356127207.13-edeb5dd4-a30d-4482-96e5-fc232db9cddb.tmp 2012-12-21 17:00:07,148 - DEBUG in _gio_utils._test_path(865): Create testdir 2012-12-21 17:00:07,189 - DEBUG in _gio_utils._test_path(870): Test testfile for existence 2012-12-21 17:00:07,193 - DEBUG in _gio_utils._test_path(877): Create file 2012-12-21 17:00:07,226 - DEBUG in _gio_utils._test_path(879): Write buffer: `Some arbitrary content: dd4168ef-af19-4b52-aa6d-011eecb77846` to file 2012-12-21 17:00:07,236 - DEBUG in _gio_utils._test_path(884): Re-read test file 2012-12-21 17:00:07,247 - DEBUG in _gio_utils._test_path(891): Some arbitrary content: dd4168ef-af19-4b52-aa6d-011eecb77846 2012-12-21 17:00:07,247 - DEBUG in _gio_utils._test_path(896): Remove file 2012-12-21 17:00:07,252 - DEBUG in _gio_utils._test_path(898): Remove dir 2012-12-21 17:00:07,257 - DEBUG in pathparse.query_mount_uri(253): get_mount_uri: smb://sabre/Storage/Backup_Altair 2012-12-21 17:00:07,257 - DEBUG in pathparse.query_mount_uri(253): get_mount_uri: smb://sabre/Storage/Backup_Altair 2012-12-21 17:00:07,258 - INFO in UpgradeManager.need_upgrade(145): Checking for snapshots stored in old formats 2012-12-21 17:00:07,710 - INFO in SnapshotManager._read_snps_from_disk_allformats(214): Invalid snapshot `duplicity-full.20121031T020703Z.vol1.difftar.gz` found: Name of snapshot not valid. 2012-12-21 17:00:07,715 - INFO in SnapshotManager._read_snps_from_disk_allformats(214): Invalid snapshot `duplicity-full.20121031T020703Z.vol10.difftar.gz` found: Name of snapshot not valid. 2012-12-21 17:00:07,719 - INFO in SnapshotManager._read_snps_from_disk_allformats(214): Invalid snapshot `
[Nssbackup-team] [Bug 1087872] Re: Backup to Remote PC Freezes
SBackup 'Default Profile' Logger
==
2012-12-19 18:00:07,440 - INFO in ConfigManager.__create_logger(757): Log
output for [Default Profile] is directed to file
'/var/log/sbackup.2012-12-19_18.00.07.438819.log'.
2012-12-19 18:00:07,440 - DEBUG in ConfigManager.validateConfigFileOpts(806):
Validating config file.
2012-12-19 18:00:07,442 - INFO in ConfigManager.__init__(331): Profile settings
are being read from file '/home/steve/.config/sbackup/sbackup.conf'.
2012-12-19 18:00:07,442 - DEBUG in backupproc.__init__(119): Simple Backup
Suite 0.11.4
2012-12-19 18:00:07,466 - DEBUG in profile_handler.__init__(87): Instance of
BackupProfileHandler created.
2012-12-19 18:00:07,467 - INFO in profile_handler.prepare(90): Preparation of
backup process
2012-12-19 18:00:07,468 - DEBUG in pathparse.set_and_parse_uri(216): UriParser:
Display name: smb://sabre/Storage/Backup_Altair
URI scheme: smb
eff. scheme: smb
Hostname: `sabre`
Path: `/Storage/Backup_Altair`
Port: None
Username: `None`
Password: `None`
2012-12-19 18:00:07,468 - DEBUG in pathparse.set_and_parse_uri(216): UriParser:
Display name: smb://sabre/Storage/Backup_Altair
URI scheme: smb
eff. scheme: smb
Hostname: `sabre`
Path: `/Storage/Backup_Altair`
Port: None
Username: `None`
Password: `None`
2012-12-19 18:00:07,469 - INFO in _gio_fam.initialize(100): Initializing GIO
File Access Manager.
2012-12-19 18:00:07,469 - DEBUG in pathparse.query_mount_uri(253):
get_mount_uri: smb://sabre/Storage/Backup_Altair
2012-12-19 18:00:07,469 - DEBUG in _gio_utils.mount(258): Mount path:
smb://sabre/Storage/Backup_Altair
2012-12-19 18:00:07,509 - DEBUG in _gio_utils._is_local(217): Given path is not
local
2012-12-19 18:00:07,516 - DEBUG in pathparse.query_mount_uri(253):
get_mount_uri: smb://sabre/Storage/Backup_Altair
2012-12-19 18:00:07,521 - DEBUG in _gio_utils._set_mount_flag(244):
Path_mount_info: Path: `smb://sabre/Storage/Backup_Altair`
Eff. path: `None`
Mounted: False
2012-12-19 18:00:07,521 - ERROR in _gio_utils._mount_done_cb(363): No such
interface `org.gtk.vfs.MountTracker' on object at path /org/gtk/vfs/mounttracker
2012-12-19 18:00:07,521 - DEBUG in _gio_utils._mount_done_cb(366): quit loop
2012-12-19 18:00:07,522 - DEBUG in _gio_utils._mount_done_cb(371): Calling
additional callback
2012-12-19 18:00:07,537 - ERROR in backupproc.except_hook(66): Uncaught
exception: Unable to mount: No such interface `org.gtk.vfs.MountTracker' on
object at path /org/gtk/vfs/mounttracker
2012-12-19 18:00:07,538 - ERROR in backupproc.except_hook(67): Traceback (most
recent call last):
File "/usr/share/sbackup/sbackup/fs_backend/_gio_utils.py", line 372, in
_mount_done_cb
self.__mount_finish_callback(error)
File "/usr/share/sbackup/sbackup/fs_backend/_gio_fam.py", line 157, in
_mount_cb
raise exceptions.FileAccessException("Unable to mount: %s" % error)
FileAccessException: Unable to mount: No such interface
`org.gtk.vfs.MountTracker' on object at path /org/gtk/vfs/mounttracker
2012-12-19 18:00:07,539 - ERROR in backupproc.__notify_error(335): An error
occurred during the backup:
File access manager not initialized
Traceback (most recent call last):
File "/usr/share/sbackup/sbackup/backupproc.py", line 282, in run
self.__bprofilehdl.prepare()
File "/usr/share/sbackup/sbackup/core/profile_handler.py", line 101, in
prepare
self.__check_target()
File "/usr/share/sbackup/sbackup/core/profile_handler.py", line 331, in
__check_target
assert self.__fam_target_hdl.is_initialized(), "File access manager not
initialized"
AssertionError: File access manager not initialized
2012-12-19 18:00:07,559 - WARNING in profile_handler.__copylogfile(273): Unable
to copy log. File access is not initialized.
2012-12-19 18:00:07,560 - INFO in _gio_fam.terminate(114): Terminating GIO File
Access Manager.
2012-12-19 18:00:07,560 - WARNING in _gio_fam.terminate(128): GIO File Access
Manager is not initialized. Nothing to do.
2012-12-19 18:00:07,561 - DEBUG in _gio_fam.terminate(129): Calling callbacks
anyway
2012-12-19 18:00:07,561 - INFO in profile_handler.finish(325): Processing of
profile failed with error: File access manager not initialized
--
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to sbackup.
https://bugs.launchpad.net/bugs/1087872
Title:
Backup to Remote PC Freezes
To manage notifications about this bug go to:
https://bugs.launchpad.net/sbackup/+bug/1087872/+subscriptions
___
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 1087872] Re: Backup to Remote PC Freezes
The good and bad news, I received this dump. 12/17/2012 I did delete an earlier back-up, so i don't know if that had an effect. --- 2012-12-17 21:31:11,229 - INFO: Log output for [Default Profile] is directed to file '/home/steve/.local/share/sbackup/log/sbackup.2012-12-17_21.31.11.191270.log'. 2012-12-17 21:31:11,231 - INFO: Profile settings are being read from file '/home/steve/.config/sbackup/sbackup.conf'. 2012-12-17 21:31:11,260 - INFO: Preparation of backup process 2012-12-17 21:31:11,262 - INFO: Initializing GIO File Access Manager. 2012-12-17 21:31:11,467 - INFO: Backup destination: smb://sabre/Storage/Backup_Altair 2012-12-17 21:31:11,476 - INFO: Perform tests at specified location 2012-12-17 21:31:11,519 - INFO: Checking for snapshots stored in old formats 2012-12-17 21:31:11,579 - INFO: Invalid snapshot `duplicity-full.20121031T020703Z.vol1.difftar.gz` found: Name of snapshot not valid. 2012-12-17 21:31:11,583 - INFO: Invalid snapshot `duplicity-full.20121031T020703Z.vol10.difftar.gz` found: Name of snapshot not valid. 2012-12-17 21:31:11,588 - INFO: Invalid snapshot `duplicity-full.20121031T020703Z.vol11.difftar.gz` found: Name of snapshot not valid. 2012-12-17 21:31:11,592 - INFO: Invalid snapshot `duplicity-full.20121031T020703Z.vol12.difftar.gz` found: Name of snapshot not valid. 2012-12-17 21:31:11,598 - INFO: Invalid snapshot `duplicity-full.20121031T020703Z.vol2.difftar.gz` found: Name of snapshot not valid. 2012-12-17 21:31:11,603 - INFO: Invalid snapshot `duplicity-full.20121031T020703Z.vol3.difftar.gz` found: Name of snapshot not valid. 2012-12-17 21:31:11,608 - INFO: Invalid snapshot `duplicity-full.20121031T020703Z.vol4.difftar.gz` found: Name of snapshot not valid. 2012-12-17 21:31:11,612 - INFO: Invalid snapshot `duplicity-full.20121031T020703Z.vol5.difftar.gz` found: Name of snapshot not valid. 2012-12-17 21:31:11,617 - INFO: Invalid snapshot `duplicity-full.20121031T020703Z.vol6.difftar.gz` found: Name of snapshot not valid. 2012-12-17 21:31:11,621 - INFO: Invalid snapshot `duplicity-full.20121031T020703Z.vol7.difftar.gz` found: Name of snapshot not valid. 2012-12-17 21:31:11,626 - INFO: Invalid snapshot `duplicity-full.20121031T020703Z.vol8.difftar.gz` found: Name of snapshot not valid. 2012-12-17 21:31:11,631 - INFO: Invalid snapshot `duplicity-full.20121031T020703Z.vol9.difftar.gz` found: Name of snapshot not valid. 2012-12-17 21:31:11,755 - INFO: Invalid snapshot `duplicity-full.20121031T020703Z.vol1.difftar.gz` found: Name of snapshot not valid. 2012-12-17 21:31:11,760 - INFO: Invalid snapshot `duplicity-full.20121031T020703Z.vol10.difftar.gz` found: Name of snapshot not valid. 2012-12-17 21:31:11,765 - INFO: Invalid snapshot `duplicity-full.20121031T020703Z.vol11.difftar.gz` found: Name of snapshot not valid. 2012-12-17 21:31:11,776 - INFO: Invalid snapshot `duplicity-full.20121031T020703Z.vol12.difftar.gz` found: Name of snapshot not valid. 2012-12-17 21:31:11,786 - INFO: Invalid snapshot `duplicity-full.20121031T020703Z.vol2.difftar.gz` found: Name of snapshot not valid. 2012-12-17 21:31:11,794 - INFO: Invalid snapshot `duplicity-full.20121031T020703Z.vol3.difftar.gz` found: Name of snapshot not valid. 2012-12-17 21:31:11,805 - INFO: Invalid snapshot `duplicity-full.20121031T020703Z.vol4.difftar.gz` found: Name of snapshot not valid. 2012-12-17 21:31:11,810 - INFO: Invalid snapshot `duplicity-full.20121031T020703Z.vol5.difftar.gz` found: Name of snapshot not valid. 2012-12-17 21:31:11,815 - INFO: Invalid snapshot `duplicity-full.20121031T020703Z.vol6.difftar.gz` found: Name of snapshot not valid. 2012-12-17 21:31:11,821 - INFO: Invalid snapshot `duplicity-full.20121031T020703Z.vol7.difftar.gz` found: Name of snapshot not valid. 2012-12-17 21:31:11,832 - INFO: Invalid snapshot `duplicity-full.20121031T020703Z.vol8.difftar.gz` found: Name of snapshot not valid. 2012-12-17 21:31:11,844 - INFO: Invalid snapshot `duplicity-full.20121031T020703Z.vol9.difftar.gz` found: Name of snapshot not valid. ^CTraceback (most recent call last): File "/usr/share/sbackup/sbackup-dbusservice", line 40, in retc = run(sys.argv) File "/usr/share/sbackup/sbackup/dbus_service.py", line 401, in run __launch_service(keep_alive = _options.keep_alive) File "/usr/share/sbackup/sbackup/dbus_service.py", line 351, in __launch_service sbak_service.main() File "/usr/share/sbackup/sbackup/dbus_service.py", line 324, in main self._mainloop.run() KeyboardInterrupt 2012-12-17 21:32:35,185 - WARNING: Unable to unregister connection: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus) 2012-12-17 21:32:35,185 - WARNING: Unable to unregister connection (failed). -- You received this bug notification because you are a member of Simple Backup Maintainers, which is subscribed to sbackup. https://bugs.l
Re: [Nssbackup-team] [Bug 1087872] Re: Backup to Remote PC Freezes
Thanks for responding. I am using Ubuntu Version 12.10. The manual execution of sbackup works. On Thu, Dec 13, 2012 at 4:53 PM, Jean-Peer Lorenz < 1087...@bugs.launchpad.net> wrote: > Thank you for using sbackup and reporting this issue. > > I guess the issue you are encountering is related to this: > > 2012-12-09 20:00:12,956 - ERROR: No such interface > `org.gtk.vfs.MountTracker' on object at path /org/gtk/vfs/mounttracker > > What version of Ubuntu are you using? > Do manuell backups work all the time? > > Thank you so much for your help. > > Regards, > Jean-Peer > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1087872 > > Title: > Backup to Remote PC Freezes > > Status in sbackup: > New > > Bug description: > Using Ubuntu 12.10 attempting to backup to a remote WindowsXP computer > Have AMD-64 bit Ubuntu > sbackup-gtk 0.11.4-0ubuntu4 > installed from Ubuntu directly > > String to access remote computer: smb://sabre/Storage/Backup_Altair > > manually the backups seems to work correctly > However the automated mackup using Gnome Shcduler only works > sporadically. > > I just received error message "File access manager not initialized" > Aslo get an error message that Ubuntu has had an "internal error". > Then Ubuntu asks if I am attempting to connect to a remote computer, > which I am. > sbacckup "freezes" stays stuck in assembling files. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/sbackup/+bug/1087872/+subscriptions > -- You received this bug notification because you are a member of Simple Backup Maintainers, which is subscribed to sbackup. https://bugs.launchpad.net/bugs/1087872 Title: Backup to Remote PC Freezes To manage notifications about this bug go to: https://bugs.launchpad.net/sbackup/+bug/1087872/+subscriptions ___ 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 1087872] Re: Backup to Remote PC Freezes
Thank you for using sbackup and reporting this issue. I guess the issue you are encountering is related to this: 2012-12-09 20:00:12,956 - ERROR: No such interface `org.gtk.vfs.MountTracker' on object at path /org/gtk/vfs/mounttracker What version of Ubuntu are you using? Do manuell backups work all the time? Thank you so much for your help. Regards, Jean-Peer -- You received this bug notification because you are a member of Simple Backup Maintainers, which is subscribed to sbackup. https://bugs.launchpad.net/bugs/1087872 Title: Backup to Remote PC Freezes To manage notifications about this bug go to: https://bugs.launchpad.net/sbackup/+bug/1087872/+subscriptions ___ 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 1087872] Re: Backup to Remote PC Freezes
Found this log entry. Is this helpful?
---
Backup 'Default Profile' Logger
==
2012-12-09 20:00:12,629 - INFO: Log output for [Default Profile] is directed to
file
'/home/steve/.local/share/sbackup/log/sbackup.2012-12-09_20.00.12.537149.log'.
2012-12-09 20:00:12,631 - INFO: Profile settings are being read from file
'/home/steve/.config/sbackup/sbackup.conf'.
2012-12-09 20:00:12,705 - INFO: Preparation of backup process
2012-12-09 20:00:12,707 - INFO: Initializing GIO File Access Manager.
2012-12-09 20:00:12,956 - ERROR: No such interface `org.gtk.vfs.MountTracker'
on object at path /org/gtk/vfs/mounttracker
2012-12-09 20:00:13,050 - ERROR: Uncaught exception: Unable to mount: No such
interface `org.gtk.vfs.MountTracker' on object at path /org/gtk/vfs/mounttracker
2012-12-09 20:00:13,051 - ERROR: Traceback (most recent call last):
File "/usr/share/sbackup/sbackup/fs_backend/_gio_utils.py", line 372, in
_mount_done_cb
self.__mount_finish_callback(error)
File "/usr/share/sbackup/sbackup/fs_backend/_gio_fam.py", line 157, in
_mount_cb
raise exceptions.FileAccessException("Unable to mount: %s" % error)
FileAccessException: Unable to mount: No such interface
`org.gtk.vfs.MountTracker' on object at path /org/gtk/vfs/mounttracker
2012-12-09 20:00:13,053 - ERROR: An error occurred during the backup: File
access manager not initialized
2012-12-09 20:00:13,060 - WARNING: Unable to copy log. File access is not
initialized.
2012-12-09 20:00:13,061 - INFO: Terminating GIO File Access Manager.
2012-12-09 20:00:13,063 - WARNING: GIO File Access Manager is not initialized.
Nothing to do.
2012-12-09 20:00:13,064 - INFO: Processing of profile failed with error: File
access manager not initialized
--
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to sbackup.
https://bugs.launchpad.net/bugs/1087872
Title:
Backup to Remote PC Freezes
To manage notifications about this bug go to:
https://bugs.launchpad.net/sbackup/+bug/1087872/+subscriptions
___
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 1087872] Re: Backup to Remote PC Freezes
sbackup log file output 12/9/2012 unfortunately does not mean much to me. Updating DISPLAY to: :0 Updating SSH_AUTH_SOCK to: /tmp/ssh-AkWsSMP5ySFH/agent.1770 Updating GNOME_KEYRING_CONTROL to: None Updating GNOME_KEYRING_PID to: None Updating XAUTHORITY to: /home/steve/.Xauthority Updating GPG_AGENT_INFO to: None D-Bus session bus launched DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-5FlFVve5WG,guid=47818c2b9713ba978561e98450c52603 DBUS_SESSION_BUS_PID=5924 Attempt to launch indicator application (status icon). Indicator application started (PID: 5933) Updating GNOME_KEYRING_CONTROL to: None Updating GNOME_KEYRING_PID to: None Updating GPG_AGENT_INFO to: None -- You received this bug notification because you are a member of Simple Backup Maintainers, which is subscribed to sbackup. https://bugs.launchpad.net/bugs/1087872 Title: Backup to Remote PC Freezes To manage notifications about this bug go to: https://bugs.launchpad.net/sbackup/+bug/1087872/+subscriptions ___ 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
