rtorrent 0.9.4. 0.9.2, and 0.8.9 have all had issues installed onto a normal Fedora/RHEL box. I setup a user, compiled them per the following:

http://www.filesharingguides.com/tor...redhat-centos/

and setup the .rtorrent.rc per the following:

https://gist.github.com/ItsAdventure...6c4de8dd4d2bab

and put it under a user named seedbox. The system has thousands of gigabytes of space free. No permission issues of any kind. It works for small torrents flawlessly, but reverts to pausing for any large torrents 90GB+. It also randomly starts to send blocks of 10 torrents (out of 50) to pausing. There are no hardware errors as verified by StressLinux. It is a rackmount made of server grade hardware verified in the last 24 hours.

The first attempt to fix the endless pausing was to increase the limits in /etc/security/limits.conf:

* soft nproc 65535
* hard nproc 65535
* soft nofile 65535
* hard nofile 65535

This did not work. I did not change these back, but it did not work.

The second attempt was to edit the .bashrc so it would be raised when the rtorrent daemon started in screen with the following:

screen -S rtorrent -d -m su seedbox -c "rtorrent"

bashrc edit:

if [ $USER = "seedbox" ]; then
ulimit -n 65535
fi

This also did not stop the pausing torrents.

I tried to raise the following value in .rtorrent.rc when torrents over 100GB still would not stop pausing when they download fine in Deluge under a different system user with no bashrc edits.

network.max_open_files.set = 10240
pieces.memory.max.set = 5000M (system has 16GB with nothing running).

https://cryptobin.org/1780m489

Password:

torrentinvites.org

(Watch for spaces before and after the password for those copy/pasting.)

It is very fast and can seed at 80MB/s without trouble. When it works, it is working great. The settings seem to open the server up and get it going great until it stops for no reason with no errors.

Does anyone have any ideas?

If you have a Watch directory and you have all your .torrents there... probably the cause of pausing all your torrents is this line of code (on your .rtorrent.rc config file )

# watch a directory for new torrents, and stop those that have been deleted

schedule = watch_directory,5,5,load_start=/home/(your username)/(your download folder)/watch/*.torrent

schedule = untied_directory,5,5,stop_untied=

ps: If you delete a .torrent inside Watch directory then will pause the torrent in your client.

Just wondering, this happened to me. My watch has been deleted and now all the torrents I had in my watch folder are paused. How should I fix this exactly?

Well, if the problem is what i think, ruTorrent is not installed on root, and you need to change the ownership of the new folder that you created, so ruTorrent can access it.

sudo chown -R your.user:your.user folder-name

The easiest way to know what user should go on your.user is by doing ls -ld directory (on another directory, that you did not delete before.

Hope it fix, it worked for me

I had the same issue happen and i found the solution. Lower your max connections to 1024 and see if all your torrents are ready ( not paused ) if they are ok, then it is an issue with the max open connection settings being too high even those they were modified in the config.. If you want to test if thats really the issue before changing it to 1024 kill the torrent process and run rtorrent out of screen by just typing rtorrent ( if max connections is the issus you will see a couple messages on the window saying "too many open files blah blah" ) then for sure thats the issue, set it at 1024 and start to go up gradually until you hit that error again, then you will know which is the max u can use.