Qbittorrent: What does Stalled mean?

Created on 19 Oct 2017  ·  29Comments  ·  Source: qbittorrent/qBittorrent

EDIT: This has been resolved. See https://github.com/qbittorrent/qBittorrent/issues/7620#issuecomment-587797380 for explanation

Please provide the following information

qBittorrent version and Operating System:

3.3.16 Windows 7 64-bit

If on linux, libtorrent and Qt version:

What is the problem:

Torrents status stalled.

What is the expected behavior:

Downloading.

Steps to reproduce:

Happens randomly on large torrents.

Extra info(if any):

Seem to be able to remove and re-add torrent to get it to resume downloading. Reusing the magnet link does not work however only getting torrent file from original site or using the built in search feature to find the torrent again.

Most helpful comment

My seed/peers were fine. I compared it to uTorrent. After I restarted the qBitorrent the download was running fine again.

All 29 comments

AFAIK "stalled" is a status when your programs wants to download, but all connected peers can not seed to you (by different reasons, usually because they hit some limit on their side.). This is often observed when you try to download torrent which have low number of seed/peers. When you force your program to reconnect to peers by reinserting torrent in it, it just clears some timers/limit counters on other side and transmission resumes for a while. But this is usually just a temporarily effect.

So please check a number of seed/peers first.

Thanks for the detailed explanation.

My seed/peers were fine. I compared it to uTorrent. After I restarted the qBitorrent the download was running fine again.

@spedy Thanks, that worked for me.

I had an issue with my torrents being stalled and found this but my issue was on my end and wanted to post here in case anyone else in the future reads this.

My issue was simple, my drive was full and no more data could be written to it. User error.

This also doesn't seem to be an issue with qBittorrent and this issue should be closed IMO.

I have a set of completed torrents that I'm trying to seed, but they are all "stalled". What does it mean in the context of seeding?

Happened to me as well with big torrents of more than 30GB. I don't really agree with "temporary effect" or anything related to "peer/seeds".

When they are stalled, even if they go to download nothing will be downloaded, only the upload works. I often had torrents stuck at 99.9% because of this.
To fix it usually, I have to pause, exit, start again and resume for the download to continue.

However, sometimes I get torrents stuck at 100% stalling for hours... Only a "force recheck" solves the problem.

Overall, pretty annoying because it happens a lot. A recheck for big file is ridiculously slow even on a Raid5 or a NAS.

Hi there!

I'm stuggling whit the same issue: my torrents are stopping sometimes before they are complete. Maybe, just maybe, the problem is the client doesn't allocate the file's space on the disk and other apps uses the space, and this causes IO problems, and the client can't really do anything. You can change it in the options / downloads on the bottom of the page.

Mine was a problem with qbt not reading fast resume files or being unable to resume from them. Upgrading to the latest versions (4.1.x from 4.0.x) fixed it for me.

If nothing else, perhaps a more specific/informative message is in order...

For me restarting works. A total pain in the ass, but it works. I never had the issue until build 4.1.4

image

My problem is download is 100%, download rate 0, upload rate 1.4MB, seed ratio 3.28(more than seed ratio setting).

The torrent should be stopped at this point. but its not.

image

My problem is download is 100%, download rate 0, upload rate 1.4MB, seed ratio 3.28(more than seed ratio setting).

The torrent should be stopped at this point. but its not.

check your setting
image

If you remove the default drive might cause stall. for example I use to download to an external drive, when I tried to download without that, it stalled, because the system didn't find the default external drive. After deleting torrent, reloading, restarting, chose the built in drive, it worked like a charm.

This should be in the FAQ, please.

Disk full? If yes, just call the torrent "stalled"! https://github.com/qbittorrent/qBittorrent/issues/10556

I had/have this problem,
First when I installed qBittorrent, I left everything "Default" and everything would stall.
Then I changed the port to a random one and everything worked fine.
I used to stop my torrents when done and then keeping it there but after 15 torrents or so, every new torrent would stall unless I randomized the port again and restart my client.
Removing the paused/stopped torrent seems to have solved this problem but really make the client feel like half-done.

Same here.
Disk space, network, seed}peer] list, forwarded port to be active, all worked ... and just by restarting a program is this solved. Strange. Oh .. and I dont think that (as example) last GoT episode have small amount of seedders ;-) So ... ?

For me, the problem was that I was sharing to a remembered path on my network but the network share had not been accessed since reboot (even though it appeared connected in the macOS Finder).

+1 for better handling of disk errors

Just restarted qBittorrent and the download started

Same thing just happened to me. Download was stalled until I restarted the qbittorrent. V4.1.6

This seems to be a really persistent bug. The reason I'm here is because I'm afflicted too. We should put out heads together and figure out what setting(s) causes the instability. Does anyone know if pre-allocating files improves the issue? I found a bunch of duplicate issues that all went dead, but this issue has been around since before 4.1.3.

Same problem here with v4.1.7. This use to not be an issue with earlier versions. Lots of seeders, 99.9% done. Keeps stalling even after reset, reboot, and disk is not full. Only a recheck puts things back in order. This is an issue with qBittorrent.

A simple solution is checking your antivirus and firewall - i did that, gave the permissions and all worked out just fine (i got no antivirus / firewall message about blocking it but giving permissions worked for me)

Does "Stalled" equal to "Stopped" ?

I had Stalled status when I tried to download to a folder that wasn't on the disk (it was, but I deleted it before the program started). When I chose the right destination, everything was fine. I think that qBittorrent should handle such situations, not agree to download into a folder that doesn't exist.

"Stalled" means no upload/download activity is happening at the moment. It is neither a "good" nor "bad" thing on its own.

For example, if you are seeding but there simply are no peers requesting the files, the torrent will be "stalled" (more specifically in this case, in the "stalled uploading" state).

Similarly, an unfinished torrent can be "stalled downloading", if there are no seeders/peers online from whom to request the data.

However, a torrent will also "stall" if there are peers online, but you cannot connect to them. If you believe this is due to a problem in qBIttorrent and not with said other peers, feel free to submit an issue for the specific problem you observe.

In general, stalling is "bad" _when you think it should not be stalling_, i.e., when there is no upload/download activity but you think there should be. For example, if in similar circumstances you observe upload/download activity in another client but not with qBittorrent.

I'm closing this issue because this is really a support question that should have been closed long ago. Anyone who is experiencing _actual_ issues related to stalling please post a specific standalone issue.

Running Qbt v4.2.3 on Catalina, and downloads would soon sputter and stall...
Solution was to start with fresh, saved as-local-as-possible, download folders:
I changed the incomplete torrent folder to a new one on a SSD drive, the finished .torrent files to a very accessible USB directory, and a new fresh default save path folder, on an attached USB directory.
In short, no need to save to a folder on internal 'Macintosh HD', if space is a consideration, but save to nearby drives, not network drives -- at least for all temp folders.
Solution: Folder location save path refresh worked wonders... when all else failed.

Was this page helpful?
0 / 5 - 0 ratings