dw_maintenance | (no subject)

We have now cut over to our new hardware! If you can see this, the site should be working for you.

Things you don't need to tell us about:

* The site may look a little weird or naked for a while as your computer/network/ISP/etc catches up with the switch.
* Comment notification emails should be going out properly, but inbound email (post-by-email and comment-by-email) may be delayed for a bit while your outgoing mail server catches up with the switch.
* The site search database is a few days out of date (missing entries from the past two days) and will catch up over the next few days. Entries and comments posted since the site came back up will be added to the index when they're posted.

Known issues:

* Accessing the site will be slow for a while as the caches warm back up, and you may receive Gateway Timeout errors.
* Due to the occasional database connection problem due to high load and site slowness earlier, some comments did not generate emailed notifications and those notifications can't be re-sent. New comments made since we resolved the DB problems are generating email notifications, but slowly (due to the general database slowness).
* Logging in to other sites using your Dreamwidth OpenID is broken (& we'll fix it as soon as we can!)

Let us know if you see anything else weird!

Flat | Top-Level Comments Only

Yeah! I did some testing, and it was all of my E-Mails with a + mark in them, so my old RP journals before I used filters got the notification E-Mails fine, but anything that's like myemailaddress+filtersignifier@gmail.com are not sending. I figure you realized this, but I found it satisfying to do some troubleshooting of my own.

Actually, that's probably a coincidence (or a secondary symptom, not the primary symptom), but good pattern spotting. :)

yeah, I did another test and a friend got the plus-sign e-mails fine, so.

GOOD LUCK FIXING IT and thanks for all the hard work.

basically the issue is that you all flocked back to the site the minute we hit the button, so between the caches needing to fill back up and everybody coming to test things, the db keeps hitting max connections. :)