denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
Denise ([staff profile] denise) wrote in [site community profile] dw_maintenance2016-12-01 12:14 pm

(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!
darlas_mom: (blinkingcursor)

[personal profile] darlas_mom 2016-12-02 11:01 am (UTC)(link)
Content search isn't working for me. :( I don't know about anyone else, but it's definitely something I've noticed trying to search for entries/comments in communities. everything comes back "found no result," even when I test it with random words that should pull up a trillion results.
kareila: (Default)

[personal profile] kareila 2016-12-02 02:09 pm (UTC)(link)
There is a search indexing backlog that we are having to rate-limit right now due to database load... I can't give you an estimate on when it might be caught up, but we are keeping an eye on it. Thanks!