sbackup

Sbackup and Cron failure in XFCE

Asked by Jason Ward

I have used sbackup for what seems like a long time now and been very happy with it, but I'm not at all happy with Unity and Gnome so have migrated to the XFCE desktop.

I installed sbackup expecting some problems as you are very specific its a Gnome app, but it runs fine, command line and GUI, user and superuser.

But what doesn't work is the scheduling. In the log I get this...

[code](process:20918): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Unable to autolaunch a dbus-daemon without a $DISPLAY for X11

(process:20918): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
2011-12-16 15:17:02,407 - INFO: Log output for [Default Profile] is directed to file '/var/log/sbackup/sbackup.2011-12-16_15.17.02.406464.log'.
2011-12-16 15:17:02,407 - INFO: Profile settings are being read from file '/etc/sbackup.conf'.
2011-12-16 15:17:02,410 - INFO: Preparando el proceso de backup
2011-12-16 15:17:02,411 - INFO: Initializing GIO File Access Manager.
2011-12-16 15:17:02,413 - ERROR: Error in `_do_mount`: volume doesn't implement mount [ERROR_NOT_SUPPORTED - Operation not supported for the current backend.]
2011-12-16 15:17:02,414 - ERROR: Uncaught exception: Unable to mount: volume doesn't implement mount
2011-12-16 15:17:02,414 - 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: volume doesn't implement mount

2011-12-16 15:17:02,414 - ERROR: Während der Sicherung trat ein Fehler auf: File access manager not initialized
2011-12-16 15:17:02,419 - WARNING: Unable to copy log. File access is not initialised.
2011-12-16 15:17:02,419 - INFO: Terminating GIO File Access Manager.
2011-12-16 15:17:02,419 - WARNING: GIO File Access Manager is not initialized. Nothing to do.
2011-12-16 15:17:02,420 - INFO: Processing of profile failed with error: File access manager not initialized

2011-12-16 15:17:02,421 - INFO: SBackupdDBusObject is being terminated.
No desktop session found
No desktop session found
No desktop session found
No desktop session found
No desktop session found
No desktop session found
Error while getting gconf setting: No D-BUS daemon running

Default value is used.
Error while setting gconf value: No D-BUS daemon running

Error can be safely ignored: setting is not being changed.
D-Bus session bus launched
 DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-bK8ogxBm5f,guid=03caab37f4db98130fba0b220002b652
 DBUS_SESSION_BUS_PID=20945
Attempt to launch indicator application (status icon).
No desktop session found
No desktop session found. Indicator application is not started.
drop privileges: running as nobody/nogroup[/code]

I'm ignoring the DBUS stuff as I think thats the indicator stuff for Gnome and the logs imply its not that important, but the bit that says[code]2011-12-16 15:17:02,411 - INFO: Initializing GIO File Access Manager.
2011-12-16 15:17:02,413 - ERROR: Error in `_do_mount`: volume doesn't implement mount [ERROR_NOT_SUPPORTED - Operation not supported for the current backend.]
2011-12-16 15:17:02,414 - ERROR: Uncaught exception: Unable to mount: volume doesn't implement mount
2011-12-16 15:17:02,414 - 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: volume doesn't implement mount

2011-12-16 15:17:02,414 - ERROR: Während der Sicherung trat ein Fehler auf: File access manager not initialized[/code]Seems the important bit.

Can you cast any light on what's happening?

Question information

Language:
English Edit question
Status:
Expired
For:
sbackup Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Jason Ward (jason-jasonward) said : 		#1

I appear to have tracked down the problem

It relates to a new "feature" in DBUS

It would seem sbackup will from 11.10 now always fail to run as a cron job

https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/812940

Revision history for this message
Launchpad Janitor (janitor) said : 		#2

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Revision history for this message
Dragos Toader (dragos-toader) said : 		#3

Just dbus-launch per session before calling sbackup in your cron job. No biggie.
Here is my full workaround:

------------------------------------------------------------------------------------------

#############
# "/home/dtoader/My Documents/linux/backups/launchDbus.sh"
#############
#!/bin/bash

if test -z "$DBUS_SESSION_BUS_ADDRESS" ; then
    ## if not found, launch a new one
    eval `dbus-launch --sh-syntax --exit-with-session`
    echo "D-Bus per-session daemon address is: $DBUS_SESSION_BUS_ADDRESS"
fi

------------------------------------------------------------------------------------------

#############
# "/home/dtoader/My Documents/linux/backups/sbackup500.conf"
#############
[general]
maxincrement = 1
format = 1
followlinks = 0
target = /home/backup500/files
purge = 5
mountdir = /home/dtoader/.local/share/sbackup/mountdir500
lockfile = /var/lock/sbackup/sbackup500.lock
splitsize = 0

[exclude]
regex = \.xxxxxxxxxx
maxsize = 9999220736

[log]
level = 20
file = /home/dtoader/.local/share/sbackup/log/sbackup500.log

[places]
prefix = /usr

[schedule]

[dirconfig]
/home/dtoader = 1
/root = 1
/etc = 1
/home/backup501 = 0
/home/backup500 = 0
/home/dtoader/.pulse = 0

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

------------------------------------------------------------------------------------------

#############
#"/etc/cron.d/sbackup500"
#############
# /etc/cron.d/sbackup500
# At 12 PM every day
# m h dom mon dow user command
0 12 * * * root "/home/dtoader/My Documents/linux/backups/launchDbus.sh"; /usr/bin/sbackup --no-indicator --no-dbus --conf="/home/dtoader/My Documents/linux/backups/sbackup500.conf"