diagnosing "Magnetized transfer - retrieving metadata (0.00%)"

Ask for help and report issues not specific to either the Mac OS X or GTK+ versions of Transmission
Post Reply
me2017
Posts: 3
Joined: Sat Jun 24, 2017 3:23 pm

diagnosing "Magnetized transfer - retrieving metadata (0.00%)"

Post by me2017 » Fri Jun 30, 2017 3:12 am

All of my torrents are stuck. If I give transmission a .magnet file it hangs on "Magnetized transfer - retrieving metadata (0.00%)". If a .torrent file "0B of x Mb (0.00%) - remaining time unkown"
transmission.png
transmission.png (28.06 KiB) Viewed 8478 times
Below is my diagnosis. Please any suggestions. This is transmission-daemon-2.92 on CentOS 7.

Code: Select all

---
transmission-remote  -t 64 --info
NAME
  Id: 64
  Name: CentOS-7-x86_64-Minimal-1611
  Hash: 8773903224a4b9571004cbd95f98a3533224a167
  Magnet: magnet:?xt=urn:btih:8773903224a4b9571004cbd95f98a3533224a167&dn=CentOS-7-x86%5F64-Minimal-1611&tr=http%3A%2F%2Ftorrent.centos.org%3A6969%2Fannounce&tr=http%3A%2F%2Fipv6.torrent.centos.org%3A6969%2Fannounce

TRANSFER
  State: Idle
  Location: /ddb2233/torrents
  Percent Done: 0.0%
  ETA: 0 seconds (0 seconds)
  Download Speed: 0 kB/s
  Upload Speed: 0 kB/s
  Have: None (None verified)
  Availability: 0.0%
  Total size: 713.0 MB (713.0 MB wanted)
  Downloaded: None
  Uploaded: None
  Ratio: None
  Corrupt DL: None
  Peers: connected to 0, uploading to 0, downloading from 0

HISTORY
  Date added:       Thu Jun 29 15:53:03 2017
  Date started:     Thu Jun 29 15:53:03 2017
  Downloading Time: 10 minutes (633 seconds)

ORIGINS
  Date created: Thu Dec  8 06:25:47 2016
  Public torrent: Yes
  Comment: CentOS x86_64 Minimal ISO
  Creator: mktorrent 1.0
  Piece Count: 1361
  Piece Size: 512.0 KiB

LIMITS & BANDWIDTH
  Download Limit: Unlimited
  Upload Limit: Unlimited
  Ratio Limit: Default
  Honors Session Limits: Yes
  Peer limit: 60
  Bandwidth Priority: Normal


---
transmission-remote  -t 64 -it

  Tracker 0: http://torrent.centos.org:6969
  Active in tier 0
  Got an error "Could not connect to tracker" 4 minutes (273 seconds) ago
  Asking for more peers in 26 minutes (1574 seconds)
  Got a scrape error "Could not connect to tracker" 10 minutes (640 seconds) ago
  Asking for peer counts in 5 minutes (310 seconds)

  Tracker 1: http://ipv6.torrent.centos.org:6969
  Active in tier 1
  Got an error "Could not connect to tracker" 6 minutes (398 seconds) ago
  Asking for more peers in 24 minutes (1454 seconds)
  Got a scrape error "Could not connect to tracker" 10 minutes (620 seconds) ago
  Asking for peer counts in 5 minutes (300 seconds)


---

transmission-remote  -t 65 --info
NAME
  Id: 65
  Name: Cannabis+Collection+-+Reefer+Madness+(1936)+-+Colorized+and+Rest
  Hash: 473f022cfaf5b02082d1c7d88fe8f8eb93e9680c
  Magnet: magnet:?xt=urn:btih:473f022cfaf5b02082d1c7d88fe8f8eb93e9680c&dn=Cannabis%2BCollection%2B-%2BReefer%2BMadness%2B%281936%29%2B-%2BColorized%2Band%2BRest&tr=udp%3A%2F%2Ftracker.leechers-paradise.org%3A6969&tr=udp%3A%2F%2Fzer0day.ch%3A1337&tr=udp%3A%2F%2Fopen.demonii.com%3A1337&tr=udp%3A%2F%2Ftracker.coppersurfer.tk%3A6969&tr=udp%3A%2F%2Fexodus.desync.com%3A6969

TRANSFER
  State: Idle
  Location: /ddb2233/torrents
  Percent Done: nan%
  ETA: 0 seconds (0 seconds)
  Download Speed: 0 kB/s
  Upload Speed: 0 kB/s
  Have: None (None verified)
  Availability: None
  Availability: nan%
  Total size: None (None wanted)
  Downloaded: None
  Uploaded: None
  Ratio: None
  Corrupt DL: None
  Peers: connected to 0, uploading to 0, downloading from 0

HISTORY
  Date added:       Thu Jun 29 16:01:26 2017
  Date started:     Thu Jun 29 16:01:26 2017
  Downloading Time: 23 seconds (23 seconds)

ORIGINS
  Public torrent: Yes
  Piece Count: 0
  Piece Size: None

