We’ve finished upgrading all our Web hosting servers to use MySQL 5.0.32, as we explained in this earlier post. The total time that MySQL databases were unavailable averaged about ten minutes per server. Again, we regret any downtime — this was unavoidable for such a major upgrade.
You should not notice any difference in how your site operates. In the unlikely event you have any problems, please contact us by opening a ticket so we can help.
This coming Saturday (August 4th), we’ll be upgrading the MySQL database software on all our servers from version 4.1.11 to version 5.0.32 (plus appropriate security updates). MySQL 5 adds many features that customers have requested, and some Web site scripts now require it.
The upgrade will take place between 11:00 PM and 11:59 PM Pacific time (the times will be slightly different for each server). We’ll be making a full backup of all databases on each server before the upgrade, and as a result, customers should expect MySQL to be unavailable for about 15 minutes during this period. In addition, large databases may be slow for several minutes after the upgrade, because MySQL automatically converts databases to the new version format the first time they are accessed, which can be time consuming.
If your site doesn’t use MySQL databases, it won’t be affected at all. If it does, you almost certainly won’t see any effects other than the 15 minute outage. That said, we do recommend checking your scripts for MySQL 5 compatibility.
We have installed Midnight Commander on all of our servers. Midnight Commander is a file manager program which runs in a shell window and lets you manage the files on your Web site. Midnight Commander splits the screen in two, letting you select different directories on each side. You can then move, copy, and rename files and directories, and perform many other operations.
Midnight Commander is designed for users who connect to the shell but may not be fully comfortable with typing commands on the command line.
We’ve installed several security updates recently. We’ve updated PHP 4, PHP 5, the ClamAV antivirus scanner, and some XFree86 libraries. In addition, we’ve updated our own blog to use WordPress 2.2 — if you use WordPress, make sure you’ve done the same.
We’ve updated the default version of Ruby on Rails on our servers to version 1.2.3.
A couple of times in the last week, we’ve seen one of our MySQL database servers have an unusually high number of connections. That’s a serious issue: If there are too many connections to a MySQL server, customer scripts won’t be able to connect to a database, so we’ve spent some time looking at the cause and fixing it.
Some of the posts on our blog mention specific servers. You’ll occasionally see things like “The web14 server will be rebooted at 11 PM”, “mail sent from the web01 server was delayed”, or “more memory has been added to the web10 server”. Your question, quite naturally, is “How do I know if they’re talking about the server that has my account?”
We’ve updated PHP 5 on our servers to cover sixteen recently identified security issues. This only affects customers who have chosen to use PHP 5 — but since this upgrade only fixes security bugs, even those customers shouldn’t notice any changes.
The following stable PEAR packages were updated on our hosting servers today:
The full list of PEAR modules we have available (and more details about PEAR) is on this page.
We’ve updated PHP 4 on our servers to cover six recently identified security issues. Users shouldn’t notice any changes.
An upgrade for PHP 5 is also in progress. After testing, we actually rolled out the update onto our servers for a short time, until a customer reported an unusual problem with vBulletin posts getting cut off when they contain an odd number of apostrophes shortly afterward. This problem appears to be related to the update, so we have rolled back to the previous version of PHP 5 while we investigate this. (This kind of thing is very rare: this is the first security update in over year that has caused a problem. We have a suite of “regression tests” that we use to test PHP upgrades, and there wasn’t a general problem with it. We’ll follow up with more details when we know more.)
By the way, if you’re unfamiliar with what we mean by a “security update”, this page will help.
