Transmission

Thanks x190. I've installed those.

I don't really need help with the scripting but what I am struggling with is trackers and registration of the torrents - or maybe I should just use magnet files?

I have what is probably a fairly simple requirement but one which I am struggling to implement.

My remote server runs a weekly cron job which produces a zip file and makes that file available for public ftp download. The file contains a full backup of a hosted web site together with instruction on ...

IPv4 DHT not ready (broken, 1 nodes) (tr-dht.c:590)
That may be quite normal. You just need to wait longer; it could take 30-60 min to get enough good nodes.

I've waited over 2 weeks now - with many other torrents too. Still not a single byte in or out with the 'broken nodes' number raching 15 ...

Specific error messages might help.
Already posted in previous thread https://forum.transmissionbt.com/viewtopic.php?f=2&t=14964

Here it is again - log level set to 3:

[20:17:24.956] Transmission 2.76 (13786) started (session.c:722)
[20:17:24.956] Couldn't read "/var/lib/transmission/stats ...

I'm pretty sure that 51413 IS open for both protocols, since the Web UI reports it as open and Nmap reports it as Open/TCP and Open|filtered/UDP. I will check the UDP thing by other means though.

So, if it IS open and those are the only required open ports, why does neither DHT or connectionn to ...

For background on my experience leading to this post ,
from the past few days:
https://forum.transmissionbt.com/viewtopic.php?f=2&t=14964

and from 18 months-2 years ago ago:
https://forum.transmissionbt.com/viewtopic.php?f=2&t=11401
https://forum.transmissionbt.com/viewtopic.php?f=2&t=12522 ...

I have had those two ubuntu torrents loaded for nearly 3 days now and still not a byte in or out.

I tried a traceroute to the trackers. That revealed that the probe packets could not exit (or maybe just the replies get back to) the server. Investigation shows that, by default, traceroute uses udp ...

I have been running T on a Centos 5.5 vps for a couple of years now. See these threads for the issues I faced when I started:
https://forum.transmissionbt.com/search.php?search_id=egosearch
The installation worked out-of-the-box and ran with no issues for over 2 years - (used only for distributing ...

Thanks for all the help with this. I've learned a lot.

Still haven't got it working on the offending vps but a fresh install on another of my vps's worked out-of-the-box and I can live with it on just that machine for now.

No time to get to the bottom of the problem but it does appear to be a vps ...

Thanks rb07. It was your help that got me going with Transmission originally back in March this year. Much appreciated.

The following are examples of the connection errors I am getting:
1. Announce error: Could not connect to tracker
http://torrent.ubuntu.com:6969
http://linuxtracker.org:2710

2 ...

Thanks for that Gunzip.

This is what that 'Nstat' command returns - while Transmission is running with 3 x torrents, all paused:
tcp 0 0 0.0.0.0:9091 0.0.0.0:* LISTEN 102 336407411 27895/transmission-
tcp 0 0 0.0.0.0:51413 0.0.0.0:* LISTEN 102 336407412 27895/transmission-
tcp 0 0 127.0.0.1:9091 ...

My Transmission Daemon has been running fine for about 6 months (two version upgrades done in that time - presently on Centos 2.33). It runs on a remote vps and I use the web client.

Transmission stopped working at about the same time my provider upgraded the vps and I suspect they have altered ...

I guess the UDP thing is probably at the root of the my Magnet links problem too. The only ones I have tried have the trackers hosted at openbittorrent .com which uses only UDP.

Thanks for all your help rb07 - much appreciated.

Any idea of a timeframe on v2.30?

Do these show "got 0 peers" and a non-zero number of Leechers (on the tracker info)?

Sorry. Seeding is OK now. Just the Magnet links not working.

Also, there does seem to be a problem connecting to some trackers, notably:
udp://tracker.example.com:80/announce
which is the one used most ...

I've got the port open now - transmission-remote --port-test reports "Yes". Also DHT is enabled.

However, problems remain exactly as before: ie No seeding occurs and attempts to use Magnet links produce a red progress-bar outline and the messages:
Downloading from 0 of 0 peers - DL: 0.0 KiB/s UL ...