| View previous topic :: View next topic |
| Author |
Message |
d4mo
Guru
Joined: 27 Jun 2005
Posts: 430
|
 Posted: Tue Oct 25, 2005 8:00 pm Post subject: rtorrent help |
 |
|
I can't seem to connect to any trackers and I'm not sure why.
It says : Tracker: [server returned nothing (no headers, no data)]
and
[Could not parse bencoded data].
Here is my config file | Code: | # 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.
# Minumum amount of peers to connect per torrent, if available.
#min_peers = 40
# Minumum amount of peers to connect per torrent.
#max_peers = 100
# Maximum number of simultanious uploads per torrent.
#max_uploads = 15
# Global download rate in KiB. "0" for unlimited.
#download_rate = 0
# Global upload rate in KiB. "0" for unlimited.
#upload_rate = 0
# Default directory to save downloaded files. Note it doesn't support
# space yet.
#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 =
# The ip address reported to the tracker.
#ip = 127.0.0.1
# The ip address the listening socket and outgoing connections is
# bound to.
#bind = 127.0.0.1
# Port range to use for listening.
port_range = 6881-6881
# 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
#
# 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
# Max number of files to keep open simultaniously.
#max_open_files = 128
# Number of sockets to simultaneously keep open.
#max_open_sockets = <no default>
# Dump data received from trackers to the files
# "./tracker_dump.<time>".
#tracker_dump = no
# Change the interval between each throttle tick, in milliseconds. In
# the range 1-5000 ms.
#throttle_interval = 1000
|
I have port 6881 forwared on my router. |
|
| Back to top |
|
 |
Kaapeli
Tux's lil' helper
Joined: 27 Dec 2004
Posts: 110
Location: Oulu, Finland
|
| Posted: Wed Oct 26, 2005 4:00 pm Post subject: |
|
|
Can you verify that it's not a tracker problem? I had this same issue with one tracker a while ago, but it got fixed by itself (apparently the tracker side problem was fixed).
_________________
Temperatures |
|
| Back to top |
|
|
d4mo
Guru
Joined: 27 Jun 2005
Posts: 430
|
| Posted: Thu Oct 27, 2005 9:11 pm Post subject: |
|
|
| You're right it was a tracker problem. In my options file I set it as port 6881-6889 and to connec to a random port. But when I open rtorrent it just picks one of the ports and runs all connections through it. Is that how it's supposed to be, or is it supposed to use all of the ports. |
|
| Back to top |
|
|
Kaapeli
Tux's lil' helper
Joined: 27 Dec 2004
Posts: 110
Location: Oulu, Finland
|
| Posted: Sat Oct 29, 2005 1:38 pm Post subject: |
|
|
I don't know why it would need more than one port. It seems quite normal (for me atleast) that is listens to only one port
_________________
Temperatures |
|
| Back to top |
|
|
|
Unsupported Software
