Upgrading to PHP 5.3
As described in a previous blog post, we’re removing the obsolete PHP version 5.2 from our servers. Our customers should only be using the newer PHP 5.3 series.
As described in a previous blog post, we’re removing the obsolete PHP version 5.2 from our servers. Our customers should only be using the newer PHP 5.3 series.
The PHP developers have announced the release of version 5.3.17 that fixes several bugs.
We’ve upgraded PHP 5.3.16 to PHP 5.3.17 on our servers as a result.
At 3:33 PM Pacific time September 12 2012, our “web04” server became unstable and needed to be restarted. This led to an 8 minute outage of Web sites and e-mail hosted on that server.
All services are now working normally, and other servers were not affected.
This isn’t normal or acceptable. We take server reliability seriously, and we’re investigating the underlying cause to avoid a recurrence of this problem.
WordPress 3.4.2 was released yesterday, and it contains important security updates to keep your site safe.
Our WordPress one-click installer automatically installs the latest version for new sites. If you’ve previously installed WordPress, you should upgrade it right away from within your WordPress Dashboard.
In fact, you should always update immediately when WordPress tells you there’s a new version available. Don’t let yourself get behind, because it gets more difficult to update smoothly if you’re several versions out-of-date.
Our business offices will be closed on Monday, September 3 to observe the US Labor Day legal holiday. As always, we’ll provide same-day support for time-sensitive issues via our ticket and e-mail systems. However, questions that aren’t time-sensitive (including most billing matters) may not be answered until Tuesday, and telephone support (via callbacks) will be available only for urgent issues.
This post was updated November 30, 2012 to reflect the additional availability of PHP 5.2.17.
We currently offer PHP versions 5.2.6, 5.2.17, and the 5.3 series. You can choose which version your account uses in the “PHP Settings” section of our “My Account” control panel.
PHP 5.2 has been obsolete for many years. Because of that, we’re beginning the process of removing PHP 5.2.6 from our servers and encouraging customers to switch to PHP 5.3. (PHP 5.2.17 is still available for now, but discouraged.)
Shortly after we made PHP 5.3.15 available to hosting customers, the PHP team announced the release of version 5.3.16 that fixes several bugs.
We’ve upgraded PHP 5.3.15 to PHP 5.3.16 on our servers as a result.
PHP 5.3.15 is now available on all hosting accounts. It’s the default for new customers, and existing customers can update their PHP version using the “PHP Settings” link in our “My Account” control panel.
If you’re an existing customer using an older version of PHP, we haven’t yet changed your PHP version. However, we will begin doing that in about 30 days (we’ll announce that separately), so we recommend that you upgrade now. That way, if you find you’re using an outdated PHP script that isn’t compatible, you can set PHP back to the previous version and work to update the script. The old PHP 5.2 series will be removed from our servers by the end of 2012.
We’re occasionally contacted by customers who report that mail isn’t arriving (when we can see that it is), or that their Web site is down (when we can see that it isn’t)…. and the mystery is eventually solved by the customer saying “Oh! Never mind. I own something.org [or something.net, or something.biz, etc.], but the person who had the problem was typing something.com”. Sometimes people even make this mistake with their own domain name.
As far as most people are concerned, “.com” means “the Internet” (and vice-versa). You can tell people “something.biz” till you’re blue in the face, but they’ll still often remember it as “something.com”. That’s a real problem if you own one but not the other.
At 12:50 AM Pacific time, the web08 server experienced extremely high disk load and needed to be restarted as a result, resulting in approximately 5 minutes downtime for sites on that server. Other servers were not affected, and the server is now working normally.