Transmission

The above file limits were for the user 'transmission' Today I also set higher file limits for the daemon-transmission service, and higher file limits for the systemd-nspawn container service, and after an hour it seems to be fine. May not have been necessary to edit open file limit for the user, bu...

I have three clients that repeatedly run into these errors. One has ~40k torrents, two have ~115k torrents each. I'm using transmission-daemon 4.0.5 running under the user 'transmission' in a Debian systemd-nspawn container on TrueNAS. root@tm:~# sudo -u transmission /bin/bash -c "ulimit -a&quo...

Yeah, I don't use public trackers. I can try 50 but it might not be for a week or so after I'm off vacation. For now just wanted to get it functioning.

Any suggestions for troubleshooting why starting the client takes an hour to load?

I'm a bit confused... "the tracker" is ???? A single torrent tracker (eg: tracker.fred.cc) or a torrent indexing web site (eg: all-those-freds.cc)? "isn't reporting" in what way? Sending announces fast enough isn't a thing. The issue is how many announcers can be touched at once...

https://github.com/transmission/transmission/blob/main/libtransmission/announcer.cc#L58 Would increasing this number possibly fix the problem? Is there any way to change it without building it? EDIT: Built 4.0.4 with the linked line changed to a higher number. This has resolved the issue. I would li...

Good day, I had 10 instances of a client with ~21k torrents each. The tracker was correctly reporting all seeded torrents. Wanting easier management, I looked for a client that could handle all torrents in a single instance. I migrated all torrents to the current version of Transmission. I access th...

This is some crap. You guys say the r8420 nightlies gets rid of this very annoying bug - I tried the latest one, which is r8551, and it doesn't work. Every time I try to add a torrent, it says: "Connection Failed: Could not connect to the server. You may need to reload the page to reconnect.&q...