transmission-daemon don't share files

[thorleif]

Hi,

I installed bttrack as a private tracker on my ubuntu server. On my server, I use transmission-daemon in order to have a persistant client. However, when I want to download a file with my computer, my bittorrent client find peers but it can't download.

I got an error in transmission-daemon log :

Code: Select all

Couldn't bind port 6969 on 0.0.0.0: Address already in use (Is another copy of Transmission already running?) (net.c:369)

I don't know why. Can you help me.

PS : Sorry for my english

[rb07]

Use

Code: Select all

netstat -anp | grep 6969

that should tell you which application has that port, if its not a 2nd copy of transmission itself then change transmission-daemon to use another port.

[thorleif]

Thanks, I fixed it but it doesn't work.

This is transmission-daemon log :

Code: Select all

 [09:54:43.174] Transmission 1.93 (10621) started (session.c:609)
[09:54:43.174] RPC Server Adding address to whitelist: 127.0.0.1 (rpc-server.c:772)
[09:54:43.174] RPC Server Serving RPC and Web requests on port 9091 (rpc-server.c:945)
[09:54:43.174] RPC Server Whitelist enabled (rpc-server.c:949)
[09:54:43.174] RPC Server Password required (rpc-server.c:952)
[09:54:43.174] Couldn't bind port 6969 on 0.0.0.0: Address already in use (Is another copy of Transmission already running?) (net.c:369)
[09:54:43.174] DHT Reusing old id (tr-dht.c:365)
[09:54:43.174] DHT Bootstrapping from 151 nodes (tr-dht.c:146)
[09:54:43.174] Using settings from "/iscpif/users/rougier/.config/transmission-daemon"(daemon.c:425)
[09:54:43.174] Saved "/iscpif/users/rougier/.config/transmission-daemon/settings.json"(bencode.c:1651)
[09:54:43.174] transmission-daemon requiring authentication (daemon.c:429)
[09:54:43.174] Loaded 1 torrents (session.c:1683)
[09:54:43.174] Port Forwarding (NAT-PMP) initnatpmp succeeded (0) (natpmp.c:67)
[09:54:43.174] Port Forwarding (NAT-PMP) sendpublicaddressrequest succeeded (2) (natpmp.c:67)
[09:54:51.175] Port Forwarding State changed from "Not forwarded" to "Starting" (port-forwarding.c:87)
[09:54:51.175] Port Forwarding State changed from "Starting" to "???" (port-forwarding.c:87)

[rb07]

I fixed it but it doesn't work.

No you didn't:

Couldn't bind port 6969 on 0.0.0.0: Address already in use (Is another copy of Transmission already running?) (net.c:369)

and, do you really want port forwarding?

Port Forwarding (NAT-PMP) initnatpmp succeeded (0) (natpmp.c:67)
Port Forwarding (NAT-PMP) sendpublicaddressrequest succeeded (2) (natpmp.c:67)
Port Forwarding State changed from "Not forwarded" to "Starting" (port-forwarding.c:87)
Port Forwarding State changed from "Starting" to "???" (port-forwarding.c:87)

You should improve your writing skills, "fixed it but it doesn't work" is a contradiction, I guess you are leaving the important details out, what did you "fix"? and what "doesn't work"?

[thorleif]

I'm sorry, I posted an outdated log. I'm going to disable port fowarding.

I guess you are leaving the important details out, what did you "fix"? and what "doesn't work"?

I fixed the port problem but transmission-daemon doesn't share files.

New log :

Code: Select all

[16:23:30.996] Transmission 1.93 (10621) started (session.c:609)
[16:23:30.996] RPC Server Adding address to whitelist: 127.0.0.1 (rpc-server.c:772)
[16:23:30.996] RPC Server Adding address to whitelist:  (rpc-server.c:772)
[16:23:30.996] RPC Server Adding address to whitelist: 192.168.*.* (rpc-server.c:772)
[16:23:30.996] RPC Server Serving RPC and Web requests on port 9091 (rpc-server.c:945)
[16:23:30.996] RPC Server Whitelist enabled (rpc-server.c:949)
[16:23:30.996] RPC Server Password required (rpc-server.c:952)
[16:23:30.996] Port Forwarding Stopped (port-forwarding.c:176)
[16:23:30.996] DHT Reusing old id (tr-dht.c:365)
[16:23:30.996] DHT Bootstrapping from 141 nodes (tr-dht.c:146)
[16:23:30.996] Using settings from "/var/lib/transmission-daemon/info" (daemon.c:425)
[16:23:30.996] Saved "/etc/transmission-daemon/settings.json" (bencode.c:1651)
[16:23:30.996] transmission-daemon requiring authentication (daemon.c:429)
[16:23:30.996] Loaded 1 torrents (session.c:1683)
[16:23:44.998] planning ecole.xls Starting DHT announce (poor, 12 nodes) (tr-dht.c:660)

Thank you

[rb07]

Try :

Code: Select all

transmission-remote --port-test

I'm guessing that by "doesn't share files" you mean "doesn't upload", and from the tracker point of view it means you are not "connectable" (which is not even a proper word, but that's what they say)... and all that means your router/gateway is not configured correctly.

Port forwarding could solve that, but you are seeing that it doesn't, and the log section I quoted shows that something went wrong using NAT-PMP. You'll have to configure port mapping (on the router, a.k.a. modem, a.k.a. gateway).

[thorleif]

Code: Select all

$ transmission-remote -n transmission:transmission --port-test
Port is open: Yes

In fact, I have a Ubuntu server. On this server I installed a tracker and transmission-daemon. Transmission-daemon is the only bittorrent client which can publish .torrent file and it is the first seeder.

[rb07]

So the port is open, and we knew the setup (you described it on your first post, no need to repeat)... then, what do you mean by "don't share files"?

Guess: you are testing with a second computer, and your server doesn't send anything. Correct? if yes, then what are you using in the second computer, Transmission-GTK+? another transmission-daemon? what does it show in the tracker info? (I mean as number of seeders, and number of leechers).

If all of the above is about right, and you do have the one seeder which is your server, does the other client establish a connection? is the second computer on your LAN? can it access the server using the public IP address, not the LAN address?

[thorleif]

In the second computer, I use transmission-gtk. It finds the tracker. Tracker info : 1 seeder and 3 leechers (3 clients have the torrent). All the other computers are on my LAN. Yes, I can access the server using the public IP address.

[rb07]

If all computers are on the LAN they appear to be just one to the tracker (with different port perhaps, but same IP, the public IP), I'm not sure the "server" would send anything to what appears to be "itself". Since you own the tracker, couldn't you use LAN addresses for the test?

More info would be interesting:

On the 2nd computer: is there any connection reported? i.e. under the torrent, the status shows "Downloading from 0 of X connected peer(s)", what is the X?

On the server: same thing, except that the status should say "Seeding to Y of Z connected peer(s)", what's the Y and the Z?

Have you seen the server log lately, anything interesting?

[thorleif]

If all computers are on the LAN they appear to be just one to the tracker

My server (tracker) is on the LAN. All computers on the LAN got own IP. Therefore they don't need to use public IP.

On the 2nd computer: is there any connection reported? i.e. under the torrent, the status shows "Downloading from 0 of X connected peer(s)", what is the X?

Downloading from 0 of 0 connected peer(s)

On the server: same thing, except that the status should say "Seeding to Y of Z connected peer(s)", what's the Y and the Z?

Tracker had 1 seeders and 2 leechers