Tracker stats.

[danomac]

I've been doing some reconfiguring to tracker.danomac.org and have had complaints of the scrape output not working. I've noticed some here on asuki have that issue and some don't (was looking at A-Kraze's Angel Heart) and was wonder if you could tell me what URL it's using to scrape and what the return code is (if possible...)

Hopefully I can isolate this problem and fix it.

If it's too much work don't bother, I'll do more thorough testing on the weekend. I did some quick checks and it seems to be working, so I'm left scratching my head. :twitch:

[GHDpro]

The only "tracker.danomac.org" entry marked as "down" on our database is the one operating on port 7000. The port 80 entry works fine.

I realize you also have the tracker working on ports 7001 and up, but unfortunately my scripts don't support scanning trackers other than the primary one yet (there is still lots of legacy code that doesn't support every BT feature, even stuff that's considered a basic feature these days).

This is the output I get from my scripts:tracker.danomac.org
( http://tracker.danomac.org:7000/tracker.php/announce/scrape -- last scan: 3.38 s -- 142.179.93.187 )

Contacting site...OK (http return code: 400)
Time: 3.2632 seconds
Data downloaded: 0.04 Kb. (37 bytes)

Warning: Invalid scrape page.

Tracker output:
This file is for BitTorrent clients.

Stats
Time: 0.0170 seconds
Files tracked: 0
Files updated: 0

It appears your tracker software is locking my scripts out based on the HTTP User Agent it sends, which IMHO I think is wrong. But that's just a guess. The user agent string my scripts send is "Mozilla/4.0 (compatible; MSIE 6.0; AnimeSuki)".

I'm still planning a rewrite of my "trackerscan" script btw, and in the rewrite I'll make it so that my scripts spoof the user agent of a random BT client. But the rewrite is far from ready yet.

Edit:
I just noticed my scripts got the scrape URL slightly wrong. I'm testing again with fixed URL (/announce taken out of the URL)

Edit 2:
No, no change even when using this scrape URL: http://tracker.danomac.org:7000/tracker.php/scrape

[danomac]

The only "tracker.danomac.org" entry marked as "down" on our database is the one operating on port 7000. The port 80 entry works fine.


Ahh, my quick check only consisted of port 80. Part of the restructuring/reconfiguration is to remove all announces and scrapes from port 80. Port 80 will not respond to tracker announces and scrape requests in a bit. (An error placeholder will be left in place for a while to inform users.)



I realize you also have the tracker working on ports 7001 and up, but unfortunately my scripts don't support scanning trackers other than the primary one yet (there is still lots of legacy code that doesn't support every BT feature, even stuff that's considered a basic feature these days).


My external stats scanner script on the tracker isn't multitracker aware either... I want to fix that but I never seem to get around to it.


It appears your tracker software is locking my scripts out based on the HTTP User Agent it sends, which IMHO I think is wrong. But that's just a guess. The user agent string my scripts send is "Mozilla/4.0 (compatible; MSIE 6.0; AnimeSuki)".


I don't filter scrape requests at all. I see no need to. Actually, the client HTTP User Agent check comes after the scrape processing in the tracker script.

Ah-ha! It appears after reconfiguring the tracker to use lighttpd in CGI mode on ports 7000-7004 it stopped. Apparently it's not passing the '/scrape' to the script so it assumes it's a normal announce.

Darn it, I shouldn't have started messing with the tracker when the hockey playoffs are on. :heh:

I am likely going to have to change the announce URL to http://tracker.danomac.org:7000/announce.php for all active torrents (I just tested http://tracker.danomac.org:7000/scrape.php and it does indeed work.)

I'm going to try to fix it after work today with one eyeball on the hockey game. :eyespin:

I'll post in here when I get all the changes done. Is it hard to change all the announce URLs for tracker.danomac.org in the asuki database?

[GHDpro]

That makes sense actually: if the tracker software can't see the request is for the scrape page, it might think it's for the announce instead, in which case it expects certain arguments to be passed and upon the absense of those arguments displays that error message.

Anyway... chaning the announce URLs isn't hard... trackers are automatically added to the database when a new one is found inside a torrent, and it's easy for any staff member to edit the announce and most importantly scrape URL manually.

In this case though it might be better to have my scripts "rescan" the torrents to update the changes automatically.

[danomac]

Okay, it looks like I've resolved it. I've changed all the existing torrents to the new announce URLs, so you can either update your database or re-sync.

Some groups have the torrents on their website, and those may not be changed quite yet.

Here's the announce URLs:

http://tracker.danomac.org:7000/announce.php
http://tracker.danomac.org:7001/announce.php
http://tracker.danomac.org:7002/announce.php
http://tracker.danomac.org:7003/announce.php
http://tracker.danomac.org:7004/announce.php

And of course the scrapes are:
http://tracker.danomac.org:7000/scrape.php
http://tracker.danomac.org:7001/scrape.php
http://tracker.danomac.org:7002/scrape.php
http://tracker.danomac.org:7003/scrape.php
http://tracker.danomac.org:7004/scrape.php

As of June 1st the tracker will not be answered requests on port 80 for announces/scrapes. I'll leave a placeholder with an error message to remind users to redownload their torrents.