Thread: rtorrent.rc problem

hi when I type



cd /home/username
ls -a

nano .rtorrent.rc I get rtorrent files everythign up to here is fine

problem when I change max memory usage or anything in that list rtorrnet not start and when I put old value still be same not strat it start and close in 1 secceond after ı PUt this # it start but sudenly it get crashed in a few ahours and not start again

any idea why this is happing I sick of change ram t 4gb every time

PS when Iput #maxmemoryusage

i memory became 3277 :( and get crash everytime in a few ahours

If you edit the rtorrent configuration settings, you have to be careful how you change them.

If there is an octothorpe (# sign) in front of a line, that line will be ignored and rtorrent will use a default value instead. Remove the # to enable the line.

rtorrent probably wouldn't start after you made changes because of syntax/grammar/typo/extreme value. You didn't provide any details as to exactly how you were changing the value, so there is no way for me to be certain. When you comment out the line (add the # sign), it starts up because you have forced a default value. And probably crashes later because the default value is woefully out of date and inadequate. If it was literally 3277, that is 4 MB, which would be a very low value. Again you didn't tell us what error message you may have seen or what was in the log, so I cannot be certain here. But it is likely.

If your send_buffer_size is a default setting (probably 4 MB - you can check with cat /proc/sys/net/ipv4/tcp_wmem) or even if you delete a number of torrents in a short time span, you will can easily run out of memory. For instance if you have 100 upload slots x 4 MB each, that alone will consume 400 MB.

max_memory_usage refers to kernel mapped memory, not physical memory. And the setting may, within reason, exceed the amount of physical memory available. A commonly seen error when this value is inadequate is;
Storage error: [File chunk write error: Cannot allocate memory.]

sample .rtorrent.rc entry:
max_memory_usage = 3500M

I found :D problem I didnt give space between = and number :D

anyway I have 1 more quesition after I start Upload little prgrams lik 400 500mb and if you consider I have 4tb HDD on my server

I have 100 active torrents now and Im gettin this error msg cant crunk open files tomany times ? how can I fix this
I see at settigns open files limit is 256 copper do you have any idea to make it work with 100 torrents

It's not clear to me what error message you are seeing. Ideally, I'd like to see your rtorrent configuraton file. But you should at least copy and paste the exact error message into this thread + then we may be able to offer you better suggestions.

# This is an example resource file for rTorrent. Copy to
# ~/.rtorrent.rc and enable/modify the options as needed. Remember to
# uncomment the options you wish to enable.
#
# Based on original .rtorrent.rc file from The libTorrent and rTorrent Project
# Modified by Lemonberry for rtGui rtgui - Web based front-end for "rTorrent" - the Linux command line BitTorrent client - Google Project Hosting
#
# This assumes the following directory structure:
#
# /Torrents/Downloading - temporaray location for torrents while downloading (see "directory")
# /Torrents/Complete - Torrents are moved here when complete (see "on_finished")
# /Torrents/TorrentFiles/Auto - The 'autoload' directory for rtorrent to use. Place a file
# in here, and rtorrent loads it #automatically. (see "schedule = watch_directory")
# /Torrents/Downloading/rtorrent.session - for storing rtorrent session information
#

# Maximum and minimum number of peers to connect to per torrent.
min_peers = 30
max_peers = 300

# Same as above but for seeding completed torrents (-1 = same as downloading)
min_peers_seed = 30
max_peers_seed = 100

# Maximum number of simultanious uploads per torrent.
max_uploads = 30

# Global upload and download rate in KiB. "0" for unlimited.
download_rate = 0
upload_rate = 0

# Default directory to save the downloaded torrents.
directory = /home/freddy/downloads

# Default session directory. Make sure you don't run multiple instance
# of rtorrent using the same session directory. Perhaps using a
# relative path?
session = /home/freddy/rtorrent/session

# Watch a directory for new torrents, and stop those that have been
# deleted.
schedule = watch_directory,5,5,load_start=/home/freddy/rtorrent/watch/*.torrent
#schedule = untied_directory,5,5,stop_untied=

# Close torrents when diskspace is low. */
schedule = low_diskspace,5,60,close_low_diskspace=100M

# Stop torrents when reaching upload ratio in percent,
# when also reaching total upload in bytes, or when
# reaching final upload ratio in percent.
# example: stop at ratio 2.0 with at least 200 MB uploaded, or else ratio 20.0
#schedule = ratio,60,60,stop_on_ratio=200,200M,2000


# When the torrent finishes, it executes "mv -n <base_path> ~/Download/"
# and then sets the destination directory to "~/Download/". (0.7.7+)
# on_finished = move_complete,"execute=mv,-u,$d.get_base_path=,/home/downloads/<username>/complete/ ;d.set_directory=/home/downloads/<username>/complete/"

# The ip address reported to the tracker.
#ip = 127.0.0.1
#ip = rakshasa.no

# The ip address the listening socket and outgoing connections is
# bound to.
#bind = 127.0.0.1
#bind = rakshasa.no

# Port range to use for listening.
port_range = 55950-56000

# Start opening ports at a random position within the port range.
port_random = yes

scgi_port = 127.0.0.1:5000

# Check hash for finished torrents. Might be usefull until the bug is
# fixed that causes lack of diskspace not to be properly reported.

check_hash = no
# Set whetever the client should try to connect to UDP trackers.
#use_udp_trackers = no

# Alternative calls to bind and ip that should handle dynamic ip's.
#schedule = ip_tick,0,1800,ip=rakshasa
#schedule = bind_tick,0,1800,bind=rakshasa

# Encryption options, set to none (default) or any combination of the following:
# allow_incoming, try_outgoing, require, require_RC4, enable_retry, prefer_plaintext
#
# The example value allows incoming encrypted connections, starts unencrypted
# outgoing connections but retries with encryption if they fail, preferring
# plaintext to RC4 encryption after the encrypted handshake
#
encryption = allow_incoming,enable_retry,prefer_plaintext

# Enable DHT support for trackerless torrents or when all trackers are down.
# May be set to "disable" (completely disable DHT), "off" (do not start DHT),
# "auto" (start and stop DHT as needed), or "on" (start DHT immediately).
# The default is "off". For DHT to work, a session directory must be defined.
#
dht = disable

# UDP port to use for DHT.
#
# dht_port = 6881

# Enable peer exchange (for torrents not marked private)
#
peer_exchange = no

#
# Do not modify the following parameters unless you know what you're doing.
#

# Hash read-ahead controls how many MB to request the kernel to read
# ahead. If the value is too low the disk may not be fully utilized,
# while if too high the kernel might not be able to keep the read
# pages in memory thus end up trashing.
hash_read_ahead = 10

# Interval between attempts to check the hash, in milliseconds.
hash_interval = 50

# Number of attempts to check the hash while using the mincore status,
# before forcing. Overworked systems might need lower values to get a
# decent hash checking rate.
hash_max_tries = 1

# Max number of files to keep open simultaniously.
network.max_open_files.set = 256

# Number of sockets to simultaneously keep open.
#max_open_sockets = 65023

# Max amount of memory to use
#max_memory_usage = 1610612736

# Example of scheduling commands: Switch between two ip's every 5
# seconds.
#schedule = "ip_tick1,5,10,ip=torretta"
#schedule = "ip_tick2,10,10,ip=lampedusa"

# Remove a scheduled event.
#schedule_remove = "ip_tick1"

#max_open_http = 32
trackers.numwant.set = -1
#max_file_size = -1
#split_file_size = -1
max_memory_usage = 4000M
network.send_buffer.size.set = 4M
network.receive_buffer.size.set = 4M

problem is like this

"To many Open files "





BTW my upload speed is verry slow is it posibly we can increase it no ıone is asking me slot for upload I only upload 3 4 person per torrent

Some of those settings are odd. And several lines appear to be incorrectly formatted as well. I don't believe that the 'network.' prefix should be there.

Try changing these settings..

#network.max_open_files.set = 256
#network.send_buffer.size.set = 4M
#network.receive_buffer.size.set = 4M
max_open_files = 256
send_buffer_size = 2M
receive_buffer_size = 100K
min_peers_seed = 40
max_uploads = 35
max_open_sockets = 768
use_udp_trackers = yes
max_open_files = 128

And see if that helps. Once you confirm that the problem has resolved, you can try increasing the max number of files open..

max_open_files = 256

If you are seeing slow speeds on swarms that should be fast., then the first things to look at would be the number of upload slots, preload type (recommend type 1 aka madvise) and max number of open files. You could also see if reducing the hash interval helps:

hash_interval = 30

Originally Posted by Oreme

I found :D problem I didnt give space between = and number :D

anyway I have 1 more quesition after I start Upload little prgrams lik 400 500mb and if you consider I have 4tb HDD on my server

I have 100 active torrents now and Im gettin this error msg cant crunk open files tomany times ? how can I fix this
I see at settigns open files limit is 256 copper do you have any idea to make it work with 100 torrents

Open files limits on unix systems are by default very low, with respect to torrenting. If you consider for example a SCC pack of rar'ed content.

So you need to change the system limits and the limit in rtorrent.rc . I use pretty high numbers, which have never caused me a problem, but if people think they are to high, I would love to hear why, and what problems I may encounter.

ssh into your seedbox, and use su to switch to root. Then we will edit the file that sets the limits. I use vi, but switch vi for nano if you prefer

Code:

vi /etc/security/limits.conf

Then you want to add the following 2 lines to the file:

Code:

* hard nofile 32768
* soft nofile 16384

The * makes the change system wide.

This will reset the limits, but will not take effect until the system reboots, so we need to manually reset them, in order to avoid a reboot.

Code:

ulimit -H -n 32768
ulimit -S -n 16384

exit back to your standard user, and open your .rtorrent.rc file using your preferred text editor, and edit the max files setting in rtorrent

Code:

network.max_open_files.set = 10240

restart rtorrent for that change to take effect.

As I said you may want to use lower numbers than I have, and perhaps should depending on your system, but these numbers have worked for me without an issue so far.

Originally Posted by Arakasi

Open files limits on unix systems are by default very low, with respect to torrenting. If you consider for example a SCC pack of rar'ed content.

So you need to change the system limits and the limit in rtorrent.rc . I use pretty high numbers, which have never caused me a problem, but if people think they are to high, I would love to hear why, and what problems I may encounter. ...

This is good advice, but people with limited memory may run into problems with that number of file handles. For the most part though, the systems with the least available memory tend to be seedboxes without root or even shell/SSH access anyway. rtorrent will crash with > 256 files open on some seedboxes due to limited resources. The default *nix settings, though low will be fine for all but the largest torrents. Such as SCC music packs that have thousands of RARd files. That is when Arakasi's advice shines. Recommended for power users who have sufficient memory.

A related setting that is often misconfigured is max_memory_usage. This is often set to ~75% of physical memory by vendors. This setting does not refer to physical memory though, but rather kernel mapping. So it is not bound by the amount of physical memory and should be set higher than normal to avoid chunk allocation errors.

teh problem was like this exacay

Storage error: [File chunk write error: Too many open files.]

I tring your suggest I hope it will work

---------- Post added at 12:19 AM ---------- Previous post was at 12:07 AM ----------

hey araksi I dotn know if I did correct I change files like this

- the wildcard *, for default entry
# - the wildcard %, can be also used with %group syntax,
# for maxlogin limit
# - NOTE: group and wildcard limits are not applied to root.
# To apply a limit to the root user, <domain> must be
# the literal username root.
#
#<type> can have the two values:
# - "soft" for enforcing the soft limits
# - "hard" for enforcing hard limits
#
#<item> can be one of the following:
# - core - limits the core file size (KB)
# - data - max data size (KB)
# - fsize - maximum filesize (KB)
# - memlock - max locked-in-memory address space (KB)
# - nofile - max number of open files
# - rss - max resident set size (KB)



# - chroot - change root to directory (Debian-specific)
#
#<domain> <type> <item> <value>
#

#* soft core 0
#root hard core 100000
#* hard rss 10000
#@student hard nproc 20
#
#@faculty hard nproc 50
#ftp hard nproc 0
#ftp - chroot /ftp
#@student - maxlogins 4

* hard nofile 32768
* soft nofile 16384

ulimit -H -n 32768
ulimit -S -n 16384

# End of file

I added those 4 lines bnefore end of file line is it ok ?


I had this kind of problem now

Storage error: [Hash checker was unable to map chunk: Too many open files] this is new :D BTW my uupload speed islike 1mb/s it slowed down so much it was like 10 15mb/s

download speed is ok but IM having problem with ratıo with this way

---------- Post added at 12:25 AM ---------- Previous post was at 12:19 AM ----------

adn MY all files stoped after write this code


and I cant start my torrents all of torrents stoped :(

---------- Post added at 12:43 AM ---------- Previous post was at 12:25 AM ----------

I gues s ts re cheecking my files and I got 2 times closed rtorrent I I hope I will not lose my all files I have 3.5 seeding files and Rtorrnet is getting crashed even I make everything like old :( I cant make rtorrent work it close it self after 5 6 minutes what I gonne do ?



[07.10.2011 17:46:52] ruTorrent can't detect the uid or rtorrent user. Some functionality will be unavailable.
[07.10.2011 17:46:52] rTorrent is compiled with incorrect version of xmlrpc-c library, without i8 support. Version must be >= 1.11. Some functionality will be unavailable.
[07.10.2011 17:46:52] erasedata: plugin can't start for unknown reason.
[07.10.2011 17:46:52] retrackers: plugin can't start for unknown reason.

it sopened and I got this


WHen I type this code

* hard nofile 32768
* soft nofile 16384

ulimit -H -n 32768
ulimit -S -n 16384


my delete from HDD speed is about 466mb/s

I have raid0 it has arround 230mb/s reading speed

when I chang eit it get %50 slower but I dotn know what happed rtorrent its not work system write and read definatly goes fast with that code