Hi, guys.
Colohouse, our web host, substantially underestimated the size of MFO when they configured the new server onto which we were being copied. Part way through the transfer, they got a "holy mackeroley" alarm from the software, notifying them that they had run out of room (ummm ... we've had lots to say over the years? And Ted!) and the transfer was being terminated.
Their next try at making a duplicate of the site will occur after 10:00 CST tonight. And disruption should be, they swear, minimal.
Just thought you'd like to know!
Comments
Not a great beginning for Colohouse.
David, Thank you.
Cry 'God for MFO and Snowball !'
Looks good from DC @ 0900 this Monday.
As far as we can tell, the MySQL software we use (v 5.5) is so old that it crashes things every time it's touched. And, for reasons yet unexplained, our web host did not learn from Crash #1 or near-Crash #2 (hi, Crash!) and so didn't look to see if the site was back and live after last night's adventure.
Thanks to all who reached out, and to the many good folks who waited more-or-less patiently for us.
With luck, nothing happens now until after Eric updates all of the software on the offline version of the site and we hit the switch to redirect incoming traffic from the server with the old version of the site to the server with the new.
And really, what could possibly go wrong?
One problem now that I have already mentioned is that the "Account Suspended..." message page NEVER refreshes to become live. It's a dead-end page, and MFO status has to be checked via direct links to MFO to find if it's back,
https://www.mutualfundobserver.com/
https://www.mutualfundobserver.com/discuss/discussions
Here, hold my beer