I'll be pressing the button around 12:00 UTC on Saturday 6 April. Go outside or something while it's happening.
Update, 13:17 UTC: aaaand we're back!
Providing technical information, status reports and other random information about RationalWiki
I'll be pressing the button around 12:00 UTC on Saturday 6 April. Go outside or something while it's happening.
Update, 13:17 UTC: aaaand we're back!
Linode (our hosting company) has discovered hardware problems, with action to start at 0100 UTC tomorrow morning:
We continuously monitor the health of our equipment, and we've been alerted to an issue with the physical hardware on which your Linode resides. Specifically, there is a hardware issue with the RAID system which could cause data loss. Your Linode needs to be migrated to a new server immediately to avoid extended downtime or data loss. Due to the severity of this issue, we decided that an emergency migration is more prudent than scheduling maintenance.
The maintenance will start on Saturday, August 5 at 9PM EDT (Sunday, August 6 at 1AM UTC).
When your Linode migrates, it will be cleanly shutdown, migrated to its new hardware, and then returned to its last state (running or powered off). You can monitor your position in the migration queue from your Linode’s Dashboard. All of your data and any IP addresses assigned to your Linode will be migrated as well. The migration process will move your Linode’s disk images at the rate of 3-5 GB of data per minute.
Update: Completed without problems.
Tim Starling from Wikimedia has kindly helped upgrade RationalWiki to MediaWiki 1.27. This will be going live shortly. This should bring us many functionality and security improvements.
In the process, Tim discovered that, in February 2017, the RationalWiki site was breached and the site's user table was downloaded. The user table contained:
Users should change their password, and change it anywhere else they've used that password.
Tim thinks the breach was a drive-by opportunist, rather than someone targeting RW specifically.
With the kind volunteer assistance of Tim Starling (from Wikimedia), we're working on shuffling the RationalWiki servers around and upgrading at last.
First thing in the programme: around 1400 UTC today (3pm BST, 10am EDT, 7am PDT), David is about to repoint DNS at apache1, and switch off and delete the Squids and the load balancer. Users should notice no effect, but we'll be keeping watch.
Next up: set up new servers with up-to-date software, SSL termination at last ...
Update: All done. You should have seen no effect whatsoever. More to come!
This MySQL bug has shown up again. I am at the day job right now but will be attending to this from about 1900 UTC.
Update: All appears well, it was MySQL having a conniption. Now replacing it with MariaDB ...
Update: Recovered now. A dizzying array of backup mechanisms will be put into place ... tomorrow.
RationalWiki uses images from Wikimedia Commons where available, via the InstantCommons mechanism. This broke last week because Commons' API went HTTPS-only. This is fixed on RW now, though you will see HTTP pages with HTTPS images.
(yes, we still need to get around to HTTPS on the wiki itself)
After much puzzling around MySQL, it seems apache2 was hammering the living my-goodness out of the MySQL instance on apache1. There is no obvious reason for this to have occurred ... but I disabled Apache on apache2 on the assumption that flying on one engine beats crashing on two. Investigation proceeds, further hiccups may occur.
Update: The answer: MySQL on apache1 saw apache2 as coming from its internal IP, so connections from it hung when it tried a reverse DNS lookup on this IP. Simple fix: skip-name-resolve in my.cnf.
RationalWiki just got sued by Kent Hovind. The lawsuit is a comedy classic and will brighten your Friday afternoon. (Saloon Bar discussion.)
We're not worried about the suit — the worry is that we're about to get a zillion well-wishers hammering the server. Trent is frantically rejigging our setup as we write this, pressing a spare box into service. More news as it comes, and if the site entirely vanishes please try again five minutes later ...
Update, next day: We quickly spun up a 4GB Linode to just put Apache on (MediaWiki scales horizontally really well). It appears that Apache was taking lots of CPU, not MySQL! So we've split Apache for the main site between the two boxes (the old 8GB and the new 4GB) and the setup is ticking along nicely. Trent may have some nice graphs later.
Haven't checked the Squid logs as to what it is —I suspect fallout from the Nye/Ham debate. But we're getting a buttload of requests, a lot of Apache processes, load around 50-55, MySQL using 70% of CPU after a restart ... we're not actually running out of memory, the wiki's just legitimately doing a lot of work. So page loads are often working, but taking up to a minute, and there's lots of timeouts. David's keeping an eye on stuff.
Edit: It doesn't look like any particular article. Our creationism stuff in general is getting lots of hits. While youre waiting, here's today's Google cache of "How come there are still monkeys?"
Edit 2: Still very highly loaded, but is serving up pages now, if very slowly.
The Apache server is being a dick. It keeps dying with unkillable zombie processes; these don't serve data, but they do keep their hold on port 80. The only workaround is to reboot the server. This is, of course, ridiculous. I've put a ticket in with Linode. Anyone got ideas? It's just the standard Ubuntu apache2 package.
Update: Apache was causing kernel oopses. (Things that make you go "wtf.") Linode suggest using kernel 3.9-linode instead of 2.6-linode (the default for Ubuntu 10.04, which our box runs on). We'll see how that goes next reboot. Might even fix the white-screening blog too.
The wiki has been really slow all day. The Apache server and the Squids appear quite happy with life - but the load balancer is reporting huge traffic spikes. More information as I have it.
(The blogs are unaffected, as they're served directly from the Apache server.)
Update: Here's the load balancer connections per second. (The gaps are when logging is killed to increase throughput or something.) Note the bit where we go from a few tens of queries a second up to 800 a second.