Denise (
denise) wrote in
dw_maintenance2016-12-01 12:14 pm
![[staff profile]](https://www.dreamwidth.org/img/silk/identity/user_staff.png)
![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png)
(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!
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!
no subject
no subject
IT'S ALIVE
no subject
Thanks for all of your hard work.
no subject
no subject
no subject
no subject
"...good catch!" says
zorkian. Fixing now, thanks!
(no subject)
(no subject)
(no subject)
(no subject)
no subject
I did get the test comment in my DW inbox, however!
no subject
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
no subject
no subject
(no subject)
(no subject)
(no subject)
(no subject)
no subject
no subject
*leaves cookies out for the database*
no subject
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
no subject
no subject
no subject
no subject
no subject
When I reloaded the site, Donald Trump was President-Elect of the United States.
no subject
(no subject)
(no subject)
(no subject)
no subject
no subject
(no subject)
no subject
no subject
* If the person who commented got the "too many connections" error when they commented, the job for sending the email was unable to make it to the database and can't be re-sent: you won't get an email notification for that comment, sadly.
* We have another issue that we're looking into that may cause a small subset of notifications to fail, and we haven't fixed that yet. (It's the current thing people are working on.) I don't know for sure whether it will be possible to re-send those failed emails once we fix the problem, because we haven't pinpointed the exact problem yet. It's probably not very likely, though.
(no subject)
(no subject)
no subject
no subject
no subject
(no subject)
(no subject)
no subject
no subject
Usually it just puts the IP of the user up, but in a current thread I'm in, both myself and the party I'm tagging with have the IPs listed as 108.162.###.### via (actual IP). (the last two numbers are different for each of us, but the first two are the same). Is that something that will change or that needs to?
no subject
(no subject)
(no subject)
no subject
no subject
no subject
no subject
no subject
(no subject)
(no subject)