Last modified: 2013-03-06 05:38:39 UTC
So, we had the following incident a few moments ago: An Apache on the fleet was misconfigured, with wrong permissions in at least /wmf-config/. Random bits hits for some CSS (e.g. for it.wp) ended up on this Apache, which returned a page full of CSS comments with DBConnectionError ('DB connection error: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) (localhost)' in /usr/local/apache/common-local/php-1.21wmf3/includes/db/Database.php:797), since no configuration, database or otherwise, was readable or defined. The problem is that this CSS full of exceptions and no actual content was returned with a 200 status code and subsequently cached in Squid and Varnish. Fortunately the TTL for those is short, and the site recovered quickly. Could you please adjust it so that 500s are raised on such cases?
*** This bug has been marked as a duplicate of bug 33917 ***