Is is only me, or has Typophile been down all weekend?
This error message was shown on the homepage:
Warning: mysql_connect(): Can't connect to local MySQL server through socket '/tmp/mysql.sock2' (2) in /home/httpd/vhosts/typophile.com/httpdocs/cms/includes/database.mysql.inc on line 31
Can't connect to local MySQL server through socket '/tmp/mysql.sock2' (2)
Here's an update for anyone interested in the gory details. First of all, apologies for the recent outages.
In order to enable a database cache, we upgraded MySQL to version 4.1x. At the same time, we added an autostart script. What I neglected to do was to name the said script starting with a capital S (RedHat likes it that way).
In the mean time, our server is being relocated to a really sweet data center, so for the last few weekends the nice folks at Media Temple have restarted the server a couple of times. Since the startup script was failing, MySQL didn't come back online with the rest of the server like it's supposed to. The problem has been fixed, and hopefully we won't have any more sad Typophile-less weekends.
The disk space issue has been solved and isn't an issue.
As everyone knows forum software is free and super-reliable, and you can't blame the typophile farm of Mac OS servers, Xboxes and iPods that host the site as they boast 99.99999999% uptime. It must be the complex "Hrant-Bot" software that causes the problems. Some may recall the time when it was disabled for a few months, and during that time no-one visited Typophile! But during that time there were no outages. You people can’t have it both ways.
Captured from web.archive.org on 9 Jul 2011. view this capture