deluge-daemon crashing

[giodamelio]

I am running deluge-daemon on a raspberry pi with arch linux.

Code: Select all

$ uname -a
Linux alarmpi 3.6.11-12-ARCH+ #1 PREEMPT Tue Jun 11 16:09:48 CDT 2013 armv6l GNU/Linux

Code: Select all

$ deluged --version
deluged: 1.3.6
libtorrent: 0.16.10.0

It worked fine for a few days, but now it crashes within a few minutes of being started. Getting its status says it crashed with a seg fault.

Code: Select all

$ systemctl status deluged
deluged.service - Deluge Daemon
   Loaded: loaded (/usr/lib/systemd/system/deluged.service; enabled)
   Active: failed (Result: core-dump) since Sun 2013-07-07 23:40:37 BST; 1 day 19h ago
  Process: 2018 ExecStart=/usr/bin/deluged -d (code=dumped, signal=SEGV)

So I go looking for a log file, and find "/var/log/deluge/deluge", but it is empty. I noticed that above that the ExecStart command starts deluged without the logging option, so I modify "/usr/lib/systemd/system/deluged.service" to include somthing like this "-l /var/log/deluge/deludge.log". Doing that only makes it crash on startup.

So what should I do? I have done pretty much everything I can think of without getting a little more info on the crash. Seeing a detailed log would be nice.

Thanks for your time,
giodamelio

[Spadge]

Does the deluged running account have write access to the /var/log/deluge dir?

Also, if you're telling it to log with -l then also tell it a log level with -L

eg -L debug

Does 1.3.6 support libtorrent 16? I thought we were still having to use 0.15.10

[Cas]

Would need the stack trace for the segfault, it's not a deluge issue so logs wouldn't help.

Does 1.3.6 support libtorrent 16? I thought we were still having to use 0.15.10

It is supported just not recommended as such

[giodamelio]

Not quite sure what caused this, but it does not matter any more, I switched os's on my pi, and since then deluge-daemon has been working like a charm.

[Moustacha]

I'm getting similar things on raspbian with deluge daemon. It silently crashes after a while. The log level was warning, but I've increased it to info, and there's still nothing in the log about why it's crashed.

Code: Select all

$ deluged --version
deluged: 1.3.6-dev
libtorrent: 0.15.10.0

What can I do to try and track down this bug?

[Raptus]

I'm also experiencing frequent crashes.

Code: Select all

Linux 3.8.0-31-generic #46~precise1-Ubuntu SMP Wed Sep 11 18:21:16 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

Code: Select all

deluged: 1.3.6
libtorrent: 0.15.10.0

Deluge log shows nothing interesting. Syslog however:

Code: Select all

