Deluge Keeps Queuing Torrents

[macro_]

Hello,

I've recently setup Deluge and the webui in Ubuntu. I'm running 1.2.1 /w libtorrent 0.14.9.0 /w Ubuntu 9.10. The webui is not responding after I add a magnet link url from the web site (separate issue) so I VNC into the server, click Add URL, add my magnet links and hit go. I'm using TPB.org

After about an hour or so I'll check and all my torrents are "Queued". It doesn't matter if I have 1 torrent running, or 10, for some reason they just go into a "Queue" state. So I go to Edit -> Preferences -> Hit "Apply" and "OK" without changing a single setting, and they all fire back up for a while.

In my Queue section I've tried setting everything under Seeding to 0, I've tried raising the numbers as high as they go. I've tried setting everything at the top different and it doesn't seem to help. I started with 10 active, 5 downloading, 3 seeding, but i've slowly increased it over time to see if it would make a difference and it does not. For some reason they just randomly stop. To be even more confusing I've noticed they will randomly start back up after 12 hours or so, then stop themselves in an hour or so.

I'm not a huge linux guy, so I haven't tweaked with any settings behind the scenes. I've simply set a folder for finished torrents to move to (which works sometimes, sometimes not), I've set the Incoming and Outgoing ports to a different port and that's about it. Here's a screenshot of my Queue section right now:


Also here's my bandwidth section:


I thought maybe this was a temporary thing so I've rebooted a couple times now, and waited a week but it's still doing it.

Any reason why my torrents are automatically queuing themselves?

[johnnyg]

What does your queue page look like?

[macro_]

I posted a screenshot of the queue section above.

Is there a way to disable queue altogether?

[macro_]

Just wanted to note this is still happening. I started a couple downloads just now, within 30 minutes they are back to queue status. Maybe there is some type of debug logging I can turn on?

[Cas]

http://dev.deluge-torrent.org/wiki/Faq

[macro_]

I started up with debugging enabled and the torrents were queued. I went to options and hit OK, they started back up. After about 10 minutes they all went to queued again. I started all them back up and closed out.

Here are some of the warnings that I saw. There were about 4 or 5 groups of these with different names:

Code: Select all

[WARNING ] 19:49:34 torrentmanager:289 Unable to open /home/jordan/.config/deluge/state/1efefa8375fffe36e85372454310ebc29180c502.torrent: [Errno 2] No such file or directory: '/home/jordan/.config/deluge/state/1efefa8375fffe36e85372454310ebc29180c502.torrent'
[WARNING ] 19:49:34 torrentmanager:314 Unable to delete the fastresume file: [Errno 2] No such file or directory: '/home/jordan/.config/deluge/state/1efefa8375fffe36e85372454310ebc29180c502.fastresume'

Later in the log is where I believe I started them back up because I see many of these types of messages:

Code: Select all

[DEBUG   ] 19:49:34 rpcserver:409 intevents: {}
[DEBUG   ] 19:49:34 torrentmanager:832 on_alert_torrent_checked
[DEBUG   ] 19:49:34 torrent:337 set_state_based_on_ltstate: Downloading

I see many of these:

Code: Select all

[DEBUG   ] 19:49:34 torrentmanager:943 on_alert_save_resume_data_failed: TORRENT HERE resume data was not generated: save resume data failed, torrent is being destructed
[DEBUG   ] 19:49:34 torrentmanager:943 on_alert_save_resume_data_failed: TORRENT HERE resume data was not generated: save resume data failed, torrent is being destructed
[DEBUG   ] 19:49:34 torrentmanager:925 on_alert_save_resume_data

I also see many of these:

Code: Select all

[WARNING ] 19:50:15 config:405 Unable to open config file: /home/jordan/.config/deluge/web.conf

Some of these:

Code: Select all

[DEBUG   ] 19:55:03 alertmanager:115 performance_alert: TORRENT HERE: performance warning: max outstanding disk writes reached
[DEBUG   ] 19:55:54 alertmanager:115 save_resume_data_failed_alert: TORRENT HERE resume data was not generated: save resume data failed, torrent is being destructed

After that we get a lot of stopped commands sent to the tracker. Is this a disk write problem?

[macro_]

I'll also note I run a 3ware raid controller, with a mirror raid of 1tb hard drives. I increased my cache a huge amount. I'm not sure if it is helping or not.

[Cas]

if you are happy building from source you may want to try Deluge 1.2.3 with Libtorrent-RB 0.15 as this may resolve the 'max outstanding disk writes reached' issue.

[macro_]

I'll probably end up making things worse lol . I'll wait until a build gets released that I can install and we'll see I guess.

[Spaceboy]

I'n having similar issue with 1.2.3. Deluge Keeps Queuing Torrents after a few hours.

Can't get Deluge to run in debug mode. With Debug mode on Win Task Manager shows Deluge*32 as running, but the UI never starts up.