Recheck on startup - hours of wasted time.
Posted: Sat Feb 06, 2021 5:40 pm
I have two Deluge server instances setup on my Windows server. One is for seeding to private trackers and one is for seeding to public.
I have some very large torrents on my private trackers (~500 GB) and to check these torrents takes maybe 20-30 minutes each.
Every time my server shuts down these need to be rechecked, which is a manual process (since the torrents start in "error" state) and takes at least an hour each time.
I found this thread here:
viewtopic.php?t=44489
But I'm not taking anything new away from it. I believe my deluged-consol.exe nssm service is setup properly. On a Windows shutdown command each service should be receiving a shutdown command from the system and should then nssm should issue a CTRL-C to the console (the only command that I was able to get it to terminate).
I have a 60 second timeout set which is 40x greater than the default (1500 ms). I have no way to know what an acceptable shutdown period should be, but over a minute seems excessive for deluge to do whatever it needs to to ensure that a seed is properly shut down.
Can I have some input as to why this is happening, or what an acceptable shut down time frame should be (and why it needs to be so long)?
I've attached my NSSM screens for review.
I have some very large torrents on my private trackers (~500 GB) and to check these torrents takes maybe 20-30 minutes each.
Every time my server shuts down these need to be rechecked, which is a manual process (since the torrents start in "error" state) and takes at least an hour each time.
I found this thread here:
viewtopic.php?t=44489
But I'm not taking anything new away from it. I believe my deluged-consol.exe nssm service is setup properly. On a Windows shutdown command each service should be receiving a shutdown command from the system and should then nssm should issue a CTRL-C to the console (the only command that I was able to get it to terminate).
I have a 60 second timeout set which is 40x greater than the default (1500 ms). I have no way to know what an acceptable shutdown period should be, but over a minute seems excessive for deluge to do whatever it needs to to ensure that a seed is properly shut down.
Can I have some input as to why this is happening, or what an acceptable shut down time frame should be (and why it needs to be so long)?
I've attached my NSSM screens for review.