Problems with running timevault

Asked by fsk141

Here is the error I'm getting, and I was wondering if you could shed any light on the error:
"
Traceback (most recent call last):
  File "/usr/bin/timevault/timevaultNotifier.py", line 187, in <module>
    N = Notifier()
  File "/usr/bin/timevault/timevaultNotifier.py", line 52, in __init__
    self.InitializeDBusLibNotify()
  File "/usr/bin/timevault/timevaultNotifier.py", line 123, in InitializeDBusLibNotify
    bus = dbus.SessionBus()
  File "/usr/lib/python2.5/site-packages/dbus/_dbus.py", line 215, in __new__
    mainloop=mainloop)
  File "/usr/lib/python2.5/site-packages/dbus/_dbus.py", line 106, in __new__
    bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop)
  File "/usr/lib/python2.5/site-packages/dbus/bus.py", line 107, in __new__
    bus = cls._new_for_bus(address_or_type, mainloop=mainloop)
dbus.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
"

Thanks, Jonny

Question information

Language:
English Edit question
Status:
Answered
For:
TimeVault Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
fsk141 (fsk141) said :
#1

I did a little messing around and here's what I found when I ran individual python scripts...

timevault.py
"
Traceback (most recent call last):
  File "./timevault.py", line 311, in <module>
    tv = TimeVault()
  File "./timevault.py", line 64, in __init__
    timevaultDBusServer.Server.__init__(self)
  File "/usr/bin/timevault/timevaultDBusServer.py", line 37, in __init__
    bus_name = dbus.service.BusName("net.launchpad.timevault", bus=dbus.SystemBus())
  File "/usr/lib/python2.5/site-packages/dbus/_dbus.py", line 198, in __new__
    private=private)
  File "/usr/lib/python2.5/site-packages/dbus/_dbus.py", line 106, in __new__
    bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop)
  File "/usr/lib/python2.5/site-packages/dbus/bus.py", line 107, in __new__
    bus = cls._new_for_bus(address_or_type, mainloop=mainloop)
dbus.DBusException: org.freedesktop.DBus.Error.FileNotFound: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
"

timevaultGUI.py - worked fine

timevaultNotifier.py
"
Traceback (most recent call last):
  File "./timevaultNotifier.py", line 187, in <module>
    N = Notifier()
  File "./timevaultNotifier.py", line 52, in __init__
    self.InitializeDBusLibNotify()
  File "./timevaultNotifier.py", line 123, in InitializeDBusLibNotify
    bus = dbus.SessionBus()
  File "/usr/lib/python2.5/site-packages/dbus/_dbus.py", line 215, in __new__
    mainloop=mainloop)
  File "/usr/lib/python2.5/site-packages/dbus/_dbus.py", line 106, in __new__
    bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop)
  File "/usr/lib/python2.5/site-packages/dbus/bus.py", line 107, in __new__
    bus = cls._new_for_bus(address_or_type, mainloop=mainloop)
dbus.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
"

timevaultPicker.py - worked fine

It's odd that GUI, and Picker worked fine, and nothing else did. All the errors are listed, and everything was ran under root. If you need anything else please let me know.
Thanks, Jonny

Revision history for this message
fsk141 (fsk141) said :
#2

Ok, I got timevault.py working, I hadn't started dbus, now the only thing not working is the Notifier

Revision history for this message
SourceContact (sourcecontact) said :
#3

Sorry, Launchpad didn't email me about this question for some reason. But it looks like you took care of most of it yourself. Have you installed 0.6.7. Does notifier work in that one?

Revision history for this message
fsk141 (fsk141) said :
#4

No, 0.6.7 didn't help, still the same error, And only notifier isn't working... It's really a bummer, and I think it might be a dbus error. I'm not for sure, but that's the most logical reason. It seems to kinda work, yet I get the same did not receive a reply from dbus when i start up thunar. Yet I still think it roots back to the software for the previous lines that say traceback, and so on. And that talk about bus.py. I would really like to get this software working so that I might be able to help with further development, maybe make the software a little more user friendly. And possibly build a source from C so that it can be compiled. Right now I'm running Arch Linux, and an XFCE4 GUI. I know I'm not on ubuntu, but that shouldn't matter since its written in python, and I have all the dependencies, and such. Let me know if anything comes to mind.
Thanks, Jonny

Revision history for this message
SourceContact (sourcecontact) said :
#5

Oh, I didn't know you weren't running GNOME.

Do you start DBus manually after logging in?

You probably want to check that the daemon is running, timevault.py:

$ ps -Af | grep timevault.py
root 7152 1 0 Jul07 ? 00:00:04 python /usr/bin/timevault/timevault.py --verbose

