Qbittorrent Number Of Downloads

2 views
Skip to first unread message

Jaunita Rousu

unread,
Aug 4, 2024, 10:31:03 PM8/4/24
to necnoteco
Ive been using Docker to run various applications, including the ever-so-popular qBittorrent. All was going swell until my downloads decided to play a game of hide-and-seek without inviting me! ? Each download attempt ends with qBittorrent throwing a mysterious "No such device" error at me.

1. You have published the yaml file without indentations. It would be convenient to edit that publication and add the indentations of that file, sometimes there are errors that cannot be seen if you publish it like this.


3. Likewise, reading that page you must specify /downloads to the right of the colon, if you write anything else you are not accessing the correct folder within the container. /downloads_qbittorrent I would say that it is useless. Although I'm not sure about this because I don't know how this container works. In any case the permissions error seems to be related to the permissions of that volume on your server. That is, the user with UID=1000 must have access to the /srv/mergerfs/mediafiles/mymedia/temp_downloads/qbittorrent folder.


By default, Docker sees each mounted directory as a different filesystem (FS). Right now, if you could extract to a different directory outside of "/srv/.../qbittorrent" (which you currently can't), you'll not only have to define that path as well in your compose file but also if the file is moved, it will always be a copy (cp) operation instead of a move (mv), which obviously takes longer.


Firstly, a huge shoutout to chente for the wise suggestion to reach out to LinuxServer, the creator of the Docker container. That thread provided a treasure trove of insights! Also, a big thanks to @olduser for highlighting the intricacies of how Docker handles mounted directories as a different filesystem. This certainly gave me a new angle to consider.


After connecting the dots and gathering insights from various threads (including an intriguing one I stumbled upon on LinuxServer's Discourse forum), I'm leaning towards the theory that the root of the problem might be how qBittorrent uses mmap.


I promise to loop back and update you all with any progress or revelations. If this workaround does the trick, it could potentially assist others facing similar challenges with qBittorrent on OMV and Docker.


I recently decided to switch from uTorrent, which had been working well, to qBittorrent. In the AirVPN client settings, I added an open port. I then opened qBittorrent and added this port number to the Incoming Connections field. I also unchecked the uPnP box in qBittorrent, per instructions I've seen around here.


(if on Windows, find the Local Area Connection number that references your tunnel adapter. You can find this out by going to a command prompt, running ipconfig /all, and look for the adapter with the 10.x address).


id be interested in your opinion or if you if know specifically regarding qBitTorrent how the the ratio of download vs upload is affected? Is there a point where you don't get any further returns from increasing your upload speeds further - I'm currently capping uploads to 100KB/s and it seems anything larger than that doesn't offer any greater download returns.


That really depends on how the seeders are set up more than how you are set up. Some people only seed based on that ratio and some seed the same regardless. I have my torrent client (not qbit) set up to upload at a max rate of 1k but I have no issues pulling down torrents at 800k apiece. Not sure why that is.


Agree with Khariz. The seeders determine the allowable ratio (speed and/or bytes). I have my client set to unlimited for both (I have FiOS 75/75 service) so I really don't know the affects in general terms.


For the record, this enables searching for peers on the Local Area Network, so unless you have multiple torrent clients running on your LAN (and any VPN or tunnel systems allowing local connections) you probably don't need this checked. It won't really affect you either way but it's a waste of CPU cycles, especially if you bind qBittorrent to your tunnel interface.


This is user preference. If you intend to let a lot of downloads go by while you're away you might want to queue them so you don't have them all fighting over your pipe. Or if you want to manage it manually and start/stop specific torrents as you feel the need, you can disable (un-check) it. qBittorrent uses a "Priority" system that's really just a queue order so you can set which ones will start when a slot becomes available for them.


Let me explain: I add the RSS to the feeds lists. So, in order to download them automatically, I go to the RSS Feed Downloader window and check the "Automatic download..." box. As the RSS feed is filtered server-side and contain only downloads in which I'm interested, I do not set any filter.


I guessed I've done everything right. I expected it to start downloading new itens as they were added to the feed. However, every time I launch qTB, it tries to download every entry in the RSS ever. I have set two RSS feeds, and it tries to queue all torrents in it, no matter how old they are, every time I restart qbT or click in the "Update All" button in the RSS tab.


At first, I though it was trying to download everything in the feed list once, and I should only remove the files from the queue and it would not bother me again, as it would count these as already downloaded. It would be a bug, indeed (at most, it should try to download only the articles shown in the list, as set in the RSS preferences - and that would be still a bad design). But this is not what happened. If I remove the downloads from the queue and restart qBT, it put all of them again in the queue.


But it didn't fix my problem: as soon as i first launched v2, it started downloading all torrents again. I deleted then, restarted the software, and they all came back. I even deleted the original RSS entries, created a new one with the same link (the one above), and the problem remains the same as described in the first post.


So, I changed the "Maximum number of articles per feed" to 4, and episode 06 appeared in the article list. I marked it as read and, as I expected, it was not queued. qBT is now attempting to download all episodes from 05 and before, but not episode 06.


I have:

1. Added your RSS feed to the list

2. Went to RSS Feed Downloader dialog and check the checkbox "Download torrents from this feed"

3. Closed the RSS feed Downloader and hit "Update All" button

4. All 30 torrents were added to the download list

5. All 30 RSS items appear as Grey (Read) in the RSS list

6. Restarted qBittorrent

7. Still have the 30 torrents in the list, qBittorrent did not attempt to redownload the same torrents (according to the log window) and the RSS articles corresponding to the torrents still appear ad grey.

8. Removed all the torrents from the download list

9. Restarted qBittorrent

10. The download list is now empty, qBittorrent did not attempt to redownload the previously added torrents.


Wow. I just started using the software (really, I installed it few minutes before the first post and had not even downloaded a single file), and I've already helped finding a bug, which was promptly fixed in a few minutes.


I read through this thread experiencing the same problem. I saw that the issue was solved with the newest release, so I added the PPA. I now have version 2.9.3 but am still experiencing the same problem as before. I will mention all the steps I have taken:


2. For the RSS Downloader... button (Automated RSS Downloader) I created a rule and checked "Use Regular Expressions" then added Must Contain "x" (so that it downloads everything that is in the 01x06 format etc).


5. I close Qbittorent. I open it again...(in the process right now) and it is downloading ALL Happy Endings and Cougar Town episodes. Now it is starting to download Burn Notice Episodes..... Deleting them now. Deleted them... now it is moving onto Community and downloading all of those episodes. [As a side note, this is more progress then the previous version of Qbittorent, which for some reason would only download Burn Notice episodes].


7. Now, I will try to replicate the same thing. Closing Qbittorent now..... Yikes... went to close it and noticed that it is now downloading ALL of Happy endings (and is starting to download Community and Burn Notice as well). Definitely a problem.


I am making the full plunge from Ktorrent (which works great but I prefer some of the features of Qbittorent). So any help you can give me would be greatly appreciated; I really don't want to go back to Ktorrent at this point.


Is the qBittorrent client showing a "Stalled" status for your downloads? This indicates that no download activity is taking place through your torrent client. When your torrent software displays this status, it means it has failed to establish a connection between seeders, people who have the downloaded torrent data, and peers, people like you, who are downloading this data. But why?


Maybe it's not just you, but every qBittorrent user might be facing the same issue. The reason? Due to a problem with the torrent clients' backend. Therefore, ruling out this possibility will save you from struggling to fix a problem that is beyond your capacity.


To do that, open your browser, enter "is QBittorrent down?" and press Enter. Then, visit a couple of websites that display the current status of your torrent client. If you find many reports of this issue on different websites, the problem lies with the backend. Therefore, wait a couple of hours and restart the download once the backend issues have been resolved.


Downloading files, specifically through third-party clients, requires a stable connection. If your internet connection isn't strong enough or stable, the download might be interrupted. This could also be the cause of the issue you're facing, meaning qBittorrent doesn't have access to a reliable internet connection.


If the connection turns out to be unstable, either shift to a different internet connection or check out our guide on how to fix an unstable Wi-Fi connection. If the connection is already stable, move on to the next fix.

3a8082e126
Reply all
Reply to author
Forward
0 new messages