Oct 19 09:30:55 kernel: [1609266.014706] deluged[10317]: segfault at 682e000 ip 00007ff4130a897d sp 00007ff40ef62fa0 error 4 in libcrypto.so.1.0.0[7ff41301f000+1b1000]
Oct 19 10:52:30 kernel: [1614158.304289] deluged[10390]: segfault at 6e27000 ip 00007ff1783e097d sp 00007ff17429b370 error 4 in libcrypto.so.1.0.0[7ff178357000+1b1000]
Oct 19 11:32:11 kernel: [1616537.485769] deluged[11129]: segfault at 5c80000 ip 00007f03d0a4297d sp 00007f03cc8fcfa0 error 4 in libcrypto.so.1.0.0[7f03d09b9000+1b1000]
Oct 19 11:35:11 kernel: [1616717.445099] traps: deluged[11163] general protection ip:560d38 sp:7fff8386ff50 error:0 in python2.7[400000+270000]
Oct 19 11:36:28 kernel: [1616794.092226] deluged[11211]: segfault at 6795000 ip 00007f0dc131c97d sp 00007f0dbd1d7370 error 4 in libcrypto.so.1.0.0[7f0dc1293000+1b1000]
Oct 19 11:53:43 kernel: [1617829.039347] deluged[11244]: segfault at 656a000 ip 00007f8bf1e0a97d sp 00007f8bedcc4fa0 error 4 in libcrypto.so.1.0.0[7f8bf1d81000+1b1000]
Oct 19 11:56:09 kernel: [1617975.012051] deluged[11463]: segfault at 5276000 ip 00007fd1d157d97d sp 00007fd1cd437fa0 error 4 in libcrypto.so.1.0.0[7fd1d14f4000+1b1000]
Oct 19 11:58:00 kernel: [1618085.393532] traps: deluged[11499] general protection ip:553ed0 sp:7fff5340e4c0 error:0 in python2.7[400000+270000]
Oct 19 11:59:55 kernel: [1618200.777439] deluged[11516]: segfault at 5538000 ip 00007ff6f500197d sp 00007ff6f0ebbfa0 error 4 in libcrypto.so.1.0.0[7ff6f4f78000+1b1000]
Oct 19 12:02:06 kernel: [1618331.654462] deluged[11527]: segfault at 58c8000 ip 00007f53133bc97d sp 00007f530f276fa0 error 4 in libcrypto.so.1.0.0[7f5313333000+1b1000]
Oct 19 12:06:00 kernel: [1618565.814983] deluged[11570]: segfault at 6fe7000 ip 00007f454782097d sp 00007f45436dafa0 error 4 in libcrypto.so.1.0.0[7f4547797000+1b1000]
Oct 19 12:13:54 kernel: [1619039.084359] deluged[11611]: segfault at 622c000 ip 00007f92251cb97d sp 00007f9221085fa0 error 4 in libcrypto.so.1.0.0[7f9225142000+1b1000]
Oct 19 12:17:25 kernel: [1619250.034393] traps: deluged[11652] general protection ip:553ed0 sp:7fffde7d3b90 error:0 in python2.7[400000+270000]
Oct 19 12:19:06 kernel: [1619351.516707] traps: deluged[11698] general protection ip:4b2f46 sp:7fffd2e05520 error:0 in python2.7[400000+270000]
Oct 19 12:20:28 kernel: [1619433.129397] deluged[11714]: segfault at 6483000 ip 00007f431c3f397d sp 00007f43182ae370 error 4 in libcrypto.so.1.0.0[7f431c36a000+1b1000]
Oct 19 12:22:02 kernel: [1619527.417632] deluged[11752]: segfault at 6d75000 ip 00007f83bd5d297d sp 00007f83b948cfa0 error 4 in libcrypto.so.1.0.0[7f83bd549000+1b1000]
Oct 19 12:27:25 kernel: [1619849.763513] deluged[11779]: segfault at 6717000 ip 00007f4d6be1b97d sp 00007f4d67cd6370 error 4 in libcrypto.so.1.0.0[7f4d6bd92000+1b1000]

[xareth]

I am also experiencing silent Deluge crashes with my Raspberry Pi. Almost every time I try and login the daemon has crashed. Would be interested if anybody has managed to solve this.

Code: Select all

Linux 3.6.11+ #538 PREEMPT Fri Aug 30 20:42:08 BST 2013 armv6l

Code: Select all

deluged: 1.3.3
libtorrent: 0.15.10.0

My /var/log/deluged.log shows nothing interesting. The last few entries before crashing shows a failed hash check for one piece and deluged banning an IP. Normal stuff. My /var/log/syslog also shows nothing interesting (no segfault).

Its not my network interface falling over. Throughout the process (before and after 'crash') I can SSH to the Pi and access Samba shares. Restarting the deluged process returns everything to normal.

There doesn't seem to be a specific speed or number of peers that triggers the crash however I do feel crashes are more frequent under heavier load.

[Cas]

If you can install the latest 0.16 libtorrent it doesn't seem to trigger this bug.

[xareth]

Thanks Cas
That's a big IF. Unfortunately, it seems I don't have the necessary skills. I assumed I'd have to compile 1.3.6 and 0.16.11 from source, since apt-get update/upgrade leaves me with 1.3.3 and 0.15.10 and Google didn't turn up any better ideas.
I tried following the forum post here mainly because it's a deluge user compiling 0.16.11 and the instructions resembled the libtorrent build instructions. I didn't have boost installed and got stuck on the line

Code: Select all

./configure --enable-python-binding

After installing libboost-dev I get

Code: Select all

Checking for boost libraries:
checking for boostlib >= 1.36... yes
checking whether the Boost::System library is available... yes
checking for exit in -lboost_system... no
configure: error: Could not link against boost_system !

Ill pick this up tomorrow. Its time for bed.
Should I try and "link against boost-system" tomorrow? Or is there an easier way to get libtorrent 0.16.x on Raspbian Wheezy?

[Cas]

You should actually be able to use the libtorrent from this PPA: https://launchpad.net/~surfernsk/+archi ... t-software

Adapt these instructions for the above PPA: http://dev.deluge-torrent.org/wiki/Inst ... ian/Wheezy