nago Posted September 5, 2010 Report Share Posted September 5, 2010 Hi! I've gotten the uTorrent server running on Fedora 13 [2.6.34.6-47.fc13.x86_64].I seem to be unable to start a torrent. I've had it auto-load torrents (but not start them) from a directory, and I see the torrent in the "Downloading" list, however the stats it displays are 0% completion, 0 seeds, 0 peers, and ¿? in swarm, and no errors that I can seemingly spot within the UI (like tracker errors.) I have started the torrent since it was loaded.The only error present within the UI at all is 'Request Failure #1 (Will retry in 2 seconds) action=getxferhist' --in fact this is the only entry at all in the logger in the UI.The OSD for the daemon only shows:'server startedIPv6 is installed'Where should I be looking to discern why this torrent is not doing anything? Link to comment Share on other sites More sharing options...
DreadWingKnight Posted September 5, 2010 Report Share Posted September 5, 2010 How many torrents do you have loaded and what are your queue settings? Link to comment Share on other sites More sharing options...
nago Posted September 5, 2010 Author Report Share Posted September 5, 2010 I have 47 stopped 0% torrents.(I was planning on seeding, but I realized I was not able to manually set the download location, so I just left them stopped. As an aside, is this feature planned or expected?)Queue settings are default. [8 total, 5 download, seeding stops at 150%]Status of torrent is "Downloading" and not queued. Icon is a blue arrow pointing downwards.Edit: It appears to be a tracker problem, I just tried one from a public tracker and it seems to be working just fine. It'd be nice to see the tracker errors like I can in the windows client so I can see what the problem is. Link to comment Share on other sites More sharing options...
mcdonald Posted September 7, 2010 Report Share Posted September 7, 2010 It'd be nice to see the tracker errors like I can in the windows client so I can see what the problem is.Try setting the environment variable LOGMASK to a 32-bit number in hexadecimal format - you should be able to see more messages for every set bit in that mask. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.