万恶的DreamHost,万恶的bad_httpd_conf

经过2月26日的断电劫难后,我们的数据被移到welchs上,可怜的welchs,经常重启,而且cpu占有相当高,还导致我们有多个域名down掉,呈bad_httpd_conf状,一天后竟然连ping都ping不通。尝试n多种修复方法后还是不行,最后没办法了,只好联系客服要求更换服务器,全文如下:

Message from you (Mar 2nd, 2007 – 01:27:05 / #1755252)
Subject: SAVE US! People are DYING! Downed sites:
gailou.com
heyamigo.cn
lovebaby.biz
wikiwind.net

Downed users: our420/suwarm/gailou
Panding WebID: our420

uptime: 00:18:34 up 20:34, 5 users, load average:
49.29, 57.98, 52.72 (VERY LOW UPTIME!)

Our old server “coffee” is more steady than our
current server “welchs”. The current server is very
UNSTEADY!,it often restarts,please move our data to
another server.

幸运的是DreamHost的客服反应够快,很快就给了我答复,说是答应我的要求,把我们搬到名叫“monster”的新服务器上,他的介绍说是“This
is a newer server with very good stability and very low load.”果然这台服务器性能相当不赖。附全文:

Reply from DreamHost (Mar 2nd, 2007 – 04:31:47 / #10533451)
Subject: Re: SAVE US! People are DYING! Hello Wang,

So sorry for the downtime! I’ve moved you from welchs to monster. This
is a newer server with very good stability and very low load. Keep in
mind, this move may take from 24-48 hours to take effect. Please let me
know if you have any other questions!

Thanks!
Jeffrey

今天搬过来以后,发现所有域名都可以连得上了,而且速度还不错,但bad_httpd_conf的情况还是没有改善,于是在写这篇blog的前再给客服发了封mail,希望到了明天大家的网站都可以正常访问啦!

PS:新的服务器的名字真的很geek哦~!
叫怪物哦~这难道是DreamHost的自嘲?呵呵!
附个monster的uptime:
00:32:48 up 4 days,  5:57,  4 users,  load average: 0.09, 0.18, 0.20
Update:前天给客服再发了个Mail,昨天他给我了个答复,看来原来绑定A记录的都换成新的A记录或者绑定他们的NS记录。

Ah, since you’re not using our nameservers you’ll need to manually update
where your custom nameservers are pointing to. After the moves, your
sites are at different IP addresses, but the nameservers are still
pointing at the old machines. 😉 Basically it’ll be way easier if you
switch over to our nameservers for your domains. That way if there’s
ever an IP address change in the future we’ll take care of it
automatically. Otherwise you’ll need to go to the Domains > Manage
Domains section of your panel at
https://panel.dreamhost.com/index.cgi?tree=domain.manage& and then click
the “DNS” link for the domain. Then just make sure that the A records
match up between that page and what you’ve got setup at your nameservers.
You’ll need to contact your registrar or DNS service to take care of
that end of things.
If there’s anything else I can help you with, just let me know!

Thanks!
Craig

Share Your Thought