torrents sometimes need recheck without giving visual cues

[TheShanMan]

I posted this in the windows section (http://forum.deluge-torrent.org/viewtop ... 12&t=44489) but it doesn't seem to be getting attention over there. Hopefully this is a reasonable place to post this, as it's semi-windows and semi-general in nature.

I *think* I'm having some shutdown problems with deluge running as a service. At least, it's the only thing I can think of to explain my problem. I've been seeing that a torrent site I'm on reports that many of my torrents status are at 0% even though they've long since downloaded fully and successfully, and deluge shows them as "seeding". In other words, deluge gives no indication of a problem, but one of the admins of the torrent site says that deluge is telling them my status is 0%.

If I do a force recheck on the torrents that show as 0%, the torrent site then sees them as complete/seeding. The only thing I can think of is that the service is not shutting down cleanly when I reboot. Is there anything I can do to fix this, and more importantly, if deluge is telling the site that my status is 0%, why won't it give me any indication of a problem?

[TheShanMan]

So no clues on how I can proceed and/or troubleshoot?

[TheShanMan]

Can't anyone help? Troubleshooting tips? Shutdown workarounds? Anything? Rebooting leaves so many of my torrents in some sort of a surreptitiously invalid state. Looking at Deluge's UI you'd think everything is perfectly fine. Everything reports as "seeding". But one torrent site I use indicates that half of my torrents from that site as being in the "downloading" state, and they tell me that's how Deluge is reporting their states. This happens when I reboot my server.

I'm assuming that other sites have similar issues but they just don't report as well as that one site does. So as a result, I have to do a force recheck on all my torrents just to make sure they're all working correctly, and this takes HOURS.

[TheShanMan]

OK, I figured out how to get logging set up and I tried shutting down the daemon from the UI. The daemon never closes. I waited an hour and it was still sitting there. With logging at "info" level I only see this at the end:

[INFO ] 18:51:35 daemon:187 Waiting for components to shutdown..
[INFO ] 18:51:35 server:684 Shutting down webserver

With it at "debug" level I obviously get much more but I'd rather not post it publicly. Nothing jumps out at me but of course with a massive volume of post-shutdown messages and not knowing what I'm looking for, I could be overlooking a key message. I'd be happy to provide the log file to a deluge person privately.

At any rate, I imagine this is why the status of my torrents are getting messed up, but I'm still really troubled by the fact that the UI doesn't tell me which ones are messed up. So not only would I like to find a solution to my shutdown problem, but I'd really like to see an enhancement to deluge so that I can see torrents that aren't seeding properly.

[TheShanMan]

Bump. I wish someone could provide some guidance, acknowledge it as a bug, or something. I absolutely dread the thought of rebooting my machine now because of the many hours required to force recheck everything.

[Ratanak]

Does this issue only occur when you are running Deluge as a service? What happens on the tracker if you pause and then seed again?

I've looked over the code and Deluge seems to do all it can in terms of loading torrents into a libtorrent session. The state of a torrent is immediately retrieved from the session after it has been added. In other words, Deluge will say a torrent is seeding, if libtorrent says it is. I'm not sure if it will solve your problem, but you might want to try updating your libtorrent to a newer version.

[TheShanMan]

I tried pausing and seeding all of the torrents on said tracker and they all showed as properly seeding on that tracker after. I am using it as a service. I'll try running it as a non-service and see if that makes any difference. I'll also look into updating libtorrent. I didn't know there was a library independent of deluge that I could update. Many thanks for the ideas and I'll report back my findings, good, bad, or indifferent.

[TheShanMan]

Running as a non-service didn't seem to help. After rebooting and then re-launching the daemon, the tracker is reporting over half of the torrents as "downloading".

I guess I'll try updating libtorrent next.

Frustrating!

[TheShanMan]

As best as I can tell, "libtorrent.pyd" is what I'd want to replace. Is that right? If so, where do I get it? I can find source code but not the pyd file. Do I *have* to build it? If so, I would be much more inclined to install a beta/alpha/test version of deluge that includes the latest library, with the understanding of course that it could be unstable. Is that possible?

[TheShanMan]

I stumbled across a link for a version of deluge that has a newer libtorrent on http://dev.deluge-torrent.org/ticket/2389. I tried over-installing it but the daemon wouldn't start after. I then tried overinstalling the official 1.3.6 and the daemon still wouldn't start. I then tried restoring my deluge directory from backup, which got me back up and running. I then tried copying the newer libtorrent.pwd into the official 1.3.6 install and the daemon wouldn't start.

Any help on the right way to go about this, assuming it's even possible? Is there something wrong with the build I tried? If so, is there another build I could try? And if not, is over-installing not the proper way to upgrade to a newer version of deluge?