take 3?

So as you may or may not have noticed, the update previously advertised wound up getting partially reverted about a day after it was deployed.  After getting the full production load on it, we wound up crashing it several times again.  There’s just not much we can do to emulate real users using WinSCP to upload files from our load testing scripts. 🙁

We’ve gotten some new patches to the unionfs filesystem driver that attempt to fix some of the crashes we’ve been getting.  Unfortunately our only real way to test them is to throw it back into production and see what happens.  As such, over the next week or two, the domain name will be swapping back and forth between the old machine and the new one periodically as we test things.  If you were following the directions given in the previous announcement this shouldn’t affect you at all, but I thought it would be good to give people a heads-up.  Obviously this means today’s deadline for the old machine to remain available has been averted, and it’ll probably still be around for another week or two at least.

If you absolutely need to reach the old machine, it’s at  The new machine is at  The domain name could point at either one of them at any given time for the next week or two while we continue testing.  If possible it’d be great if you can continue to use and follow where the domain points so you can help with the testing.  But if you run into any problems, feel free to use just to guarantee the old way of access.

#build on is the place to ask if you have questions or have any issues.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.