Opened 13 years ago
Closed 13 years ago
#1509 closed Enhancement (invalid)
multiple transmissioncli or daemon do not downloading apart on each other
| Reported by: | dzimi | Owned by: | charles |
|---|---|---|---|
| Priority: | Normal | Milestone: | None Set |
| Component: | libtransmission | Version: | 1.40 |
| Severity: | Normal | Keywords: | |
| Cc: |
Description (last modified by charles)
Hello,
I have tested this issue:
Machine number 1 has two running processes:
1a) transmissioncli -p 19338 -g /root/.one -w /root/one /root/torrent1.torrent (seeding torrent1)
1b) transmission-daemon -g /root/.two -p 12002 -w /root/two (with loaded torrent1 to download)
Machine number 2 is running OpenTracker? as tracker for torrent1.torrent and to/from this tracker is announce torrent file.
As you can see machine number 1 running two different processes on two different TCP port. Why does the transmission-daemon can not receive the data from transmission-cli? Is it transmission issue or tracker? cli and daemon don't receive the information from tracker about apart on each other or just transmission (libtransmission) ignore this data from tracker?
It would be great if this one enhancement be implemented as soon as possible. (of course if this problem depends on/in transmission or libtransmission)
Attachments (1)
Change History (8)
comment:1 Changed 13 years ago by charles
- Description modified (diff)
comment:2 Changed 13 years ago by charles
- Resolution set to invalid
- Status changed from new to closed
comment:3 Changed 13 years ago by charles
Please reopen this ticket when you attach the two debug logs.
comment:4 Changed 13 years ago by dzimi
- Resolution invalid deleted
- Status changed from closed to reopened
RE-open. Please charles - would you like see what was happen there ? Seems like peer-io.c have no idea what to do when the data is available from the same IP as he is.
comment:5 Changed 13 years ago by dzimi
Hmm, I tested another one version and I saw this problem does not exist in transmission-1.34. I will send here logs with using TR_DEBUG_FD. I hope this will help.
comment:6 Changed 13 years ago by charles
This ticket appears to be the same as #1574. Are they the same problem?
comment:7 Changed 13 years ago by charles
- Resolution set to invalid
- Status changed from reopened to closed
There's not enough information in this ticket to answer the question.
Try using TR_DEBUG_FD on the cli and daemon to see what they're thinking, and attach those two log files to this ticket. You'll need to run the daemon in the foreground for this to work.