(2.9.7) DHT drops to 0 nodes

[James Clarke]

Ive been having an issue with a band new install of 2.9.7 (just switched from uTorrent)

When qTorrent has been left open for a while the number of DHT nodes drops to zero If i try to seed or download anything it wont connect any peers via DHT. If i disable and re enable DHT still nothing, the only way is to shut down the program and start it up again.

Im not sure if this was happening the other times as well but when it happened last time I tried to seed a torrent and it couldnt connect to any of th 4 trackers as well but 1 restart of the program later it connects first time to the trackers and to DHT peers.

Im running Windows 7 64bit and have manually fowarded all the ports on the router DHT also uses a different port but it also happened while using the same port.

Any help will be appreciated

Thanks.

[James Clarke (fragger-unknown)]

Just woken up this morning and found the DHT at 0 nodes after being on all night and a torrent downloaded through RSS stuck at stalled as alll the trackers are down. I tried seeding a torrent that worked fine last night and it too cant contact any of the trackers.

One restart of the program later and both torrents suddenly connect to the trackers and DHT starts finding peers.

[koplop (sot69a)]

I have the same problem. qBittorent Version 2.9.7 win7 64
It connects to peers through DHT with no problem but after a while the number of nodes drops to 0.
I have tried the same things (manually port forward, different port for DHT) but it doesn't seem to help.
When i restart qBittorent it reconnects to DHT with no problem until the same thing happens again after a short period.

[Haldrik (haldrik.cz)]

Having the same problem with qBittorrent 2.9.7 and 2.9.9 on Slackware Linux 13.37 x86_64, qBittorrent downloaded from alienBOB's repos (http://www.slackware.com/~alien/slackbuilds/).

[Zaph0d (nertberble)]

This problem is still present. I'm using v3.0.0 under Windows (both x86 and x64) and without fail I loose all DHT nodes shortly after the client starts up. Closing and restarting qbt resolves the problem temporarily, but not for long. Giving DHT it's own port doesn't help, nor does checking "announce to all trackers" under advanced options. This is discouraging, as this is a good client otherwise.

[Haldrik (haldrik.cz)]

Do we all have big amount of torrents in qBT (like 100+ nonpaused torrents)?

[Dayman (daymansmail)]

I've managed to fix this by reinstalling windows (it died, so that was a nobrainer).
Full log of my struggle: http://qbforums.shiki.hu/index.php?topic=845.0

[Zaph0d (nertberble)]

>> Haldrik:
>> Do we all have big amount of torrents in qBT (like 100+ nonpaused torrents)?

Doesn't make a difference. This happens with only one torrent running just as readily as with hundreds running. It will also happen if no torrents are loaded at all. Simply leave the client running for an hour or so, and it looses all DHT nodes - regardless of how many/few torrents are running.

>> Dayman:
>> I've managed to fix this by reinstalling windows (it died, so that was a

If that proves to be true, and qbt continues to behave for you, it's possible that you may be able to figure out the mystery factor(s) that may be contributing to this. Reinstall and reconfigure your apps slowly, and watch qbt as you do. When you see it start dropping DHT nodes again, let us know what the last software/settings changes you made were. Perhaps we can identify the root cause of this issue.

>> Everyone who's experiencing this issue:

What brand and firmware is everyone using as their router(s)? I've pretty much ruled my router out as the source of this issue, but haven't discarded the possibility entirely. I'm running a Linksys wrt310n using dd-wrt firmware. How about the rest of you? Could be a long shot, but maybe our hardware has something in common. It's worth considering, at least.

[Haldrik (haldrik.cz)]

Its hard for me to repeat this bug right now, in last week qBT dropped nodes one or two times, but some weeks ago it was hard to get some node on start, its inscrutable for me....some days it works fine and rarely drop nodes to zero, some days it starts with zero nodes and cant get more. My router is cheap shit, rarely i have problem with connection and when i reboot router its ok.

TP-LINK WR340G v5 081524C2
Firmware Version: 4.7.8 Build 100920 Rel.50756n

[estienne (steber)]

I have the same problem, but only since I moved from Avast to McAfee. I disable the firewall in McAfee Antivirus plus, but it doesn't do any good - only a restart of qbittorrent solves the problem. So it seems to be something that McAfee does that qbittorrent doesn't like.

I'm a big fan of "freeware", but it seems I will have to go back to utorrent...?!?!?

WRT54G with tomato 1.28.

[estienne (steber)]

Forgot to add details... Win7 with qbittorrent 3.0.0. Had the same problem with previous version + McAfee.

[jake (nichiren)]

Having the same problem as described by others. Running version 3.0.0 on Win7 Pro 64bit. Anti-virus/firewall F-Secure (configured to allow everything not explicitly blocked), with µTorrent DHT works normally.

Also, on the same network another computer running Gentoo and qBittorrent 3.0.1 no problems with DHT. Router is Buffalo WHR-HP-G54 with DD-WRT v24 SP1, though given that µTorrent works on the same computer and Linux qBittorrent behind same router works without a hitch.

[Zaph0d (nertberble)]

I was hoping everyone would end up having the same router, or all be running custom firmware, same NIC, or some other easily identifiable culprit. No such luck. However, I have seen this exact same bahaviour in the client Deluge, which is also built upon libtorrent (their current version uses libtorrent v0.15.10). After running for a couple of hours, it loses connection to all DHT nodes. So I'm thinking this might be a libtorrent issue, and not something that is fixable by the qbt devs. I filed a bug report over at libtorrent.org, so hopefully they'll have some help. I will post anything I learn from them here.

[Zaph0d (nertberble)]

Oops, forgot... here's the link to my bug report to the libtorrent devs for anybody that wants to follow it first hand:

http://code.google.com/p/libtorrent/issues/detail?id=368