Custom Query (2449 matches)

This will sadly require libtorrent 0.16 in order to work (because that release adds port-reusing and forced ports ​http://code.google.com/p/libtorrent/issues/detail?id=305), but it would be a MAJOR improvement to Deluge, for multiple reasons:

• A static port is best for DHT, because old clients will be lookng for you at your last-known IP and port, which is why clients like uTorrent have a single port setting.

• Your router will be getting requests to old ports and will fill its logs with "UDP blocked" messages, similar to a Denial of Service attack, which can actually crash lower specced routers.

Once Deluge works well with libtorrent 0.16, it really would be worth looking into defaulting to a single, static port, randomly selected on config file generation.

Requesting a single port is easy in 0.16; see the libtorrent bug tracker link above. You just pass in two flags to tell it to re-use the port even if it's in TIME_WAIT state (the state just before it is freed by the system) and to disallow the system from choosing another port at random. It'll also require a small check that says "the only port we wanted is in use? okay, don't start the daemon, instead log a fatal error"

Deluge 0.6.0.0r3225

resuming a paused seeding torrent fails, pausing a single seeding torrent just gives out:

[DEBUG   ] toolbar:151 on_toolbutton_resume_clicked
[DEBUG   ] menubar:222 on_menuitem_resume_activate
[DEBUG   ] core:395 Resuming: ['dcab4cf8c0a58754a2c8ebf81d1de3be31b4e06b']
[DEBUG   ] core:607 torrent_resumed signal emitted
[DEBUG   ] signals:97 torrent_resumed signal received..

no error but with resume all:

systemtray:276 on_menuitem_resume_all_activate
[WARNING ] torrentmanager:436 Unable to resume torrent 5c236425e2e61d22a8dabd4657ecfa36a0775704
[WARNING ] torrentmanager:436 Unable to resume torrent 409b686058f03fb03779a440e31bbf5732250680
[WARNING ] torrentmanager:436 Unable to resume torrent d4e0c3f10ee07b78f4c66c6b34066a4305daabce
[WARNING ] torrentmanager:436 Unable to resume torrent a2180cd9c41e439c23fb891ef2c6779ec3c0c2b8
[WARNING ] torrentmanager:436 Unable to resume torrent 62c6b0b1c2531f68acae6921f09883d101d25055
[DEBUG   ] core:617 torrent_all_resumed signal emitted
[DEBUG   ] signals:107 torrent_all_resumed signal received..

the 3rd torrent is the one paused, 4th is queued for downloading, 2nd is seeding and the remaining 2 are downloading

also when you add a torrent that was already completed for seeding, if during the check it gets in the download queue, when the check completes torrent resumes seeding as expected, but if the queue is empty or not full, while checking the torrent is in paused state and when the check completes the torrent remains paused, it's probably related with the above problem of resuming seeding torrents

On startup, after all torrents have been loaded, Deluge will start re-saving resume data, for each torrent individually. With 800 torrents this makes Deluge unresponsive for 2 minutes for me.

This is caused by all torrents getting paused and unpaused, or at least the respective alerts being emitted. Deluge saves resume data in on_alert_torrent_paused.

The proper way to fix this should be to prevent those alerts.