Posted by Ackis Jan 29, 2009 at 15:59 UTC
There were many e-mails sent out regarding projects which were marked as inactive.
These e-mails, in the format of:
We're sorry, your project, <Project Name> (http://wow.curseforge.com/projects/project-1234/), has been marked as inactive on CurseForge/WowAce.
Recently the site upgraded its project status component and as a result all projects which have been previously merged or deleted were marked as inactive again, causing the e-mail to be sent out. Your main projects have not been affected in any such way.
-Note from Kaelten: Yea guys, we apologize for the mixup. We've already patched the cronjob so that such a thing won't happen again. Also for those of you who have many projects that were marked as inactive last night sorry for the span :)
Posted by ckknight Jan 18, 2009 at 21:48 UTC
Hey all, we're planning on having a downtime on Monday, January 19, 2009. Planning on starting around 10 AM CST and it shouldn't last more than a few hours.
This will affect the repositories and the website, but not forums.
We're planning on migrating from MySQL to PostgreSQL, since we've had just far too many issues with InnoDB locking up the database making the entire site inaccessible for minutes at a time, and we can't afford to lose transactions and ACID compliance by switching to MyISAM. Here's hoping it fixes the problem.
Addendum: And we're all done. Very anti-climactic, if you ask me.
Posted by Kaelten Jan 13, 2009 at 17:20 UTC
Sorry for the brief outage.
The issue has been fixed, just click login in the top right as usual and the forums should log you in without issue.
Posted by ckknight Jan 12, 2009 at 21:33 UTC
We're doing some maintenance on the forums system, moving boxes around in the server room and all. We expect the downtime to last no more than a couple hours.
To pass the time, here's a kitty:
Posted by ckknight Jan 07, 2009 at 17:31 UTC
Hey beautiful people, we're gonna have another downtime today.
Hopefully this won't take too long, but it's always hard to gauge.
We're transferring the DB back to the real DB server, which has been upgraded to a newer OS as well as 64-bit, so we can finally use 8 GiB of RAM instead of just 2 GiB.
Addendum: And we're done and everything went smoothly.