Mark Smith (
mark) wrote in
dw_maintenance2012-02-08 07:16 pm
![[staff profile]](https://www.dreamwidth.org/img/silk/identity/user_staff.png)
![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png)
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.
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.
no subject
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!
no subject
The site is also much less slow than I was expecting it to me. And since I know what's actually going on (to the best of my limited understanding!), I feel a lot better. I just wanted to let you guys know it really counts.