Deluge Forum

I think this must be a bug in one of the more recent libtorrent commits. It was working just fine for me with libtorrent 1.2.3 a few weeks ago. It only started happening after I upgraded using mhertz's most recent (01-Feb-2020) installer.

I'm not sure it's worth rebuilding the installer for each commit, since each commit may or may not result in an overall stable libtorrent build.

Sorry for the repeated messages - but in case anyone is interested in previous builds of the installer - it looks like you can select the current version of the file (select, not download) and then a "version history" option appears. I'm going to test a few of the previous builds to see if I can find the most recent one where this error goes away.

So I went from getting hundreds of tracker errors per hour with the most recent installer, to 0 tracker errors in the last 90 minutes with the installer from January 7th.

It's possible a more recent installer would also work. I'm not savvy enough to know which libtorrent commit introduced the issue, or if something could have been changed in the installer itself that caused it.

Thanks for reporting and investigating, appreciated.

If wanted, then here's libtorrent 1.2.3, which is the same since 1.2.3 was added first. Overwrite libtorrent.pyd in '<INSTALL-DIR>\Lib\site-packages' folder. If getting an error when starting deluge again, then delete session.state in deluge config dir under '%appdata%\deluge'.

http://s000.tinyupload.com/index.php?fi ... 6991545754

Could you also please run at a time when having time, no hurry of-course, a debug-run using the problematic libtorrent.pyd and see if can catch the error to get further data:

To enable debug-logging for deluge, then copy the following and press: win+r > ctrl+v > return. The log(deluge.log) is saved to your desktop when quiting deluge again and is overwritten on each run also.

Code: Select all

"%programfiles%\Deluge\deluge.exe" -L debug -l "%userprofile%\Desktop\deluge.log"

(Change path if needed.)

About the error you got, then nothing on deluge or libtorrent, but a wealth of other reports of same error on countless apps, with varying reasons, usually write/permission errors, problematic folder/file-name, too little free space etc.

I'll check the commit list through also, to see if there are any "suspecious looking commits", there where a few commits added today or yesterday, so I was gonna rebuild soon, but don't seem like addressing any such issue from reading the last few commits from the commit-log unfortunetly.

I myself can not really see the error, but am only testing shortly, as not using Windows personally.

Good luck!

Edit: January 7'th where libtorrent 1.2.3 stable, as linked above. Thanks for report, i'll test some more on my side to see if can also catch this error myself.

If it helps, I have 2000+ torrents in the client, so it could be that the problem does not appear until there is a high volume.

Thanks. Btw, my script just finished building/uploading rebuilt installers for the last few commits of libtorrent 1.2.x, but I don't think it fixes your issue unfortunetly I'll test some more on my end, probably first tomorow as midnight here and I need early up in morning.

Hitrun30, sorry, I completely missed your post, must have scrolled to quick or something

As per official documentation, please use debug exe's for nssm services.

Can you manually install plugins i.e move plugin to plugins folder in deluge config folder and rename plugin if needed to have 37 in name, instead of 36 or 38 etc. Then try enable plugin in deluge afterwards and see if working.

If still having issues, please tell me plugin and I'll test myself also.

Vander, I read through all 64 commits added since last libtorrent 1.2.3 release, and it didn't sound to me like anything that would result in your issue, though that is hard to gauge of-course. There's no issues reports(bug-tickets) reporting your issue either. I cannot reproduce your issue either, with a few linux iso's running for some time, granted not testing 2000 either.

I did read on both utorrent and qbittorrent old posts about errors often of files not found, and it was reported to be either to long path, or in some cases to much going on at once(I/O) or using a drive not quick enough for the throughput. In qbittorrent there's currently an open issue of error's of files not found on windows machines.

Anyway, sorry I couldn't be of help to your issue, and based on everything above, then I will not change away from RC branch.

@all, If wanted, then here's latest stable releases of libtorrent for manual replacement yourself:

Libtorrent 1.2.3:
http://s000.tinyupload.com/index.php?fi ... 6991545754

Libtorrent 1.1.14:
http://s000.tinyupload.com/index.php?fi ... 3532988470

Extract and overwrite libtorrent.pyd in '<INSTALL-DIR>\Lib\site-packages' folder. If getting an error when starting deluge again, then delete session.state in deluge config folder under '%appdata%\deluge'.

Just a quick update - I haven't had a chance to install any other versions, but I did want to let you know that it's been running flawlessly without even the smallest hiccup. This includes the daemon running on my server with 2500+ torrents, the thin client from my desktop/laptop and even the web client works perfectly. All my plugins are working in every interface as well.

Appreciate the update Vander, and good to hear you found a version vorking for you. I'm honestly thinking if should change to stable releases of libtorrent, or add extra checkboxes for it, or add RC libtorrent only to deluge git-develop installer. I dunno really, will have to think some more of it, as some prefer newest fixes and others, release versions, possibly more stable. If changing anything, and a big if, then it will be changing to release versions(checking out release tags instead of RC branch), as too many checkboxes as is(I previously had to copy/paste some obscure win32 api system calls assembly looking code function into my NSIS script to make room for them all without showing scroolbar, for easy overlook, because so many), and only adding RC libtorrent to deluge git installer isn't something I think I'll do either.