Auschan Back Online-sort of

OK the site is back up but some files are still transferring and entire boards are still missiong. Please be patient.

Basically what has happened is Dreamhost have found a cp image on the server and disabled auschan. I can't find an infringing file and they still haven't let me know exactly which file is the culprit but they must have found something. Anyway we are on a new server and over the next 12-24 hours things will continue to return to normal.

Auschan Major Outage

Auschan is suffering a major outage and will be down for an extended period. Stay tuned for updates.

SQL server being moved to new hardware

The hard drive in Auschans db server has shit itself causing the can't connect to MySQL server error when you try to load a page. It is being restored from backup so the site will hopefully come back up soon.

UPDATE: After an extended outage it looks like the site is finally running smoothly again.

Auschan issues resolved

It turns out the previous database rebuild did not go smoothly after all leaving it broken into two pieces. A bunch of tables were missing including the entire ban list. Luckily I was able to access the old database through an old username, back it up and merge it onto the new partially built DB and everything is finally running smoothly again.

Publish Post

Database server down

Auschan's database server has been flakey over the last few days and is completely down at the moment. The cause of the outage is currently unknown and is being looked into.

UPDATE:  Auschans database has been rebuilt and the site is back up and running normally. If you encounter any problems or errors please let us know admin@auschan.org.

Auschan slow

Auschan may be slow or completely down while the site is migrated to a new server. The move should be completed withing 30 minutes.

Thankyou for your patience during this time.

Failed to write to disk error RESOLVED

Outstanding customer service as always from Dreamhost...

Sorry about that! It looks like the /tmp partition filled up on the server. We've fixed that now, so your site shouldn't be displaying that error any longer.