I have noticed that when drone adds a file to the torrent client (i use deluge) i get this error:
The file still gets added to the queue
Yes, we’ve been getting reports of timeout issues on the Deluge api. Still not sure what’s causing it.
But Myth is looking into supporting the Daemon RPC (binary format) instead of the WebUI JSON RPC.
Still I should probably check why the Deluge JSON api is having timeouts.
cool to know.Does this effect functionality?
Dont know if this can help but i just added 2 shows to my deluge and got the error. The shows were added in a paused stated because i have my client on a schedule.
Hard to say, if it’s permanent then drone won’t be able to communicate with Deluge and can’t queue new downloads or import existing ones.
The funny thing is that on utorrent it didnt seem to be a issue that the torrents were added in a pause state because of scheduler
With the indexer refactor pretty much done and an available weekend, I had some time to investigate this.
If you change certain settings in deluge it actually restarts it’s internal rpc server, which causes the separate web-api to lose it’s connection to the rpc server.
Drone connects to the web-api and is oblivious to the lost connection. Instead of returning a “connection lost” error, the web-api actually just hangs on, probably waiting for the daemon request to time out. This causes time-outs in drone and drone UI.
I’ve changed two things in drone. One is that I’ve set the timeout to 4 sec, which means drone will find out pretty quick that something is wrong and attempt to re-authenticate. During the re-authentication we also tell the web-api to connect to the daemon. This seems which seems to have fixed the timeout issue on my test setup.
I’ll push the changes later, so it isn’t available yet. Just to let you know it’s handled.
This little thing cost me hours.