We will be performing maintenance on MySQL tonight to fix the 'host is
blocked because of too many connection errors' problem. This is being done
earlier than expected because it's required for the new load-balanced MySQL
servers. The total downtime should be under 20 minutes per server.
This issue is being tracked in JIRA as MNT-165.
-----BEGIN PGP SIGNED MESSAGE-----
On willow, there is no termcapinfo for linux, so I cannot use nano or
screen (possibly other stuff, but that's what I discovered). Is this
something I can fix? Something to send to JIRA? I normally use xterms,
but others may not, and it'd be nice to have ttys work as expected in
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
-----END PGP SIGNATURE-----
I am about to decommission cache.stable.toolserver.org. Requests to the
host will still work as before, but will go straight to the web server
without being cached.
This may return in the future as a cache for toolserver.org instead.
amaranth (which serves web applications including JIRA and the wiki) is
being shut down now in order to move it to a different rack. This will take
a few minutes.
Sorry about the short notice.
yarrow, the database server for s1, s3, s4 and s6, has started to use too
much memory and is swapping, which results in unacceptable performance. As
a temporary workaround we will reduce the InnoDB buffer pool size and
restart the server. The server will be offline for about 20 minutes while
I am currently importing s1 into one of the new database servers to replace
the damaged copy on rosemary. After the import is down, I will switch the
s1 server, then put it in read-only mode to copy user databases. Downtime
will be about half an hour to switch servers, and possibly a couple of hours
for user database imports.
After this is complete, we will start looking at providing redundant
(failover) databases for each cluster, starting with s1. Hopefully that
should happen within the next couple of weeks.
There is currently an open issue that is preventing updates to the
Toolserver email configuration from propagating to the mail server. This
means that email forwarding for newly created accounts is not working, and
changes to your Toolserver email address (using setmail) will not take
effect. The issue is somewhat complicated and I will be away most of this
week, so this won't be fixed until next week at the earliest. Sorry for the
This issue is being tracked in JIRA as MNT-65.