Transmission on debian failing to retrieve magnetized data

[hadware]

Hello,

I've searched a lot if this problem was already met somewhere else, but i can't find anything looking like it.
I have a headless debian-squeeze server running transmission, and transmission-deamon. It works pretty flawlessly, except for one thing: it won't download the magnetized data.
If i give it a magnet link, it adds a torrent correctly, and then proceeds to the "retrieving metadata" step... but never completes it. The weird thing is that it downloads about ~10% of it, and then falls back to 0.
If I give it a .torrent file, everything works fine. It's really this one client that screws up, because my transmission client running on ubuntu does it in a matter of seconds, on the same connection/network.
Could you please give me clues to where i could look to find my error?

Thanks a lot for any help provided.

[rb07]

You need more details to see where the problem is.

Look at the original magnet link, does it have a tracker url? or only a hash code... With the first case Transmission gets the metadata from the tracker or trackers on the magnet link. With the second Transmission needs DHT enabled (I think, not 100% sure, perhaps PEX also works but I have DHT enabled, PEX disabled) to get the metadata from the DHT cloud.

If the magnet has URL(s) then the problem is probably a network problem. A recent case turned out to be that the server could not resolve DNS names, but there are other possibilities.

Perhaps comparing the 2 configurations (desktop and server) could point something out. I mean comparing settings.json, not something else. I assume they use different ports, but that shouldn't affect magnets.

[hadware]

Here's an example of the magnet link i could have used. The torrent is well-seeded, and i tried downloading it with my Ubuntu laptop (as i said, on the same LAN), and it worked perfectly.

---- removed to prevent from getting banned ----

As you can see, it provides the tracker URLs...

I'll look up the JSON files, however which one should I use? Since the server version of transmission is started using tr-deamon, and the laptop version is run from my user session...
I did tweaked a bit the config, here's the json file from the server.

Code: Select all

{
    "alt-speed-down": 5, 
    "alt-speed-enabled": false, 
    "alt-speed-time-begin": 120, 
    "alt-speed-time-day": 127, 
    "alt-speed-time-enabled": true, 
    "alt-speed-time-end": 540, 
    "alt-speed-up": 5, 
    "bind-address-ipv4": "0.0.0.0", 
    "bind-address-ipv6": "::", 
    "blocklist-enabled": false, 
    "dht-enabled": true, 
    "download-dir": "/home/torrentflux/transmission", 
    "encryption": 1, 
    "incomplete-dir": "/home/torrentflux/", 
    "incomplete-dir-enabled": false, 
    "lazy-bitfield-enabled": true, 
    "lpd-enabled": false, 
    "message-level": 2, 
    "open-file-limit": 32, 
    "peer-limit-global": 240, 
    "peer-limit-per-torrent": 60, 
    "peer-port": 51413, 
    "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, 
    "preallocation": 1, 
    "proxy": "", 
    "proxy-auth-enabled": false, 
    "proxy-auth-password": "", 
    "proxy-auth-username": "", 
    "proxy-enabled": false, 
    "proxy-port": 80, 
    "proxy-type": 0, 
    "ratio-limit": 2.0000, 
    "ratio-limit-enabled": true, 
    "rename-partial-files": true, 
    "rpc-authentication-required": true, 
    "rpc-bind-address": "0.0.0.0", 
    "rpc-enabled": true, 
    "rpc-password": "**************************************", 
    "rpc-port": 9091, 
    "rpc-username": "hadware", 
    "rpc-whitelist": "127.0.0.1", 
    "rpc-whitelist-enabled": false, 
    "script-torrent-done-enabled": false, 
    "script-torrent-done-filename": "", 
    "speed-limit-down": 100, 
    "speed-limit-down-enabled": false, 
    "speed-limit-up": 100, 
    "speed-limit-up-enabled": false, 
    "start-added-torrents": true, 
    "trash-original-torrent-files": false, 
    "umask": 18, 
    "upload-slots-per-torrent": 14
}

I'll try setting incomplete to true and see what happens.
What's the "ipd-enabled" option doing?

Thanks for your answers!

[rb07]

First comment: edit what you put here, what you show is going to get you banned in this forum.

As you can see, it provides the tracker URLs...

So, as I said, its probably a network problem, not a Transmission problem.

The trackers the magnet shows are well known unreliable/overloaded trackers. Its quite usual those don't respond, or some times respond one time, not the next... I wouldn't waste time tracking down problems with them, but if you really want to test, then give them more time (like days, even weeks -- last one of those has never responded as far as I know).

I'll try setting incomplete to true and see what happens.
What's the "ipd-enabled" option doing?

Don't just move things to see what happens. Incomplete has nothing to do, and lpd (Local Peer Discovery) even less.

[hadware]

First comment: edit what you put here, what you show is going to get you banned in this forum.

As you can see, it provides the tracker URLs...

So, as I said, its probably a network problem, not a Transmission problem.

The trackers the magnet shows are well known unreliable/overloaded trackers. Its quite usual those don't respond, or some times respond one time, not the next... I wouldn't waste time tracking down problems with them, but if you really want to test, then give them more time (like days, even weeks -- last one of those has never responded as far as I know).

I'll try setting incomplete to true and see what happens.
What's the "ipd-enabled" option doing?

Don't just move things to see what happens. Incomplete has nothing to do, and lpd (Local Peer Discovery) even less.

Okay, got it.
I did not just "try to move things" to see what happens. Once i had a problem with torrents not launching, and it was because the incomplete folder didn't have the proper rights given to transmission