13Aug

Partial Network Outage


This morning between the hours of 7:35 AM and 9:45 AM, Mr.Host experienced a partial network outage.

One of the four network interfaces on the main NAS (Network Attached Storage) device failed, causing some servers to lose access to the web and e-mail disk storage.

This would have affected access to your website and e-mail. Any e-mail received during this period would have been queued on the Mr.Host E-mail Cluster, and delivered once the issue was resolved- no e-mail was lost during this outage.

The network interface was replaced with a spare, and service was completely restored at 9:45 AM.

We apologize for any inconvenience this may have caused.

If you have any questions or concerns about this outage, please let us know.

26Jul

PHP 5.3.3 Upgrade


This evening all Mr.Host web servers have been upgraded to PHP 5.3.3

Backwards incompatible change:

  • Methods with the same name as the last element of a namespaced class name will no longer be treated as constructor. This change doesn’t affect non-namespaced classes.
<?php

namespace Foo;

class Bar {
    public function Bar() {

        // treated as constructor in PHP 5.3.0-5.3.2
        // treated as regular method in PHP 5.3.3
    }
}

?>

There is no impact on migration from 5.2.x because namespaces were only introduced in PHP 5.3.

Security Enhancements and Fixes in PHP 5.3.3:

  • Rewrote var_export() to use smart_str rather than output buffering, prevents data disclosure if a fatal error occurs (CVE-2010-2531).
  • Fixed a possible resource destruction issues in shm_put_var().
  • Fixed a possible information leak because of interruption of XOR operator.
  • Fixed a possible memory corruption because of unexpected call-time pass by refernce and following memory clobbering through callbacks.
  • Fixed a possible memory corruption in ArrayObject::uasort().
  • Fixed a possible memory corruption in parse_str().
  • Fixed a possible memory corruption in pack().
  • Fixed a possible memory corruption in substr_replace().
  • Fixed a possible memory corruption in addcslashes().
  • Fixed a possible stack exhaustion inside fnmatch().
  • Fixed a possible dechunking filter buffer overflow.
  • Fixed a possible arbitrary memory access inside sqlite extension.
  • Fixed string format validation inside phar extension.
  • Fixed handling of session variable serialization on certain prefix characters.
  • Fixed a NULL pointer dereference when processing invalid XML-RPC requests (Fixes CVE-2010-0397, bug #51288).
  • Fixed SplObjectStorage unserialization problems (CVE-2010-2225).
  • Fixed possible buffer overflows in mysqlnd_list_fields, mysqlnd_change_user.
  • Fixed possible buffer overflows when handling error packets in mysqlnd.

Key enhancements in PHP 5.3.3 include:

  • Upgraded bundled sqlite to version 3.6.23.1.
  • Upgraded bundled PCRE to version 8.02.
  • Added FastCGI Process Manager (FPM) SAPI.
  • Added stream filter support to mcrypt extension.
  • Added full_special_chars filter to ext/filter.
  • Fixed a possible crash because of recursive GC invocation.
  • Fixed bug #52238 (Crash when an Exception occured in iterator_to_array).
  • Fixed bug #52041 (Memory leak when writing on uninitialized variable returned from function).
  • Fixed bug #52060 (Memory leak when passing a closure to method_exists()).
  • Fixed bug #52001 (Memory allocation problems after using variable variables).
  • Fixed bug #51723 (Content-length header is limited to 32bit integer with Apache2 on Windows).
  • Fixed bug #48930 (__COMPILER_HALT_OFFSET__ incorrect in PHP >= 5.3).

For users upgrading from PHP 5.2 there is a migration guide available on http://php.net/migration53, detailing the changes between those releases and PHP 5.3.

For a full list of changes in PHP 5.3.3, see the ChangeLog.

21Oct

Partial Mail / Web outage


We experienced a server failure at around 9:15am EST this morning, that affected a small number of hosting customers. The issue was resolved around 10am EST, but some customers may have noticed degraded performance when accessing their e-mail.

As of 3pm EST, all services are fully functional on this system.

There will be additional emergency maintenance performed on this system later tonight at 3am EST, to completely rectify the problem.

If you have any questions or concerns, please let us know.

03Oct

Email Migrations – Complete!


The e-mail migration to the new mail system is complete.

It took a little longer than we had expected, but so far we haven’t had any issues related to this mail transition; hopefully you didn’t even notice the change.

The new mail system allows you to use up to 50 GB of storage (depending on your web hosting package) for your e-mail, so you’ll never have to worry about running out of space!

If you have any questions or concerns about this migration, please let us know.

FYI – For those of you that are interested, we migrated ~500 GB of e-mail, and close to 1 billion messages to the new system.

21Sep

Email Migrations


Over the next few days, Mr.Host will be migrating all the customer e-mail from the current mail system, to our new mail hosting platform. Due to the sheer number of mailboxes, and amount of e-mail, we’re opting to not do the migration all at once, but to spread the copy out over several days, copying only a handful of e-mail accounts at a time.

What this means to you, is a shorter disruption in your service, only as your mailbox is copied; the length of the disruption will be directly proportional to the size of your mailbox- if you use POP3 to check your e-mail, and you don’t leave messages on the server, you likely won’t even notice the transition.

There are no changes that need to be done by you to support this new system, nor will any mail be lost during the transition. New mail will continue to be delivered as it comes in.

Why is this good?

Once on the new system, your e-mail quota for all your mailboxes, will share the space allocated to your web hosting account.

So, for example, if you have a Bronze Hosting package, which includes 10GB of storage, and you’re only using 1GB for your website, you’ll have 9GB (9,000MB) of space for e-mail. This is a huge jump from the current system which only allowed 20MB of space per mailbox.

Impact of this migration:

During and after the migration, you will see a new “mail” folder when you FTP into your web space- this is where your e-mail is stored- DO NOT delete this folder, if you do, it will delete your mailbox, and all your e-mail.

After the migration, you may notice some of your e-mail folders now have a number at the end of them, for example “sent-mail0” or “sent-mail1”. This is because there were multiple folders with the same name; the migration process renames these folders so they don’t conflict, to support the new system. All the e-mail in these folders is preserved, and can be copied out at your discretion.

If you have any questions or concerns about this migration, please let us know.