Apparently the tracker has been unresponding for some time now, although port 80 still accepts connections. Regards Antoine.
On 5/11/2010 7:16 PM, Antoine Pitrou wrote:
Apparently the tracker has been unresponding for some time now, although port 80 still accepts connections.
As I reported before, there have been on and off problems for days. Messages like (minutes ago) upon trying to login: "Service Temporarily Unavailable The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later. Apache/2.2.9 (Debian) mod_python/3.3.1 Python/2.5.2 mod_ssl/2.2.9 OpenSSL/0.9.8g Server at bugs.python.org Port 80" Now I retry and it works.
On Wed, 12 May 2010 13:09:11 -0400, Terry Reedy
On 5/11/2010 7:16 PM, Antoine Pitrou wrote:
Apparently the tracker has been unresponding for some time now, although port 80 still accepts connections.
As I reported before, there have been on and off problems for days. Messages like (minutes ago) upon trying to login:
"Service Temporarily Unavailable
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later. Apache/2.2.9 (Debian) mod_python/3.3.1 Python/2.5.2 mod_ssl/2.2.9 OpenSSL/0.9.8g Server at bugs.python.org Port 80"
Now I retry and it works.
That last was us restarting roundup, which cured the problem at least temporarily. We've added a robots.txt file to hopefully slow down the bot hits (which are the bulk of the traffic on the tracker) once they bother to notice it. I'm not convinced that hit count load is the problem, but it might be. -- R. David Murray www.bitdance.com
participants (3)
-
Antoine Pitrou
-
R. David Murray
-
Terry Reedy