Some Residual Issues

September 13, 2005 on 12:19 pm | In Foobars, Updates by Dallas Kashuba |

As many of you have pointed out there are still some remaining residual issues following yesterday’s power outage. All of our servers are up and running and most websites are functioning normally. There are some remaining issues and we are actively addressing those as quickly as we can. Most of us worked late into the night last night and all of us will be working all day today to make sure everything is completely back to normal.

There is currently some network degradation within our data center that we are currently looking into. That is most likely accounting for slow response times you may be seeing on your websites. That will be fixed as soon as possible.

We will also be investigating the issues with our non-functioning backup generators and will take action as necessary.

19 Responses to “Some Residual Issues”

  1. Jack Says:
    September 13th, 2005 at 12:22 pm

    What is this?
    Site Temporarily Unavailable
    We apologize for the inconvenience. Please contact the webmaster/ tech support immediately to have them rectify this.
    error id: “bad_httpd_conf”

  2. hipocratico Says:
    September 13th, 2005 at 12:46 pm

    Hope everything´s back to normal, as soon as possible.

    You have been a great host service.

  3. Deamos Says:
    September 13th, 2005 at 12:48 pm

    I hope everything is back to normal soon.

    I’m having spotty success reaching my site or anything on the dreamhost network that I access on a regular basis.

    This explains why I couldn’t get my email yesterday afternoon though. :)

  4. Simon Jessey Says:
    September 13th, 2005 at 12:48 pm

    I thought it was already understood that you are not allowed food, drink, or sleep as long as a problem exists? We all demand free hosting on dedicated servers for ever and ever (or until California falls into the Pacific, whichever is sooner).

    Seriously though, you guys are doing an excellent job. Not only have you kept us fully informed as to what has been going on, but you’ve also worked like slaves to minimize the impact as much as possible. I’m impressed.

  5. Robert Says:
    September 13th, 2005 at 1:10 pm

    So that’s what it is.. the degradation… cuz I’m feeling it! Site is up but quite slow. Ah well, glad you guys are working on it! Found your blog just now, to be really helpful! Thanks!

    Is there an ETA on having everything back to normal??

  6. Bob Says:
    September 13th, 2005 at 1:42 pm

    [quote]What is this?
    Site Temporarily Unavailable
    We apologize for the inconvenience. Please contact the webmaster/ tech support immediately to have them rectify this.
    error id: “bad_httpd_conf”[/quote]

    Jack, try going to the webpanel and reconfiguring that domain you’re having problems with… that might give the thing a kick to make it start working!! (I’ve done that before when recieving that error message).

    My sites are up and running, but they are going a bit slow!

  7. Wardoggie Says:
    September 13th, 2005 at 1:59 pm

    Glad this blog was here to keep us informed. I thought it might have been some kind of DDoS attack or something like that, but when my email was down and http://www.dreamhost.com was offline for a couple of hours, I knew it had to be something worse. Then I got word of the LA blackout and figured it was something related to that. Good work getting things going again!

    Wardoggie

  8. Jack Says:
    September 13th, 2005 at 2:18 pm

    For those who care, it seems like slowness/latency issues has more to do with Dreamhost’s uplink providers–such as Level3.net–than Dreamhost themselves.

    if you note the ping times from my Brooklyn, NY abode to my Dreamhost hosted site–picpatrol.com–you’ll notice that ping times triple when hitting ‘losangeles1.level3.net’.

    –BEGIN–
    traceroute to picpatrol.com (66.33.193.138), 64 hops max, 40 byte packets
    1 pool-68-161-100-104.ny325.east.verizon.net (68.161.100.104) 48.270 ms 1.185 ms 1.075 ms
    2 10.32.97.1 (10.32.97.1) 23.998 ms 24.341 ms 24.511 ms
    3 130.81.10.21 (130.81.10.21) 24.770 ms 24.749 ms 25.493 ms
    4 so-6-0-0-0.bb-rtr2.ny325.verizon-gni.net (130.81.18.90) 25.299 ms 27.291 ms 25.388 ms
    5 so-7-0-0-0.peer-rtr1.ny111.verizon-gni.net (130.81.17.131) 25.346 ms 24.636 ms 26.924 ms
    6 so-1-0-0-0.gar2.newyork1.level3.net (4.78.174.13) 25.393 ms 25.269 ms 26.931 ms
    7 ae-1-56.bbr2.newyork1.level3.net (4.68.97.161) 24.985 ms ae-1-52.bbr2.newyork1.level3.net (4.68.97.33) 24.240 ms 25.767 ms
    8 ae-0-0.bbr2.losangeles1.level3.net (64.159.1.126) 92.765 ms as-0-0.bbr1.losangeles1.level3.net (64.159.1.157) 92.626 ms ae-0-0.bbr2.losangeles1.level3.net (64.159.1.126) 93.617 ms
    9 ae-11-51.car1.losangeles1.level3.net (4.68.102.12) 92.648 ms ae-11-55.car1.losangeles1.level3.net (4.68.102.140) 92.676 ms ae-21-54.car1.losangeles1.level3.net (4.68.102.108) 91.992 ms
    10 ge1-l3.dreamhost.com (4.78.192.66) 139.544 ms 127.492 ms 131.437 ms
    11 basic-igloo.van.dreamhost.com (66.33.193.138) 115.009 ms 111.410 ms 132.703 ms
    –END–

  9. sean Says:
    September 13th, 2005 at 2:46 pm

    Anyone else having issues with SMTP? I’ve been able to receive emails, but have not been able to send since the outage. And the server keeps asking me for a password when sending an email even after the proper password has been entered.

  10. Anonymous Says:
    September 13th, 2005 at 3:12 pm

    The bad_httpd_conf error is an error message generated by an error in the Apache (web server) configuration file for that domain.

    The suggestion to make a change to the domain is a good one because it might take some time for the DH guys to make a change with everything else that is going on.

    I usually get this error when I add a domain and forget to create the directory the website files are going to be placed in. (This will generate an apache error).

    In case some data had to be restored from backup (and might not have been done successfully) I’d log in with ssh or ftp and make sure that the directories and files are all there.

  11. Dave Hodgkinson Says:
    September 13th, 2005 at 4:14 pm

    I thought web hosting was easy?

  12. Dave Says:
    September 13th, 2005 at 4:39 pm

    Hope you get everything sorted asap.. my sites up though :D

  13. SW Says:
    September 13th, 2005 at 4:53 pm

    Thanks for the improved explanation - the link to Media Temple provides some further details. Looks like you are reliant on the building backup power and someone outside of DreamHost screwed up that for you (and everyone in the building).

  14. Mike Piontek Says:
    September 15th, 2005 at 1:08 am

    The previous comment got me curious, and I couldn’t find the Media Temple link that was referred to. I was able to find some information on their site though.

  15. Dim Says:
    December 23rd, 2005 at 1:52 am

    I hope everything is back to normal soon.

    I’m having spotty success reaching my site or anything on the dreamhost network that I access on a regular basis.

    This explains why I couldn’t get my email yesterday afternoon though

  16. Saha Says:
    December 25th, 2005 at 2:02 am

    Seriously though, you guys are doing an excellent job. Not only have you kept us fully informed as to what has been going on, but you’ve also worked like slaves to minimize the impact as much as possible. I’m impressed

  17. Saha Says:
    December 28th, 2005 at 7:05 am

    Seriously though, you guys are doing an excellent job. Not only have you kept us fully informed as to what has been going on, but you’ve also worked like slaves to minimize the impact as much as possible. I’m impressed.

  18. Denn Says:
    December 28th, 2005 at 7:25 am

    usually get this error when I add a domain and forget to create the directory the website files are going to be placed in. (This will generate an apache error).

    In case some data had to be restored from backup (and might not have been done successfully) I’d log in with ssh or ftp and make sure that the directories and files are all there.

  19. Anonymous Says:
    January 19th, 2006 at 1:06 pm

    Site Temporarily Unavailable
    We apologize for the inconvenience. Please contact the webmaster/ tech support immediately to have them rectify this.

    error id: “bad_httpd_conf”

    i login the web control panel and i saw a msg is that “This account is currently disabled!” . i tried to send a ticket about this issue to the technical support team but i didn’t get any reply from them.

    dreamhost service is worst of the worst. no phone supporting, no live chat supporting. what we can do is waiting for their email. wtf

Leave a Reply

Powered by WordPress. Pool theme by Borja Fernandez, modified by DreamHost.
Entries and comments feeds. ^Top^