iyear
Get item failed: rpcDoRequest: engine was closed, skip...
happens randomly . reopening tdl immediately downloads will resume from the start. i am unsure if some limiter is activating since with no cool down period i can reopen and continue normally only to happen again after some time. when this occur downloads will stall and a few minutes after this stalled state it will abort.
What is your thread size? An excessive number of threads will cause the connection to be closed by the Telegram server.
I tried -t 8 -s 262144 -l 4 , -t 4 -s 262144 -l 4 , -t 4 -s 131072 -l 4 , -t 4 -s 262144 -l 2 . test 2 groups with large files . what i noticed is the engine closes at the same amount downloaded let say 50 files. reopening tdl right back not even 30 sec delay downloads start right up but since tdl has no history of what was downloaded in the prior session it just start downloading from the beginning again just for the engine to close again around the same amount of files. i thought maybe since it stops consistently in the around the same stop there where something about a file causing the issue so i tried a different group different files same effect. Since right after the engine closed i can reopen and it continues normally it doesn't seem like a limiter. Do you need me to gather anymore info Just let me know. do you recommend me a setting to test?
I've had this happen before in a very poor network environment, and I'm not sure what the possible causes are at the moment...