From: Mark Wielaard <mark@klomp.org>
To: overseers@sourceware.org
Cc: patchwork-admin@sourceware.org
Subject: mysql/patchwork overload
Date: Tue, 26 Dec 2023 06:28:04 +0100 [thread overview]
Message-ID: <20231226052804.GI6896@gnu.wildebeest.org> (raw)
Hi,
I haven't done a full analyzis yet, but from aprox 03:53 to 04:33 UTC
mysqld was completely overloaded taking 20+ cores are 100%. At the
same time patchwork was sending 1000+ emails to the patchwork admins
about being unable to access mysql. So I assume this was a spider/bot
attack on patchwork. But it also took out bugzilla.
For now all I did was stop patchwork, restart mysql and then started
patchwork again. This seems to have resolved the issue for now.
I also added one specific ip address 47.76.35.19 (Alibaba Cloud) to
the block.include list that did about ~20.000 requests to patchwork
around that time.
The same ip address was blocked earlier (December 8th) because it was
doing a great amount of bugzilla buglist queries. In the Christmas
spirit it was unblocked a few days ago. But I cannot say I am feeling
the Christmas spirit right now.
It might just have been lots of requests, but an analysis of which
specific queries cause mysqld to use up so much cpu time would be
helpful.
Merry Christmas,
Mark
next reply other threads:[~2023-12-26 5:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-26 5:28 Mark Wielaard [this message]
2023-12-27 19:44 ` Mark Wielaard
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=20231226052804.GI6896@gnu.wildebeest.org \
--to=mark@klomp.org \
--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).