Thread: rtorrent.rc problem

3600 GiB (2x2TB RAID0)

2x Intel Quad Core Xeon E5620 (2.4Ghz, HT, Turbo)



8GB DDR3 ram

---------- Post added at 02:14 AM ---------- Previous post was at 02:12 AM ----------

rtorren always do this to me new version has this problem when any big size fize cheeking it stack and not open new version definatly worse then old one I never had such problem with old version dam I wish I didnt upgrade it


even I install its open it chhecking files it about 300 400gb and it stack sudently get crashed close and we go the where we start I need to deleted Itorrents and it will open but I dont want to delted my ratio download under 1 :( for this reaosn

ok so high end for a seedbox, in which case increasing the open files limit, would not be a problem.

Sounds like the problem is with the hash checking. Not sure about those settings, so can't help, but I am sure someone ca. I will say though that to avoid hash checking, when restarting rtorrent, stop all torrents before closing it down, then start them up again after restart. That doesn't help if rtorrent has crashed though.

genereally it work ok but sometime sudenly close its not fix anyway I will delete all torent this limit thing for HDD is worked I can read and write faster

I would not delete all your torrents, I would reinstall rtorrent from scratch.

woow its downloading 100mb/s from rtorrent now :D WTF :D even Im raring :D

Does your last post mean that it is working now? If so \O/

Otherwise, having the actual error messages is helpful in troubleshooting. It sounds like your conifig settings or possibly rtorrent dependencies are a bit of a mess. There are some config. settings that you can try, that should resolve this. If the problems persist though, Arasaki is right you should consider reinstalling ru/torrent.

Too many files open osbtensibly means that there isn't enough resources e.g. mapped memory/handles/sockets to work with the active torrents. so.. try the more conservative .rtorrent.rc changes below. Once it is stable, then you can try tweaking for performance if you wish. But stability first.

.rtorrent.rc

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

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

# Maximum number of simultaneous uploads per torrent.
max_uploads = 20

#network.max_open_files.set = 256
#network.send_buffer.size.set = 4M
#network.receive_buffer.size.set = 4M
max_open_files = 128
#send_buffer_size = 1M
#receive_buffer_size = 25K
#max_open_sockets = 768
#use_udp_trackers = yes
max_memory_usage = 3500M

If that is stable and resolves the errors, you could try choosing preload type 1 (madvise) and uncommenting the buffer size statements.

If you can check the OS buffer sizes too that would be great
$ cat /proc/sys/net/ipv4/tcp_wmem