DHT nodes sometimes drops to 1

Specific support for Deluge on Microsoft Windows OS
Post Reply
funnel
Member
Member
Posts: 30
Joined: Fri Dec 09, 2011 9:31 pm

DHT nodes sometimes drops to 1

Post by funnel »

After leaving Deluge 1.3.1 open for several hours (Windows XP Pro x64), I sometimes find it idle (no connected peers) with only 1 DHT node. Upon restarting Deluge, I return to about 180 nodes (my usual maximum), and transfers resume within a minute or so. I've only been seeding lately, so the transfers I've observed have only been seeding, not downloading. What might cause this drop in nodes to occur? My bandwidth settings are:

Global:
  • Maximum connections: 200
    Maximum upload slots: 4
    Maximum download speed: -1
    Maximum upload speed: 26
    Maximum half-open connections: 8
    Maximum connection attempts per second: 20
(checked) Ignore limits on local network
(checked) Rate limit IP overhead

Per-torrent:
  • Maximum connections: 30
    Maximum upload slots: -1
    Maximum download speed: -1
    Maximum upload speed: -1
I have the blocklist and scheduler plugins active. However, I've not checked whether the drop occurred during any events associated with those plugins. My router's external IP is dynamic, but as far as I know, it hasn't changed while Deluge has been open. I don't know if a dynamic IP would even affect DHT because nodes are added automatically anyway.
funnel
Member
Member
Posts: 30
Joined: Fri Dec 09, 2011 9:31 pm

Re: DHT nodes sometimes drops to 1

Post by funnel »

Sorry. I didn't realise this is more likely a libtorrent issue, not Deluge's.

Just to update for this thread's posterity, my Deluge now has 1 DHT node but is seeding to 2 peers on only one active torrent, and that torrent only has UDP trackers. So, I'm guessing those peers were discovered from the trackers, which seems to suggest the inactivity doesn't affect my entire connection, only DHT.
anonymous_user
Member
Member
Posts: 40
Joined: Sat Jan 31, 2009 7:28 am

DHT nodes sometimes drops to 1

Post by anonymous_user »

sry for resurrecting this dead, old thread,
but the initial post is describing the same problem i´m currently experiencing.
maybe someone has finally found a solution for this issue?!

my situation in detail:
unlike the op, i observed this problem especially during downloads:
freshly opened, deluge starts torrents until the max.number of concurred dls is hit.
these downloads will work until they´re done(which usually takes a few hours),
but as soon as deluge is supposed to start some new downloads from the queue,
it won´t detect any peers anymore cuz dht drops to 1.
upon restart, deluge is able to find peers again and starts downloading the second batch... wth?! :/
this drives me crazy!
pls help guys!!

my specs:
deluge: 1.3.3
libtorrent: 0.15.10.0
running on my raspberry pi (raspbian)
plugins: scheduler, label

EDIT:
sry, just after posting i saw this was posted in winOS...
...maybe someone can help me anyways?!
or should i start a new thread in general support??
http://www.bugmenot.com
Post Reply