any experience with rtorrent?

[filonome]

hey i was wondering if anyone here has a lot of experience with rtorrent and could answer a quick question of mine.

i have rtorrent setup on my vps to download torrents with but the problem is that if i let it get above a certain download rate it seems that this causes it to crash--and no error is given.

could this be a problem with rtorrent or is it more likely a problem with my limited amount of memory on the vps (256mb)

any feedback is appreciated, thanks!

filonome

[fstokebanget]

even you use linux with the lightweight torrent client like rtorrent, in my opinion having the ram only 256mb isn't enough at all, maybe if you use it on a slow connection it'll work, but on 100/100 even it's shared by a number, still doesn't enough, try to increase your ram

[filonome]

ok that's what i figured, ill just keep it tuned down for now i guess, i'll buy more ram next month.

[fstokebanget]

just curious, on what hosting is your vps ? thanks

[DanielleD87]

have you tried turning your buffer up? I know doing so will use more memory but 256megs should be fine to run rtorrent on. seems kind of awkward it is carshing. my guess is the hard drive is locking up, but i'm not expert with rtorrent. i kind of ditched it for azureus (i know I'm lame lol)

[filonome]

please explain what you mean "turning your buffer up"

[DanielleD87]

like the bigger the buffer the more memory is used and the less hdd is used. at high speeds a hard drive will choke unless the mem is buffered a god amount.

[iTK98]

First I will show you my VPS specifications:
VM: Xen
OS: CentOS 5
Mem: 256ram / 512 swap
Client: rTorrent 0.7.9 + libTorrent 0.11.9 (custom build)
Other Things I'm running, sshd, httpd - apache, ftpd - vsftp, bnc - psybnc
identd - oidentd. I think I covered everything... (I'm NOT running any kind of VNCs)

I'm running rTorrent successfully without any glitches (well,
sometimes when the transfer rates are very high, I get errors
related to Disk Buffer, and the chunks are dropped). I can
download more then 5 torrents simultaneously with out any
problems, and I can download big torrents (the biggest
torrent I've downloaded was 11gb)

The client itself never crashed on me. I'm running it inside
'screen' so if I got disconnected, the client will be still alive
inside the screen. (and I recover it with screen -r).

please supply more information, like conf (.rtorrent.conf) logs
and specs.

[filonome]

ok well how do i turn my buffer up?

[iTK98]

supply



cat /proc/sys/fs/file-max
and


ulimit -n
(Make sure you're running this with the same user whose
running the rTorrent application)

:angry: Read my previous post, and supply the specs and .rtorrent.rc.

[filonome]

[jonathon@filonome ~]$ ulimit -n
1024
[jonathon@filonome ~]$ cat /proc/sys/fs/file-max
262144

and .rtorrent.rc is as follows:

# 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.

# Maximum and minimum number of peers to connect to per torrent.
#min_peers = 40
#max_peers = 100

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

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

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

# Set maximum memory usage
max_memory_usage = 251658240

# Default directory to save the downloaded torrents.
# directory = ./

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

# Watch a directory for new torrents, and stop those that have been
# deleted.
#schedule = watch_directory,5,5,load_start=./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=300,200M,300"

# 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 = 7769-7777

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

# 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 = yes

# 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 = auto

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

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

#
# 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 = 100

# 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 = 10

[DanielleD87]

# Set maximum memory usage
max_memory_usage = 251658240

if the box only has 256 megs and you set rtorrent to use 256 megs there will not be enough memory for the OS or anything else you are running. Try setting it to 200megs.

[pro267]

if the box only has 256 megs and you set rtorrent to use 256 megs there will not be enough memory for the OS or anything else you are running.
That's what virtual memory is for..

[DanielleD87]

yes aka using the hdd, hitting an overload and crashing

[fstokebanget]

So you're telling rtorrent uses almost all of physical memory to do the job ?

[DanielleD87]

i'm saying he has it setup to use more then there is physical memory available and that is what is causing it to crash.

[filonome]

i have it set at 250, what should i put it down to?

[Submission]

200 like he said you dumb fuck

[DanielleD87]

I AM A FEMALE dumb fuck

[fstokebanget]

:lol:

[Fibre]

Where are the mods to sort the kids out? :|