dw_maintenance | static file hiccup details

Hi all,

We are currently working around a problem with our static file serving -- i.e., JavaScript, CSS, and image files. I had to move these back to our main web frontend instead of using the fast static frontend.

The root cause is that our hosting provider, ServerBeach, reassigned the IP address we were using for static content. They assigned it to one fo the new machines they are building for us. Given the vagaries of networks, I can't unassign that IP easily on my end. I have to kill the machine and it's still in provisioning, so I don't have access to it yet.

In order to work around this problem, I've had to make two changes -- use the main Perlbal infrastructure and turn off an optimization we use -- this is going to cause things to load a little slower. I will be working this evening to resolve the problem in a more efficient way.

My apologies for the issue here. I don't know why they reassigned our IP address, but as soon as I figure out what happened, I will let you know.

Thanks for your patience.

Flat | Top-Level Comments Only | Expand All

Thanks for the update!

Thanks for keeping everyone informed! 8D

♥

Thanks for the update and the timely response to the problems. You guys are appreciated.

(deleted comment)

is she packing any nitro-9???

(no subject)

wytchcroft - 2012-02-09 14:35 (UTC) - Expand

usedreturn - 2012-02-09 21:27 (UTC) - Expand

Thanks for letting us know -- I hope you get it figured out quick.

I had some trouble with my post page suddenly not displaying formatting, and some other formatting bits on the main pages were borked as well, but it cleared itself up within about five minutes.

That's all related! Any of the site formatting/layout, any of the JavaScript, and any images were affected by the core problem (which is why the posting page didn't have any formatting, and things like the RTE, tag autocomplete, icon switching, etc weren't working). Those things are loading again now, but the steps Mark had to take to get them working again means that the whole site will be slooooooooowwww for a bit, since those files are no longer being served by the very lightweight frontend we use to serve static (unchanging) content but are instead being served by the same webservers that build the dynamic pages -- loading things from there takes longer.

Mark and Robby are doing their best to get the static webserver talking to the internet again so we can go back to using that instead of having to use the dynamic webservers!

kore - 2012-02-09 03:57 (UTC) - Expand

figures. i figured you'd get it figured. go figure! :))

ach, you know you rule already - good luck with the gremlins!

Thank you for being so quick! It was literally like 20 minutes between realizing there was a disturbance in the Force and then it was better. Such a nice change from Livejournal. ;)

Thank you for the update!

Thank you for your hard work :)

Also, thank you for updating us so quickly and fully! I wondered what the problem was, refreshed my reading list, and there was your post. That is really great.

Thanks for the update, Mark! It's excellent to actually know what in the world is going on.

!!! Icon love!

alchemistseraph - 2012-02-09 04:27 (UTC) - Expand

celestinenox - 2012-02-09 12:25 (UTC) - Expand

psyco_chick32 - 2012-02-09 06:33 (UTC) - Expand

alchemistseraph - 2012-02-09 06:37 (UTC) - Expand

psyco_chick32 - 2012-02-09 06:38 (UTC) - Expand

alchemistseraph - 2012-02-09 06:48 (UTC) - Expand

psyco_chick32 - 2012-02-09 06:53 (UTC) - Expand

denise - 2012-02-09 08:01 (UTC) - Expand

psyco_chick32 - 2012-02-09 08:09 (UTC) - Expand

When I came home from work tonight I noticed DW was loading slower than usual. Then, I saw your post about what was going on, why it was happening, and that you were doing the miraculous stuff you do to get DW back up and running as it should.

Even though I didn't understand half of the post, it's enough to know you're already on it :)

Thank you so much!

I had no idea what was going on, but between one post an another, most of the problems cleared up.

Plus, the site is loading much faster than one would expect with the load put on it right now.

Thanks to all of you for letting your members know exactly what's going on while it's happening, instead of hours or days later.

Thanks to all of you for letting your members know exactly what's going on while it's happening, instead of hours or days later.

Yes, exactly.

I'll tell ya. As soon as I saw something hinky was going on, I didn't fret or worry because I knew that

mark,

denise, or

fu or one of the other fantastic folks here at Dreamwidth would be letting us know within minutes. Thank you for being the kind of site owners/runners who keep us posted with fast and clear information. I never flail about DW problems because I know that y'all will tell us up front about them as quickly as you can, even if all you have to say at the moment is "we know, we're looking into it". <333333333 to all of you.

this x 10000!

Yay, update! Knowledge! Thank you!

Would email notifications be related to this? I have had several people on my comms say they haven't been getting notifs all day.

Nope -- I am not aware of any issues with notifications. There aren't any emails or notification jobs in the queues. If someone isn't getting emails, they're always welcome to open up a support request and we will investigate and try to help!

You are so on top of stuff. When I realized something was going wrong with the .css, you already had a note up on Twitter about it (which was wonderful because my computer had trouble reading characters on another site and I was suddenly worried that I was having some kind of weird crash; seeing that information was a huge relief). And I can't thank you enough for your transparency on the issue! I've had the misfortune of having not one but two of my past webhosters screw up a message board by running concurrent versions of it on two different IP addresses when they were moving from one server to another (resulting in appearing/disappearing posts and data loss) but never had one point browsers at an address before it went live. Yeesh! I hope it doesn't keep you up too late!

....oh, I'm not used to a site's Twitter status being updated like that! Hah. //goes to add DW Twitter

Thanks for letting us know and your hard work! ^^

Thanks!

Thank you for keeping us in the loop!

Thanks for the detailed update! Always sucks, knowing exactly what you need to do and not being able to do it. Alas.

Thank you for informing us!

Gee, it sure is nice that you guys tell us why the site is running so slow. You're convincing me more and more that I should have left LiveJournal ages ago!

:D Hope everything gets figured out, thanks!

Page 1 of 2