From: Mark Wielaard <mark@klomp.org>
To: Overseers <overseers@sourceware.org>
Cc: Joern Rennecke <joern.rennecke@embecosm.com>,
patchwork-admin@sourceware.org
Subject: Re: gcc bugzilla (and patchwork)
Date: Thu, 30 Nov 2023 09:12:27 +0100 [thread overview]
Message-ID: <20231130081227.GA29989@gnu.wildebeest.org> (raw)
In-Reply-To: <CAMqJFCqWgN8APw-NmPLpu4=HPU4i78wiB1zAArVYmxiWm9Zm-g@mail.gmail.com>
Hi,
On Thu, Nov 30, 2023 at 05:14:04AM +0000, Joern Rennecke via Overseers wrote:
> When I try to go to https://gcc.gnu.org/bugzilla/ (e.g. following the
> bug data base link from the gcc .homepage), I get web page with an
> error message:
>
> Software error:
>
> Can't connect to the database.
> Error: Too many connections
bugzilla and patchwork seem to have been hit by some agressive bots.
I put blocks for ip ranges belonging to msnbot, bot@semrush.com and
sogouspider on our block.include list.
Things should work again.
We do have to look at the logging/warning reporting of patchwork. It
sent an email for each failing request to the admins, which wasn't fun
and made matters worse by sending thousands of emails from the
overloaded system.
Cheers,
Mark
prev parent reply other threads:[~2023-11-30 8:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-30 5:14 gcc bugzilla Joern Rennecke
2023-11-30 8:12 ` Mark Wielaard [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231130081227.GA29989@gnu.wildebeest.org \
--to=mark@klomp.org \
--cc=joern.rennecke@embecosm.com \
--cc=overseers@sourceware.org \
--cc=patchwork-admin@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).