Opened 11 years ago

Closed 11 years ago

#3623 closed Bug (invalid)

Transmission-daemon can't connect to more than 60 peers per torrent

Reported by: soulreaver1 Owned by:
Priority: Normal Milestone: None Set
Component: Transmission Version: 2.04
Severity: Normal Keywords:
Cc:

Description

I have a problem with peers limit per torrent. There is always 60 peers available per file (maximum), even if I have changed "peer-limit-per-torrent" value to 200 in settins.json file.

part of my settings.json file:

    "peer-limit-global": 600,
    "peer-limit-per-torrent": 200,
    "peer-port": 48532,
    "peer-port-random-high": 65535,
    "peer-port-random-low": 49152,
    "peer-port-random-on-start": false,
    "peer-socket-tos": 0,
    "pex-enabled": true,
    "port-forwarding-enabled": true,

Tracker section in transmission web interface says:

Seeders: 317 Leechers: 3301

I have checked this utorrent file in utorrent. It has connected over 300 peers in a moment, so I think is a transmission issue.

other info:

OS: Slax (6.12) peer-port is Open

Attachments (1)

zrzut_ekranu-1.png (81.9 KB) - added by soulreaver1 11 years ago.
web_interface_screen

Download all attachments as: .zip

Change History (5)

Changed 11 years ago by soulreaver1

web_interface_screen

comment:1 follow-up: Changed 11 years ago by charles

Please try these steps in order:

  1. exit transmission-daemon
  2. edit settings.json to set the maximum number of peers per torrent
  3. run "transmission-daemon --dump-settings ${args}" where ${args} are the arguments you usually start transmission-daemon with

In the dump from step 3, what does the peer-limit-per-torrent line say?

comment:2 in reply to: ↑ 1 Changed 11 years ago by soulreaver1

Replying to charles:

Please try these steps in order:

  1. exit transmission-daemon
  2. edit settings.json to set the maximum number of peers per torrent
  3. run "transmission-daemon --dump-settings ${args}" where ${args} are the arguments you usually start transmission-daemon with

In the dump from step 3, what does the peer-limit-per-torrent line say?

transmission-daemon --dump-settings gives: peer-limit-per-torrent": 200, just what I have set in settings.json. I've noticed that other torrent (added after modification of settings.json) has connected to 120 peers, but settings has no effect on first torrent file (there is still 60 peers)...

Last edited 11 years ago by soulreaver1 (previous) (diff)

comment:3 follow-up: Changed 11 years ago by Longinus00

Changing the maxpeers in settings.json only affects new torrents. Old torrents don't have the changes retroactively applied to them, use transmission-remote to accomplish that.

As an aside, this issue has come up before in the forums/on irc. Maybe it would be a good idea to add a "use global settings" to the torrent's maxpeer value?

comment:4 in reply to: ↑ 3 Changed 11 years ago by charles

  • Resolution set to invalid
  • Status changed from new to closed

Replying to Longinus00:

Changing the maxpeers in settings.json only affects new torrents. Old torrents don't have the changes retroactively applied to them, use transmission-remote to accomplish that.

I think you've hit the nail on the head. You can use transmission-remote or the Qt remote to change the peer limit for torrents that have already been added.

As an aside, this issue has come up before in the forums/on irc. Maybe it would be a good idea to add a "use global settings" to the torrent's maxpeer value?

Probably a good idea. At that point we might want to consider reworking the "Options" tab in the torrent properties dialog, since everything except Torrent Priority will then default to just using the session's settings.

At any rate, this enhancement belongs in a different ticket. Closing the current ticket as invalid.

Note: See TracTickets for help on using tickets.