Hi,
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.
- river.
Hi,
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
it restarts.
- river.
Hi,
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.
- river.
Hi,
amaranth will be rebooted later today to upgrade its operating system. This
will result in about 5 minutes downtime of the web applications (JIRA, wiki,
etc).
- river.
Hi,
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
inconvenience.
This issue is being tracked in JIRA as MNT-65.
- river.
Hi,
In addition to the previously announced maintenance, we will perform the
following additional maintenance on Monday, 4th January depending on whether
there is enough time:
* willow will be upgraded to Solaris 10 Update 8. (Downtime: 5 minutes)
* We will add some patches to the NFS/LDAP cluster. (Downtime: about 15
seconds)
- river
Hi,
On Sunday, 3rd January around 1-2AM UTC, I will be upgrading MySQL on the
database servers. At the same time, the operating system will be upgraded.
Total downtime will be around 30 minutes to upgrade MySQL, and 5 minutes to
upgrade the OS. There should be no user-visible impact from the upgrade.
This issue is being tracked in JIRA as MNT-112.
- river.
Hi,
wolfsbane (web server) was rebooted to complete the previously announced
maintenance, and at the same time it was upgrade to Solaris 10 Update 8.
This should have no impact on users.
These issues are being tracked in JIRA as MNT-90 (/tmp issue) and MNT-108
(upgrade).
- river.