If it was started before DBus was started, then it can't run as a DBus server since it can't connect.

Anyway, try stopping the daemon and restarting from the command line:

sudo /etc/init.d/etc/timevault -stop
sudo /usr/bin/timevault/timevault.py --verbose

Any errors?

Also, there is an error log at /var/log/timevault.py - anything interesting in there?

P.S. The little notification icon shows up in XFCE? I'm actually a little surprised.

Revision history for this message
SourceContact (sourcecontact) said :
#6

I added a TimeVaultPorts page in the wiki, could you do me a favor pls. and post your experience so far on how to get it working in XFCE4.0 on:

https://wiki.ubuntu.com/TimeVaultPorts

Revision history for this message
fsk141 (fsk141) said :
#7

Ello,
Alright when I start up in verbose this is what I get, oh and yes dbus has been started, then the timevault.py. That's how it has been since I got these errors. Anyway this is what I get when I start in verbose...
"
[root@fskspc timevault]# ./timevault.py --verbose
2007-07-08.14-01-22 Reading configuration
2007-07-08.14-01-32 . 10
2007-07-08.14-01-42 . 20
2007-07-08.14-01-52 . 30
2007-07-08.14-02-02 . 40
2007-07-08.14-02-12 . 50
2007-07-08.14-02-22 . 60
2007-07-08.14-02-32 . 70
2007-07-08.14-02-42 . 80
2007-07-08.14-02-52 . 90
2007-07-08.14-03-02 . 100
2007-07-08.14-03-12 . 110
2007-07-08.14-03-22 . 120
2007-07-08.14-03-32 . 130
2007-07-08.14-03-42 . 140
2007-07-08.14-03-52 . 150
2007-07-08.14-04-03 . 161
2007-07-08.14-04-13 . 171
2007-07-08.14-04-23 . 181
2007-07-08.14-04-33 . 191
2007-07-08.14-04-43 . 201
2007-07-08.14-04-53 . 211
2007-07-08.14-05-03 . 221
2007-07-08.14-05-13 . 231
2007-07-08.14-05-23 . 241
2007-07-08.14-05-33 . 251
2007-07-08.14-05-43 . 261
2007-07-08.14-05-53 . 271
2007-07-08.14-06-03 . 281
2007-07-08.14-06-13 . 291
2007-07-08.14-06-23 . 301
2007-07-08.14-06-33 . 311
"

It continues to go incrimentally up, and up. I'm not sure what this is , and why it displays all this, but there are no apparent errors, and the exact same thing is in the log. And the icon, I'm not sure what you talking about when you say icon, so maybe you could clear that up.

Revision history for this message
fsk141 (fsk141) said :
#8

I get a new error when trying to start the timevault daemon...meh...
"
[fsk141@fskspc etc]$ /etc/rc.d/timevault start
Starting TimeVault.../etc/rc.d/timevault: line 22: start-stop-daemon: command not found
 failed!
.
"
I don't even know what the start-stop-daemon is?

Revision history for this message
SourceContact (sourcecontact) said :
#9

Well, the good news is the server is up and running with no errors as indicated from the log you printed (it tics once every 10 seconds when in debug mode). start-stop-daemon is a command-line tool that starts daemons.

You can replace the Makefile with something like the following (at the cost of some reduced functionality):

#!/bin/sh

CMD=/usr/bin/timevault/timevault.py
[ -x $CMD ] || exit 0

case "$1" in
start)
        log_begin_msg "Starting TimeVault..."
        $CMD &
        log_end_msg 0
        ;;
stop)
        log_begin_msg "Stopping TimeVault..."
        killall timevault.py
        log_end_msg 0
        ;;
reload|restart|force-reload)
        $0 stop
        $0 start
        ;;
*)
        echo "Usage: /etc/init.d/timevault {start|stop|restart|force-restart}" >&2
        exit 3
        ;;
esac

exit 0

Revision history for this message
fsk141 (fsk141) said :
#10

Alright, I installed the start-stop-daemon, it was in aur. Yet I still cannot start the damn Notifier...If there's anything you can think of I'm stuck?
Thanks, Jonny

Revision history for this message
SourceContact (sourcecontact) said :
#11

I can't think of anything right now.

If you can't get it, I will try installing XFCE myself and take a look at it - but that I'm afraid that won't happen for a while since I'm really busy trying to get the GNOME version into shape before the application freeze for Gusty.

Revision history for this message
jtp0142 (jtp0142) said :
#12

I get the same thing, KDE 3.5.8 Ubuntu Gutsy (with all updates), TimeVault version 0.7.5 - if you need more information let me know.

Can you help with this problem?

Provide an answer of your own, or ask fsk141 for more information if necessary.

To post a message you must log in.