I've been running Deluge for a couple of years now. For the last 6-8 months (or so) it has been stopping on me and I keep having to re-start the daemon. When I ran it in classic mode I never had any problems. About 1 year ago I switched to using Flexget which required me to run the daemon. At first it worked well, but then later it started crashing on me. The daemon will just periodically stop. Sometimes it happens within seconds, other times it happens hours after starting Deluge. I've tried watching it, but there is nothing that seems to be glaring to me. I downgraded libtorrent to 0.15.10.0 and am running the latest release of deluge.
I've searched for hours and can't find a solution. I would appreciate it if someone could help me figure this out.
Here is my ~/.config/deluge/core.confhttp://pastebin.com/yLm5LKi4
Here is my ~/.config/deluge/deluged.loghttp://pastebin.com/BKstSLFP
Deluge daemon stopping frequently
-
- Member
- Posts: 11
- Joined: Tue Mar 20, 2012 1:57 pm
Deluge daemon stopping frequently
Mint Linux 13
Deluge 1.3.6
Deluge 1.3.6
Re: Deluge daemon stopping frequently
a
Last edited by ViperSBT on Wed Sep 18, 2013 5:11 pm, edited 1 time in total.
Re: Deluge daemon stopping frequently
And for the record there isn't anything tying up the port already:
# nmap -sT -O localhost
Starting Nmap 6.40 ( http://nmap.org ) at 2013-09-18 12:33 CDT
Nmap scan report for localhost (127.0.0.1)
Host is up (0.00040s latency).
Other addresses for localhost (not scanned): 127.0.0.1
Not shown: 990 closed ports
PORT STATE SERVICE
22/tcp open ssh
25/tcp open smtp
80/tcp open http
111/tcp open rpcbind
139/tcp open netbios-ssn
445/tcp open microsoft-ds
631/tcp open ipp
3306/tcp open mysql
6543/tcp open mythtv
6547/tcp open powerchuteplus
Device type: general purpose
Running: Linux 3.X
OS CPE: cpe:/o:linux:linux_kernel:3
OS details: Linux 3.7 - 3.9
Network Distance: 0 hops
OS detection performed. Please report any incorrect results at http://nmap.org/submit/ .
Nmap done: 1 IP address (1 host up) scanned in 2.20 seconds
# nmap -sT -O localhost
Starting Nmap 6.40 ( http://nmap.org ) at 2013-09-18 12:33 CDT
Nmap scan report for localhost (127.0.0.1)
Host is up (0.00040s latency).
Other addresses for localhost (not scanned): 127.0.0.1
Not shown: 990 closed ports
PORT STATE SERVICE
22/tcp open ssh
25/tcp open smtp
80/tcp open http
111/tcp open rpcbind
139/tcp open netbios-ssn
445/tcp open microsoft-ds
631/tcp open ipp
3306/tcp open mysql
6543/tcp open mythtv
6547/tcp open powerchuteplus
Device type: general purpose
Running: Linux 3.X
OS CPE: cpe:/o:linux:linux_kernel:3
OS details: Linux 3.7 - 3.9
Network Distance: 0 hops
OS detection performed. Please report any incorrect results at http://nmap.org/submit/ .
Nmap done: 1 IP address (1 host up) scanned in 2.20 seconds
-
- Member
- Posts: 11
- Joined: Tue Mar 20, 2012 1:57 pm
Re: Deluge daemon stopping frequently
I personally think that the issue is caused by deluged crashing and not properly closing the port. I might be completely off base on that but I have no knowledge of how to debug this. I would appreciate any help I can get.
Mint Linux 13
Deluge 1.3.6
Deluge 1.3.6
Re: Deluge daemon stopping frequently
Even on a fresh boot, where the port should be clear, it does the same thing.
-
- Member
- Posts: 11
- Joined: Tue Mar 20, 2012 1:57 pm
Re: Deluge daemon stopping frequently
What do you mean 'stopping', is deluged crashing, if so you need a backtrace. Without any more info I suspect it might be the libcrypto bug.
-
- Member
- Posts: 11
- Joined: Tue Mar 20, 2012 1:57 pm
Re: Deluge daemon stopping frequently
I don't know how to "backtrace". I'm not sure what is happening. Most times it works by me clicking on "Start Daemon" and other times I have to go into the shell and kill the deluged process and then start it again.
How do I backtrace it?
How do I backtrace it?
Mint Linux 13
Deluge 1.3.6
Deluge 1.3.6
Re: Deluge daemon stopping frequently
First attempt at creating backtrace, but in doing so, it never seemed to actually crash where I could issue the command to create the backtrace...Cas wrote:What do you mean 'stopping', is deluged crashing, if so you need a backtrace. Without any more info I suspect it might be the libcrypto bug.
Code: Select all
$ gdb --args python /usr/bin/deluged -d
GNU gdb (GDB) Fedora (7.5.1-38.fc18)
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/bin/python...Reading symbols from /usr/lib/debug/usr/bin/python2.7.debug...done.
done.
(gdb) run
Starting program: /usr/bin/python /usr/bin/deluged -d
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Detaching after fork from child process 11467.
[New Thread 0x7fffec1a2700 (LWP 11469)]
[New Thread 0x7fffeb9a1700 (LWP 11470)]
[ERROR ] 10:18:29 init:50 Unable to enable plugin!
[ERROR ] 10:18:29 init:51 Couldn't listen on any:8112: [Errno 98] Address already in use.
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/deluge/plugins/init.py", line 48, in enable
self.plugin.enable()
File "/usr/lib/python2.7/site-packages/deluge/plugins/WebUi-0.1-py2.7.egg/webui/core.py", line 59, in enable
self.start()
File "/usr/lib/python2.7/site-packages/deluge/plugins/WebUi-0.1-py2.7.egg/webui/core.py", line 97, in start
self.server.start(False)
File "/usr/lib/python2.7/site-packages/deluge/ui/web/server.py", line 665, in start
self.start_normal()
File "/usr/lib/python2.7/site-packages/deluge/ui/web/server.py", line 673, in start_normal
self.socket = reactor.listenTCP(self.port, self.site)
File "/usr/lib64/python2.7/site-packages/twisted/internet/posixbase.py", line 464, in listenTCP
p.startListening()
File "/usr/lib64/python2.7/site-packages/twisted/internet/tcp.py", line 927, in startListening
raise CannotListenError, (self.interface, self.port, le)
CannotListenError: Couldn't listen on any:8112: [Errno 98] Address already in use.
[New Thread 0x7fffea739700 (LWP 11471)]
[New Thread 0x7fffe9d31700 (LWP 11472)]