File stalled

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. When they are stalled, even if they go to download nothing will be downloaded, only the upload works. I often had torrents stuck at To fix it usually, I have to pause, exit, start again and resume for the download to continue.

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.

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.

Mine was a problem with qbt not reading fast resume files or being unable to resume from them. Upgrading to the latest versions 4.

For me restarting works. A total pain in the ass, but it works. I never had the issue until build 4. If you remove the default drive might cause stall. After deleting torrent, reloading, restarting, chose the built in drive, it worked like a charm. Disk full? If yes, just call the torrent "stalled"! 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. Same here. I have also sent a request to bugs fetchsoftworks. By the way, I am also checking for Fetch update, and it has been checking now for about 5 minutes with no answer! Is this a new problem?

Have you been able to download files from this server using Fetch before? It is really a problem. And I have been downloading from and uploading to this server on an almost daily base for years. The hostname is: ftp. If this is a new problem and transferring files used to work fine, then more likely this is a problem with either the server or your network connection instead of Fetch.

Based on the transcript you sent, and the fact that you are seeing delays with the "Check for Update" feature, I would recommend restarting all your network equipment using the following instructions. We find that these steps often solve problems like yours. Before I tried that, I shut off my Airport and connected my iPhone instead of, using that as my connecting device. Of course things got a bit slower, but I could connect to various sites at internet with no problem.

But still my Fetch refused to download anything telling me that the file transfer stalled. I could of course now follow your instructions, but I think that it can not be my router that is the problem. Do you have any further suggestions? You have experimented with a different network route, but since it is not the exact same setup as the one that has the problem, it may not mean that everything is fine with the router or modem.

These problems can be very specific to the kind and path of the network traffic. So I recommend that you try my original instructions to restart everything, and let us know the results.

The problem still exists. I tried to upload a small pdf file. It was running for at least 5 minutes. Then I stopped it. The normal time for that specific file is sek.

Then I tried to download a very small file - an index, and I again got the message: transfer stalled. It looks like for your Internet connection, the time Fetch's waits until it decides a transfer has stalled is too short. While our default setting works well for nearly all connections, there are a few cases where it needs to be longer, and it looks like your situation is one of them. Please try the following, which doubles the time Fetch waits until it decides a transfer has stalled:.

I have recently within a week changed internet connection to an apartment complex net. An attempt to write a SQL Server log file periodically becomes stuck for approximately 45 seconds. The log write does not finish in a timely manner. This behavior creates a blocking condition that causes second client time-outs. The application submitted a commit to SQL Server, and the commit became stuck as a log write pending. This behavior causes the query to continue holding locks and to block incoming requests from other clients.

Then, other clients start to time out. This compounds the problem because the application does not roll back open transactions when a query time-out occurs.

This creates hundreds of open transactions that are holding locks. Therefore, a severe blocking situation occurs. For more information about transaction handling and blocking, see the following Microsoft Knowledge Base article:. As more connections become blocked, the website creates more connections.

These connections become blocked, and the cycle continues. After approximately 45 seconds, the log write finishes. However, by this time, hundreds of connections are backed up. The blocking problems cause several minutes of recovery time for SQL Server and for the application. The computer had multiple HBA cards with failover support. The second HBA handled the request and quickly finished. To help prevent such stall conditions, the hardware manufacturer recommended a "retry before failover" setting of 5 seconds.

One such condition was a filter driver for backup processing that allowed a backup of the files that were open when the backup occurred. The system administrator had included the SQL Server data file directory in the file backup selections. When the backup occurred, the backup tried to gather the correct image of the file at the time the backup started. Processing tasks such as a SQL Server read-ahead were effectively disabled by the actions of the filter driver.

Additionally, another bug in the filter driver left the "one at a time" actions in process, even when the backup was finished. The only way to restore SQL Server performance was to close and then reopen the database, or to restart SQL Server so that the file handle was released and reacquired without the filter driver interaction.

To resolve this problem, the SQL Server data files were removed from the file backup process. I'm working from home and the office, and my office computer is refusing to sync with windows explorer. I'm using Windows I can see the files on dropbox. I've done an advanced re-install and set my upload and download rates to "don't limit".

My sync has restarted after changing from the stable build to Beta build View solution in original post. The way we work is changing. Share and discover new ways to work smarter with Dropbox in our community.