nssbackup crashes with: GtkWarning: could not open display warnings.warn(str(e), _gtk.Warning)

Bug #577112 reported by Martin Schaaf
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nssbackup
Invalid
Undecided
Unassigned

Bug Description

Signal handler called with signal 14
Signal handler called with signal 14
Traceback (most recent call last):
  File "/usr/bin/nssbackupd", line 31, in <module>
    main(sys.argv)
  File "/usr/lib/python2.6/dist-packages/nssbackup/nssbackupd.py", line 267, in main
    sbd.run()
  File "/usr/lib/python2.6/dist-packages/nssbackup/nssbackupd.py", line 219, in run
    self.__onError(e)
  File "/usr/lib/python2.6/dist-packages/nssbackup/nssbackupd.py", line 236, in __onError
    self.__bm.endSBsession()
  File "/usr/lib/python2.6/dist-packages/nssbackup/managers/BackupManager.py", line 598, in endSBsession
    self.__copylogfile()
  File "/usr/lib/python2.6/dist-packages/nssbackup/managers/BackupManager.py", line 579, in __copylogfile
    Util.nssb_copy( self.config.get("log","file"), logf_target )
  File "/usr/lib/python2.6/dist-packages/nssbackup/util/__init__.py", line 114, in nssb_copy
    shutil.copyfile(prep_src, prep_dst)
  File "/usr/lib/python2.6/shutil.py", line 57, in copyfile
    fdst.close()
IOError: [Errno 5] Input/output error
libnotify-Message: Unable to get session bus: /bin/dbus-launch terminated abnormally with the following error: Autolaunch error: X11 initialization failed.

** (nssbackupd:6845): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed

** (nssbackupd:6845): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed
run-parts: /etc/cron.hourly/nssbackup exited with return code 1

libnotify-Message: Unable to get session bus: /bin/dbus-launch terminated abnormally with the following error: Autolaunch error: X11 initialization failed.

** (nssbackupd:6845): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed
2010-05-07 18:25:09,922 - ERROR - nssbackupd.py:__onError(226) - [Errno 5] Input/output error
2010-05-07 18:25:09,986 - ERROR - nssbackupd.py:__onError(227) - Traceback (most recent call last):
  File "/usr/lib/python2.6/dist-packages/nssbackup/nssbackupd.py", line 217, in run
    self.__bm.makeBackup()
  File "/usr/lib/python2.6/dist-packages/nssbackup/managers/BackupManager.py", line 367, in makeBackup
    self.__actualSnapshot.commit()
  File "/usr/lib/python2.6/dist-packages/nssbackup/util/Snapshot.py", line 341, in commit
    self.commitexcludefile()
  File "/usr/lib/python2.6/dist-packages/nssbackup/util/Snapshot.py", line 493, in commitexcludefile
    FAM.pickledump( self.__excludes, self.getPath()+os.sep +"excludes" )
  File "/usr/lib/python2.6/dist-packages/nssbackup/managers/FileAccessManager.py", line 105, in pickledump
    f.close()
IOError: [Errno 5] Input/output error

libnotify-Message: Unable to get session bus: /bin/dbus-launch terminated abnormally with the following error: Autolaunch error: X11 initialization failed.

Revision history for this message
Jean-Peer Lorenz (peer.loz) wrote :

Thank you for reporting this issue.

Can you provide some more information how to trigger this bug?

Maybe you could post the configuration used. Was a X server running while the error occured? Did you use the PPA version or a manual installation?

Thanks.

Changed in nssbackup:
status: New → Incomplete
Revision history for this message
Martin Schaaf (mascha) wrote :

I get this error on every backup try. I never get a finished full backup. The backup goes to a ftp server. The X-Server is running all the time. I use the latest version from the PPA.

Revision history for this message
Jean-Peer Lorenz (peer.loz) wrote :

Very interesting. I've never seen this error before and I've tested on Ubuntu 8.04 ... 9.10. What distribution are you using?

Revision history for this message
Martin Schaaf (mascha) wrote :

Ubuntu 10.04.

Revision history for this message
Jean-Peer Lorenz (peer.loz) wrote :

I've never seen this error before and I've tested on Ubuntu 8.04 ... 10.04. (this was what I originally wanted to write). I have nssbackup running on my multimedia machine using a 10.04 with scheduled backups.

Please, can you provide more background information in order to track down the problem:
Does this happen if you run as root or user?
Would you post your configuration?
Backups manually triggered or scheduled?
Is something special on your software setup (libraries deinstalled...)?

Thank you in advance.

Revision history for this message
Jean-Peer Lorenz (peer.loz) wrote :

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.

Revision history for this message
Martin Schaaf (mascha) wrote :

> 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.

Revision history for this message
Martin Schaaf (mascha) wrote :

[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://<login>:<password>@domain.local/array1/backup
format = none
mountdir = /mnt/nssbackup
purge = 60
maxincrement = 30
lockfile = /var/lock/nssbackup.lock

[report]
from = NSsbackup Daemon <email address hidden>

[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.

Revision history for this message
Martin Schaaf (mascha) wrote :

I started nssbackupd manual from a console window under X and it finished the first full backup. Now I enabled hourly backups again and the incremental backups work without problems.

The dbus error does not stop nssbackup. The dbus fix from sbackup does not help here.
It seems that the lock file bug prevents nssbackup from finishing regularly and this one is invalid.

I investigated the dbus thing a little bit more. And tried to connect from a virtual console (not a terminal under X) with dbus-monitor to the session dbus and got the same error message. Then I tried to connect eith dbus-monitor to the system dbus and this worked. I don't have so much experience with dbus but it seems nssbackupd should use the system dbus if it does not actually. And only if a user starts its own nssbackup daemon it should use this one. Does this make sense?

Thank you for your help Jean-Peer now I have taken the first hurdle to switch to nssbackup.

Revision history for this message
Jean-Peer Lorenz (peer.loz) wrote :

>It seems that the lock file bug prevents nssbackup from finishing regularly and this one is invalid.

Yes, you are right. The removal of the lock file during the second attempt of execution by cron leads to a failure when the first backup is finished. This is fixed in branch https://code.launchpad.net/~nssbackup-dev/nssbackup/0.2.

So, I will mark this one as invalid and added your comment #9 to https://bugs.launchpad.net/nssbackup/+bug/330646 in order to collect information on the dbus issue.

Thanks for your help.

Changed in nssbackup:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.