Deluge daemon crashes when heavy downloading
Posted: Sat Oct 03, 2015 12:43 pm
I've had deluged crashing a few times within 24 hours now, so I decided to log it and then put it here on the forum.
Using deluged: 1.3.10, libtorrent: 0.16.13.0
Running on: Debian Jessie
Plugin activated: ltconfig
The situation:
I'm running Deluge daemon 24/7 on a home server. I barely have problems (except for already known performance issues when seeding lot of torrents). However when I am heavy downloading, multiple torrents at about 3 MB/s, then after some time deluged stops running. There is no problem with any other program, only deluged is effected (not even deluge-console, which just keeps running). Sometimes this happens after 30 minutes, sometimes after 10 hours of heavy downloading. I just have to restart deluged and then it picks up where it left.
Apparently it has something to do with a division by zero in the kernel?
This is the dmesg log from the time deluge suddenly stops:
I was also logging deluged in debug mode, but the log shows nothing special. These are the last lines of the debug log:
After that nothing. I'm quite new to UNIX based OS's, so I have no idea whatsoever what could have caused this.
Please have a look at it
For now I will just check often whether deluged is running or not and restart it if necessary.
Using deluged: 1.3.10, libtorrent: 0.16.13.0
Running on: Debian Jessie
Plugin activated: ltconfig
The situation:
I'm running Deluge daemon 24/7 on a home server. I barely have problems (except for already known performance issues when seeding lot of torrents). However when I am heavy downloading, multiple torrents at about 3 MB/s, then after some time deluged stops running. There is no problem with any other program, only deluged is effected (not even deluge-console, which just keeps running). Sometimes this happens after 30 minutes, sometimes after 10 hours of heavy downloading. I just have to restart deluged and then it picks up where it left.
Apparently it has something to do with a division by zero in the kernel?
This is the dmesg log from the time deluge suddenly stops:
Code: Select all
[516743.739377] Division by zero in kernel.
[516743.746540] [<c0014dd8>] (unwind_backtrace+0x0/0x138) from [<c02c1c78>] (Ldiv0+0x8/0x10)
[516743.764015] [<c02c1c78>] (Ldiv0+0x8/0x10) from [<c00e3dc0>] (vmpressure_work_fn+0x60/0x174)
[516743.782433] [<c00e3dc0>] (vmpressure_work_fn+0x60/0x174) from [<c004adcc>] (process_one_work+0x118/0x388)
[516743.792226] [<c004adcc>] (process_one_work+0x118/0x388) from [<c004b3b4>] (worker_thread+0x174/0x374)
[516743.803898] [<c004b3b4>] (worker_thread+0x174/0x374) from [<c004f9b8>] (kthread+0x84/0x90)
[516743.811648] [<c004f9b8>] (kthread+0x84/0x90) from [<c000f49c>] (kernel_thread_exit+0x0/0x8)
[516743.829335] Division by zero in kernel.
[516743.836405] [<c0014dd8>] (unwind_backtrace+0x0/0x138) from [<c02c1c78>] (Ldiv0+0x8/0x10)
[516743.853888] [<c02c1c78>] (Ldiv0+0x8/0x10) from [<c00e3dd4>] (vmpressure_work_fn+0x74/0x174)
[516743.862732] [<c00e3dd4>] (vmpressure_work_fn+0x74/0x174) from [<c004adcc>] (process_one_work+0x118/0x388)
[516743.871337] [<c004adcc>] (process_one_work+0x118/0x388) from [<c004b3b4>] (worker_thread+0x174/0x374)
[516743.878848] [<c004b3b4>] (worker_thread+0x174/0x374) from [<c004f9b8>] (kthread+0x84/0x90)
[516743.886637] [<c004f9b8>] (kthread+0x84/0x90) from [<c000f49c>] (kernel_thread_exit+0x0/0x8)
Code: Select all
[DEBUG ] 14:22:08 alertmanager:123 portmap_log_alert: UPnP: HTTP method m-search from 192.168.178.44:64648
[DEBUG ] 14:22:11 alertmanager:123 portmap_log_alert: UPnP: HTTP method m-search from 192.168.178.44:64648
Please have a look at it
For now I will just check often whether deluged is running or not and restart it if necessary.