Deluge

hi,

What is you add the executable permission to the group debian-deluged with all the plex etc. users already in?

With which version of Deluge and Libtorrent have you landed to now?

None of the possible access?
deluge-console (cli access to install)
deluge-web (webgui to install)
deluge GTK (fat client)

Hi, First thing to check: - libtorrent version binded with Deluge: Version 1.3.15 work with libtorrent 1.0.x and 1.1.x but not 1.2.x - port binding well configured, port forwarding on the router, such things - setting: have a look at ltconfig to tweak libotorrent value. It should help about performa...

Was the investigation on the network layer any informative (cable change, etc)? The script for tracker address reachability? As you are able to reach it most of the time I guess the DNS you use is not the issue A "sudo netstat -plant" (filter on the Deluge PID) show lot of time_out on the ...

And if you check the tracker answer with a script testing it each second for example? Possibly from 2 different computer including the incriminate RPI A curl retrieving the header or a tcp ping to the tracker port. The issue is from RPI3, what I guess a previous setup. Nothing on your local network ...

Hi

No experience with this system but your error and lonks point to libtorrent issue. Have you checked this part?
Deluge 1.3.X needs libtorrent <= 1.1.14
Starting Deluge 2.X you can use libtorrent >= 1.2.x

Hi, Not a general issue at least: Running Deluge 1.3.15/Libtorrent 1.1.11.0 on Debian 10 with more than 600 items seeding w/o time out. The buster version add some changes however. -What tells you "sudo dmesg -T"? anything related to a network issue, oom, - a "sudo netstat -plant"...

EXT4 is perfect, I'm using it too on an RPI...It not the root cause. The RAID1 driver maybe? Restricting to 1 the number of download is the good way to start troubleshooting, you're right at this level. I'm not experienced with container but as a basic: - the download folder is well on the R1 direct...

Hi,

It may be linked to the filesystem used on the destination disk. Example: using ntfs on a Linux box drastically raise the CPU usage for any disk operation. The container maybe part of the picture but I'm not using it so cannot tell.

It depends how your launch deluge and which tutorial you followed (by hand, cron, systemD unit). If you followed the tutorial on this site the user and group should be deluge indeed You can simply check with ps aux|grep deluged We can see your folder is owned by root:root, and deluge is certainly no...