You are not logged in.
Pages: 1
hi
i have 2 arch boxes both with deluge, after performing an update on both machines one can no longer start deluged
Traceback (most recent call last):
File "/usr/bin/deluged", line 8, in <module>
load_entry_point('deluge==1.1.2', 'console_scripts', 'deluged')()
File "/usr/lib/python2.6/site-packages/deluge/main.py", line 203, in start_daemon
Daemon(options, args)
File "/usr/lib/python2.6/site-packages/deluge/core/daemon.py", line 44, in __init__
self.core = Core(options.port).run()
File "/usr/lib/python2.6/site-packages/deluge/core/core.py", line 168, in run
self.session = lt.session(fingerprint, flags=0)
RuntimeError: eventfd_select_interrupter: Function not implemented
the only differnce between the 2 boxes that i know off is that the box that deluged refuses to start on has a custom kernel 2.6.24 with openvz patches
any ideas?
Offline
There's a thread about this , might help
* Index
* » Newbie Corner
* » Deluge stopped working, runs only as root [SOLVED]
Last edited by michaelks (2009-02-15 22:46:21)
Offline
yes i saw that post as i did a search before creating a new thread
i created a new thread as my problem is not related to the problem in the other thread.
permisions are fine and both boxes were upgraded from the same version of deluge so there should there should be no issue with existing configuratoin (which i do not want to delete)
for shits and giggles though i tried moving my configs, after launching deluged it creates a new empty config directory and fails with the same errors.
Last edited by SomeGuy1337 (2009-02-16 07:53:34)
Offline
tried boost 1.38 no luck
ill have to give the svn version a go
Offline
Take a look at the deluge changelog:
- Fix issue when initializing gettext that would prevent deluge from starting
Offline
I spent the better part of a whole weekend trying to resolve this, and what i found out is that deluge, after a new install, will only create ~/.config/deluge after it is started . I read about deleting this folder as a solution to the problem in the case that deluge would have been started as root, and therefore /root/.config/deluge would have been created. Since in my case i could only start it as root, there was no permission problem to ~/.config/deluge to speak of. So finally i found that doing sudo deluge would create that file, albeit with root permissions, and changing those solved the problem. I suggest you delete ~/.config/deluge, reinstall and maybe you'll have the same situation.
Offline
I had the same problem. I just deleted the ~/.config/deluge directory and it started working fine
Offline
Pages: 1