BitTorrent tracker announce flooding NGinx logs
reallfqq-nginx at yahoo.fr
Tue Feb 28 16:26:39 UTC 2012
I can also use my hosts file to redirect the old tracker to a new tracker :)
Thanks for the help, I am relieved: I thought I didn't do things properly
On Tue, Feb 28, 2012 at 04:10, Thorben Thuermer <thuermer at veeseo.com> wrote:
> On Tue, 28 Feb 2012 03:38:39 -0500 "B.R." <reallfqq-nginx at yahoo.fr> wrote:
> > I recently installed Transmission 2.03.
> > Since then I get my NGinx error log flooded with messages like "[error]
> > 21475#0: *6383 open() "/var/web/tracker.thepiratebay.org/announce"
> > (2: No such file or directory), client: 127.0.0.1, server:
> > request: "GET /announce?info_hash="
> > It seems there is a misconfiguration somewhere. Could you help me on that
> > point?
> the misconfiguration is here:
> $ host tracker.thepiratebay.org
> tracker.thepiratebay.org has address 127.0.0.1
> it's typical for disabled trackers to get pointed to localhost
> (instead of pulled from dns completely).
> nothing you can do about that really, at best some workaround to stop those
> requests from ending up in your log.
> (it's generally a good idea to set up a dummy default virtualhost that is
> used in production just so all the spam ends up in it's log.)
> - T.
> nginx mailing list
> nginx at nginx.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the nginx