LIMITS & BANDWIDTH
  Download Limit: Unlimited
  Upload Limit: Unlimited
  Ratio Limit: Default
  Honors Session Limits: Yes
  Peer limit: 60
  Bandwidth Priority: Normal


  ---
  transmission-remote  -t 65 -it

  Tracker 0: udp://tracker.leechers-paradise.org:6969
  Active in tier 0
  Got an error "Connection failed" 3 minutes, 54 seconds (234 seconds) ago
  Asking for more peers in 1 minute, 49 seconds (109 seconds)
  Got a scrape error "Connection failed" 2 minutes, 30 seconds (150 seconds) ago
  Asking for peer counts in 13 minutes (816 seconds)

  Tracker 1: udp://zer0day.ch:1337
  Active in tier 1
  Got an error "Connection failed" 1 minute, 28 seconds (88 seconds) ago
  Asking for more peers in 13 minutes (837 seconds)
  Got a scrape error "Connection failed" 2 minutes, 30 seconds (150 seconds) ago
  Asking for peer counts in 3 minutes, 16 seconds (196 seconds)

  Tracker 2: udp://open.demonii.com:1337
  Active in tier 2
  Got an error "Connection failed" 2 minutes, 30 seconds (150 seconds) ago
  Asking for more peers in 2 minutes, 55 seconds (175 seconds)
  Got a scrape error "Connection failed" 1 minute, 12 seconds (72 seconds) ago
  Asking for peer counts in 13 minutes (836 seconds)

  Tracker 3: udp://tracker.coppersurfer.tk:6969
  Active in tier 3
  Got an error "Connection failed" 3 minutes, 52 seconds (232 seconds) ago
  Asking for more peers in 1 minute, 11 seconds (71 seconds)
  Got a scrape error "Connection failed" 2 minutes, 19 seconds (139 seconds) ago
  Asking for peer counts in 13 minutes (796 seconds)

  Tracker 4: udp://exodus.desync.com:6969
  Active in tier 4
  Got an error "Could not connect to tracker" 4 minutes (277 seconds) ago
  Asking for more peers in 52 seconds (52 seconds)
  Got a scrape error "Could not connect to tracker" 3 minutes, 54 seconds (234 seconds) ago
  Asking for peer counts in 11 minutes (706 seconds)
  


These are attempts at using netcat to diagnose. I'm unsure if this tells me much about the UDP connections (it's successful with any port). At minimum it reflects that I can resolve and reach each of these trackers.

Code: Select all

# nc -v ipv6.torrent.centos.org 6969 </dev/null
Ncat: Version 6.40 ( http://nmap.org/ncat )
Ncat: Network is unreachable.

# nc -v -u tracker.leechers-paradise.org 6969 </dev/null
Ncat: Version 6.40 ( http://nmap.org/ncat )
Ncat: Connected to 87.233.192.220:6969.
Ncat: 0 bytes sent, 0 bytes received in 0.01 seconds.

# nc -v -u zer0day.ch 1337 </dev/null
Ncat: Version 6.40 ( http://nmap.org/ncat )
Ncat: Connected to 72.52.4.120:1337.
Ncat: 0 bytes sent, 0 bytes received in 0.01 seconds.

# nc -v -u open.demonii.com 1337 </dev/null
Ncat: Version 6.40 ( http://nmap.org/ncat )
Ncat: Connected to 104.27.130.137:1337.
Ncat: 0 bytes sent, 0 bytes received in 0.03 seconds.

# nc -v -u tracker.coppersurfer.tk 6969 </dev/null
Ncat: Version 6.40 ( http://nmap.org/ncat )
Ncat: Connected to 62.138.0.158:6969.
Ncat: 0 bytes sent, 0 bytes received in 0.01 seconds.

# nc -v -u exodus.desync.com 6969 </dev/null
Ncat: Version 6.40 ( http://nmap.org/ncat )
Ncat: Could not resolve hostname "exodus.desync.com": Name or service not known. QUITTING

me2017
Posts: 3
Joined: Sat Jun 24, 2017 3:23 pm

Re: diagnosing "Magnetized transfer - retrieving metadata (0.00%)"

Post by me2017 » Fri Jun 30, 2017 9:09 pm

Would anyone have any tips on troubleshooting?

Dragfuka
Posts: 1
Joined: Thu Jul 06, 2017 8:22 am

Re: diagnosing "Magnetized transfer - retrieving metadata (0.00%)"

Post by Dragfuka » Thu Jul 06, 2017 8:29 am

Hi,

I've got the same issue.

I don't understand anything to the code or diagnosis but I've noticed that it depends on Traker (sometimes even a same website will have different trakers that will have different results).

Issues from the trakers?

amplatfus
Posts: 2
Joined: Sun Feb 25, 2018 12:39 pm

Re: diagnosing "Magnetized transfer - retrieving metadata (0.00%)"

Post by amplatfus » Sun Feb 25, 2018 12:41 pm

Hi,

I have the same problem. Please, did you find the fix? Thanks!

Post Reply