Deluge

Hi,

This topic may help, certainly the 2 link I give in. Please have a look at them viewtopic.php?f=7&t=54985&p=228326&hilit=stretch+ppa#p228326

I hope it will be better managed in version 2 (and it should)

I have a similar issue on my setup when above 650 torrents loaded. It seems to be linked with an RPC problem for me at least, majored by the limited hardware (RPI) I'm using. This is why the issue is not generalized to all setup, the resource capabilities and the configuration influence such behavio...

If the computer can boot with your user past thius location in a cmd or explore: %appdata%/deluge/state If the computer is offline but with access to the windows drive replace $USER with your account name and go to C:\Users\$USER\AppData\Roaming\deluge\state You can take the whole Deluge folder but ...

Hi, A tracker is always needed with a torrent, sharing the peers available and what part of the file they have. So when you add a torrent to Deluge you should already have tracker(s) associated. I' never met this kind of error but I guess one of the associated trackers of the torrent is not healthy....

in your process list does the port appear? bind with which process?
If Deluged, then it seems you try to launch the software twice.

What's the connection limit you set? A high number may create such issue either on computer and router. Regarding the router you have it seems odd but anyway worth the try: limit the total numver of connections to let say 200 or 150 and give us a feedback.

Thank you for the feedback

It sounds weird if I tell you I'm running >600 torrents on a RPI? No specific plugin or else may explain such CPU usage?

Hi,

Whatever the platform you can leave it on and simply raise the number of active torrent above your number of torrents (9999 or else).
This way the queuing will never step forward