这两天又得到汇报说我的站江西电信访问特别慢，我也发现了，13号下午去市区腐败，晚上在市区包夜，那个网吧下载能达到2M/S，结果上我的网站巨慢，我彻底无语了，回寝室后，网通一切正常。上次就是因为这个电信访问奇慢的原因，我把站从Dreamhost搬到Bluehost上，没有想到这才半年不到，又出现这个问题了。现在极度怀疑是江西电信动了手脚（上次也有怀疑），但是不明白他们为什么这么做，怎么做到的。哎…你说咱是个小站长，做个小站，没人气就算了，技术不好，咱可以慢慢学，慢慢发展，可是还要被IDC、ISP整，漫漫前路，我都看不到做网站前途在哪里了…前两天，团委的老大忽然找我说要把他的那个站从我空间上搬出来，搬回国内，说什么“不利于国家监管”。我这边还没有动手呢，那边电信线路的同志就开始嗷嗷叫网站慢如龟爬了。结合这个迹象我真的怀疑是不是学校在联合电信在整我（学校的论坛我做的）。本来这个寒假没有什么事情的，想安安生生的过个寒假…今天又在满哪找空间了… …自己都觉得折腾的累。

亲爱的朋友们，如果你看过了本文，又不是很忙的话，请你留言给我，给我推荐一个不错的物美价廉的IDC。谢谢了，谢谢了。

相关日志

• 终于回来了，最近真是背的可以… (4)
• 网站…网站…网站… (0)
• 来自Dreamhost关于服务器集群“blingy” (0)
• 期末考试到，复习，稍后回来 (41)
• 手记 (0)

域名在到期前2个月和续费后两个月不能转出新网

你说我怎么这么背？我彻底无语，因为主机把我累坏了，我也不争了，也不去查验一下这个“传说中的新规则”了，放那里吧，反正也没有什么影响。我在Dreamhost的两个域名前13号刚续费，昨天就把他们成功转出到Godaddy，而且速度惊人。早就听人说，从中国的域名商手中把域名转出来难死，这次真是的感受到了，连新网都可以制定“规则”了。域名代理商我当初还特地找了我河南老家的，看来就算自己人也没有用啊，还河南老乡呢！我好几个域都在你那里，等过了那”传说中的新规则“限制的时间，我就一起把它们全转出来！
昨天晚上Godaddy申请转入域名、付的钱，今天中午就收到了Dreamhost的邮件（其实是早上8点半到的），让我确认转出，我去Dreamhost确认了下，马上收到Godaddy的邮件说我的域名已经成功转入，DNS解析马上OK了。速度真是快，我以为还要等几天呢。不过到现在还没有办法使用新的解析… …理论值是24小时内，不过一般都是几个小时就OK，这次转DNS是我感觉最慢的一次了，不知道这个是不是也算背。

就刚才9点多，家乡一个MM发来短信关心了我一下，我感动的痛苦流涕，马上去交花费（本来想多停机几天，谁都别想通过手机找不到我），到江西移动的官网上准备网上付款，碰上了江西移动的脑残设计，交花费，必须登陆，我登陆我的号码，但是因为停机我的帐户的所有功能被锁死，然后我去网付，提示我重新登陆，我重新登陆又跳回到锁死界面，然后我网付，继续提示我重新登陆… ….死循环。崩溃！不知道多少同志网付话费被郁闷死，停机了来网付，结果碰上这个脑残的设计。没有办法只能去淘宝找快冲，找了个皇冠店家，看到他在，马上付款，然后询问他在不在，他说在，然后下一秒旺旺提示我，店家改用手机登陆（就是下线）。OMG，我晕！我就这么背，结果就在11点左右他终于上了，给我冲了。快冲成了慢充。我马上给MM回电话，人家已经关机了… …

不如意啊，生活不如意啊… …不如意也就算了，走背字就更加让人郁闷了…. …祈求上帝，玉皇大帝，如来佛祖快点让我转运吧，不然我真的扛不住了，都被折磨到身心俱疲，无言以对了，连骂的力气都没有了… ….那个兄弟姐妹要是有空，过几天来找我聊聊（社团招新又要忙几天），我憋屈坏了… …
刚看到了个兄弟最近比我还背，心里舒坦点了，请大家理解我的这种BT心态，人在这种情况下都在心里对比下，要不稍微舒坦一些，要不更郁闷… …不理解的同志直接BS我，然后对显示屏竖起中指。
难得写这么多字，我改了一个不知道哪个牛人的名言来形容现在的自己：

不在崩溃中爆发，就在爆发中崩溃！

相关日志

• 网站…网站…网站… (0)
• 窝火 … … (0)
• 永远在路上,永远的Beta… (0)
• 无可救药的胖子 (3)
• 拼命是为了什么 (0)

# Rewrite 系统规则请勿修改
RewriteRule ^archiver/([a-z0-9\-]+\.html)$ archiver/index.php?$1
RewriteRule ^forum-([0-9]+)-([0-9]+)\.html$ forumdisplay.php?fid=$1&page=$2
RewriteRule ^thread-([0-9]+)-([0-9]+)-([0-9]+)\.html$ viewthread.php?tid=$1&extra=page\%3D$3&page=$2
RewriteRule ^profile-(username|uid)-(.+)\.html$ viewpro.php?$1=$2
RewriteRule ^space-(username|uid)-(.+)\.html$ space.php?$1=$2
RewriteRule ^tag-(.+)\.html$ tag.php?name=$1

由于windows下不支持.htaccess文件，因此将上面的代码保存为一个文本文件，将这个文本文件传到DH的空间后改名为.htaccess，然后在后台管理中的“基本设置-搜索引擎优化”中选择“URL 静态化”的相应的值，即可实现在dreamhost空间中的discuz的伪静态化。
伪静态化后的样例可访问：http://bbs.jxcia.net
(增加了tag.php对应的rewrite规则 2007-8-23)
我把写好的.htaccess文件给大家，大家直接上传到论坛的根目录就可以了！
htaccess.zip (370 Bytes)

htaccess.zip (370 Bytes)
下载次数: 262

2008-4-20 15:53

^_^  希望这个教程对大家有帮助！
P.S.:我DH主机上的DZ论坛已经顺利升级为6.1.0，没有任何问题！(升级为测试版的6.1.0，主要是为了主站升级做测试！）
内容主要信息转载自：http://www.lifangjin.com/archives/378

相关日志

• 网站…网站…网站… (0)
• 终于回来了，最近真是背的可以… (4)
• 来自Dreamhost关于服务器集群“blingy” (0)
• 手记 (0)
• 好消息：Discuz 7 正式版发布时间公布！ (8)

2.在你空间放置(就是你的domain.com目录下)目录建立cgi-bin文件夹
用SSH登陆后直接输入命令:

mkdir ~/[your website directory]/cgi-bin/

PS:[your website directory] 即 你的domain.com文件夹名字或者你自定义的文件夹名字!
3.建立 php-update.sh 文件(现在SSH还是在根目录)
建立php-update.sh

vim php-update.sh

写入内容按下”i”键插入.
此时看你的php版本
php4

#!/bin/sh CGIFILE=”$HOME/[your website directory]/cgi-bin/php.cgi” INIFILE=”$HOME/[your website directory]/cgi-bin/php.ini” cp /dh/cgi-system/php.cgi “$CGIFILE” cp /etc/php/cgi/php.ini “$INIFILE” perl -p -i -e ‘ s/.*allow_url_fopen.*/allow_url_fopen = On/;
• ‘ “$INIFILE”

php5

#!/bin/sh CGIFILE=”$HOME/[your website directory]/cgi-bin/php.cgi” INIFILE=”$HOME/[your website directory]/cgi-bin/php.ini” cp /dh/cgi-system/php5.cgi “$CGIFILE” cp /etc/php5/cgi/php.ini “$INIFILE” perl -p -i -e ‘ s/.*allow_url_fopen.*/allow_url_fopen = On/;
• ‘ “$INIFILE”

把[your website directory] 改成你自己的.
此代码既是开启 fopen 如果你还想开启其他的自己编辑以上代码即可.
直接复制然后在putty里按右键就可以复制进去!然后按下键盘的’ESC’然后输入”:wq”,既可以退出.(不包括” “
4运行 php-update.sh

chmod +x php-update.sh
./php-update.sh

5.设置cron使系统每个礼拜检查php
在putty里键入

crontab -e
@weekly /home/myusername/php-update.sh

编辑保存按Ctrl+X退出.
myusername改成你自己的ftp用户名.
6.在网站目录下建立.htaccess,让php按照我们的设置来运行.
putty里键入

cd domain.com

转入网站目录下.
然后建立.htaccess文件

vim .htaccess

然后输入如下代码:

Options +ExecCGI AddHandler php-cgi .php
Action php-cgi /cgi-bin/php.cgi

按”ESC”后输入”:wq”既完成.(不包括” “
需要的同志拿去，希望对你们有所帮助！有什么问题可以回帖留言！
（教程资料来源网络）

相关日志

• 网站…网站…网站… (0)
• 终于回来了，最近真是背的可以… (4)
• 来自Dreamhost关于服务器集群“blingy” (0)
• 手记 (0)
• X Space 4.0 使用教程! (0)

进入后台后-> 点击Goodies->Htaccess/WebDAV链接-> 在右边选择你要进行防盗链设置的网站-> 点击[ Configure a new directory. ]-> 在网址后面的输入框里输入你要进行保护的文件夹的名字，下面有两种设置：
Password-protect this dir?即对文件夹设定密码，在此选项后打勾即可实现本功能。
Forbid linking to files in this dir?防止指定文件的某些类型的文件被其他网站盗链，在此选项后打勾即可实现本功能。
Forbidden file extensions后面输入防止盗链的文件扩展名。
Domains that may still link设定你授权允许盗链的网站。注意的不要域名的www。

Discuz的附件目录是根目录下的attachments，Discuz的附件允许的格式是：chm, pdf, zip, rar, tar, gz, bzip2, gif, jpg, jpeg, png（在Dreamhost设置中不要加,）。一直设置完成，测试OK！

相关日志

• 网站…网站…网站… (0)
• 终于回来了，最近真是背的可以… (4)
• 来自Dreamhost关于服务器集群“blingy” (0)
• 手记 (0)
• Dreamhost主机的SS开启采集功能 (0)

        这两天站点的服务器又出现了问题。速度不稳定。不停的与美国客服联系，获知：这次的问题不是整个服务器集群 Blingy 的事情（日志：来自Dreamhost关于服务器集群“blingy”），而是我的web服务器 Spyro，说是同web（主服务器）服务器上有些用户在做SEO，抢占了太多的服务器资源，造成整台服务器负载过大，拖慢了速度，又说他们已经把那些用户给残废了（原句：We’ve since disabled them，我这样翻译“已经把那些用户给残废了”感觉挺合适，很有一种中国黑社会的味道 ^_^）。但是根据我对我的站点的观察和测试，问题并没有改观和得到很好的解决，于是我又给客服发信… …
        想想我真是有够背的了，Dreamhost的Blingy是这段日子里唯一出现问题的服务器集群，而我的web服务器 Spyro又紧接着 Blingy 出问题，导致从4月初起，我的站点就没有稳定过一天。
        不过今天的情况好多了，虽然还是不稳定，但是访问缓慢的时间已经很少了。希望明天能完全恢复。同时我也在等客服的回信，给我进一步的说明。
        这种事情的发生，让我感到很无奈和窝火，访问速度对于网站来说及其重要，如果网站访问起来十分缓慢，客户访问舒适度下降，心急的人就很有可能直接关闭浏览窗口了，不仅无法很好吸引新的访客，也会造成老客户的流失。但是以现阶段的情形来看，我也没有很好的办法解决这类问题，如果发生服务器出错，对网站造成影响，我说能做的只有给客服发信，然后等待他们给我修复和回复。这样十分被动，但是不是独立的主机，这样也没有办法。侥幸的是，国外的客服一般响应都特别快，解决速度也蛮快，让人比较放心（曾经9分钟响应解决我的问题）。
        让我们一起祈祷，Spyro 赶快恢复！上帝保佑我吧。

相关日志

• 网站…网站…网站… (0)
• 终于回来了，最近真是背的可以… (4)
• 手记 (0)
• 重新设计的cnDBI团队logo (0)
• 酒?酒精？orz (0)

来自hao123的在线翻译 http://www.hao123.com/ss/fy.htm

标题：Another Anatomy
内容：

Okay, nothing silly this time, I promise…

Some of you may have noticed that we’ve been having what a problem that is, although maybe not the worst in DreamHost history, definitely in the top 5.

There has been a DreamHost Status post about it, but it’s been going on so long, there obviously needs to be more said.

The History

The events that conspired to cause this horrible performance for everybody in our “blingy” cluster actually started to take root 19 months ago.

That was when I made this post asking our customers for some suggestions on storage. I made the mistake in that post of mentioning the name of one particular storage vendor who apparently does a search for their name in rss feeds of all kinds of blogs. I won’t mention their name again here, to test if they REALLY read this blog, but they were the one on the list right after “Netapp”.

Anyway, immediately a sales guy from there was hounding me about how great their product was. It would have super-duper reliability, super-duper performance, and super-duper ease-of-management. It was super-duper expensive compared to our current solution (about 3x the price per GB), so in the end I declined.

But, over the next year he kept hounding me and hounding me, and eventually the price came down to something in line with our current costs, so we decided to try one unit for our new cluster, “Blingy”. After we were satisfied with our internal testing, Blingy went live with the new storage solution in December 2007.

Smooth Sailing

At first, everything was fine, performance was great, everybody was hunky and dory. But then, as usage started to go up, the new file system started acting up. Around the same time every night, the system would stop responding to NFS requests for a while, which would immediately break web and mail service for everybody in the entire cluster.. thousands of customers.

Our Bad

Now, it can be a big mistake to put live customers on any new system. But honestly, we’d tested it lots, researched it a ton, and we added people very slowly at first, and it performed great.

Our biggest mistake I believe had nothing to do with what specific vendor or hardware we went with.. it was simply putting so many eggs in one basket!

Even with our Netapps (which are pretty much awesome), there are problems from time-to-time. However, a typical hosting cluster will have a dozen or so Netapps, which means any problems are one twelfth as big.

With Blingy, EVERY customer is on this one “mega” filer, which in theory should make for better performance, reliability, and ease of management. And since we got the clustered solution (in an active-active configuration)… there really is no single point of hardware failure in this thing.

But, as it turns out, there are a lot of non-hardware failures in the world.

Their Bad

Well, the techs at the vendor couldn’t figure out what was causing the NFS freezing, and so they recommended us doing a major OS upgrade to hopefully fix it.

During this whole time, the fiber channel disks were slowly filling up, and we’d been trying to move large files off to the sata pool (it’s a two-tiered solution, and there’s a feature that automatically moves less-accessed data to lower tiers).. however the thing couldn’t move the data fast enough. It couldn’t finish doing a “move job” in a single day, and every day it’d sort of “crash”, which would screw up the move job, and nothing would get moved.

Also, as the disk kept getting more full, performance kept getting worse, creating a vicious cycle. We ordered some more fiber channel disk shelves at the end of February to grow the main FC volume, since we couldn’t get things off to SATA, and it was supposed to come on March 10th and be installed at the same time as the major OS upgrade.

However, the disks didn’t end up getting installed until March 25th, and at that point it turned out we could NOT grow the FC volume with these disks (well, it was technically possible, but their on-site techs recommended VERY VERY heavily against it.. it would severly impact performance), which was sort of the whole point. So now we had a new FC volume which we still had to migrate users to.

Your Bad

Of course, this whole time, new customers just kept signing up, and being added to Blingy. What were you guys thinking?

By this point we knew this was a bad idea, but we didn’t have a new cluster ready (we’d expected Blingy to grow for another couple of months), and we try to never ever grow old clusters again once they’ve been “shut off” from new signups (because in time they stablize and have very few problems).

However, the moving people off to the new FC vol, or the original SATA vol, or even the new Netapp we also added to Blingy, just wasn’t happening fast enough. So on April 2nd we bit the bullet and switched Blingy off as the “new customer” cluster and started growing good old “Postal” again. Once we did that, we were finally able to get ahead of the curve and total usage on our first fiber channel volume has been slowly dropping ever since.

We tried at that point to contact the vendor to see if we could just get more drives that WOULD allow us to grow fcvol1, but they said their manufacturers were closed for inventory for a week after the end of the quarter and we couldn’t get anything until Friday, April 11th at the absolute soonest. Later they said they could find us some they could get us by Tuesday, April 7th, and we preliminarily said we’d take them.

This whole time we had a support ticket open with the vendor about the crashes (the OS upgrade didn’t fix it), and finally on April 3rd we received notice that they’d fixed the bug that they believed was causing it! However, the patch still needed to go through their “QA”. Finally, this Sunday April 6th they said it was all ready to be deployed, so last night we did.

What Now

Well, right now, performance is still not great on fcvol1… but mail and web should be pretty much working. One thing we’ve noticed is a website that hasn’t been visited in a long time will have a big lag still upon the first visit.. but then subsequent reloads/visits seem much faster.

At least the total disk usage is coming down now, and hopefully by tomorrow it’ll be below 85% which is supposedly a magic number where performance is fine. We’re going to keep off-loading it until things are great, though. We’ve got plenty of disk space for it, the problem is just it takes so long to move it.

We also I guess will find out tonight if the NFS freezing bug is fixed by this new patch. Hopefully so.

It’s Too Late…

I realize this is probably too little too late for many of you, but I just wanted to sincerely apologize for this whole big Blingy cluster-f*ck. Also, if you’re on Blingy (you can tell from the panel by clicking “account status” and looking at “Your Email Server”, we’d like to offer you a month worth of hosting credit.

To get it, all you need to do is contact support from our panel and make the subject of your message “Blingy Account Credit”. That’s all you have to do, and we’ll credit everybody who asks (and is actually on Blingy!) next Monday (April 14th).

相关日志

• 网站…网站…网站… (0)
• 终于回来了，最近真是背的可以… (4)
• 手记 (0)
• Dreamhost主机的SS开启采集功能 (0)
• Dreamhost上实现Discuz!6.0、6.1.0伪静态化 (1)

相关日志

• 终于回来了，最近真是背的可以… (4)
• 手记 (0)
• 站长！我向您致敬！ (0)
• 盗用wi-fi信号… (0)
• 永远在路上,永远的Beta… (0)

Today has been a pretty good day of progress. We were able to complete even more moves and free up more data from the file server. Moves have been going quicker and stability is dramatically improving. Monitoring of the servers and email in the blingy cluster today have shown a significant decrease in problems. Issues do still exist but the problem is noticeably getting better. We are also pleased to note that we have more storage that will be coming early next week. We believe that this will go a long way in helping us fix this major problem.
     真的希望服务器快点恢复，我也不用为这个烦了，最近烦心的事情已经够多了…

     今天晚上和泉哥一起出去散步喝奶茶的时候，给朝阳打了电话，朝阳说看《英国病人》看的很郁闷，弄的我也有些不开心，泉哥也是，本来说我请客请阿菲一起来喝奶茶的，阿菲说郁闷，搞得泉哥也不高兴了。结果奶茶店关门，回来的时候买了几瓶啤酒和一些零食回来消愁。对酒这东西我实在没有什么特殊的感情，就是有的时候特别想喝，今天晚上喝了一点就有点晕了，泉哥和我喝的差不多，最后说没有事情，狠狠的刺激了我一下，他曾经可是标准的一杯倒啊！
     刚回来，朝阳的QQ消息也就到了，说睡了，我听了一愣，最近很反常啊，以前都很晚睡的，怎么这两天睡的这么早，她说是因为郁闷，今天心情不好。本来以为昨天晚上没有任务可以和她好好聊聊的，结果9点多就睡了，哎…今天又这样，弄的更让我郁闷了。
     真的希望她能天天开心，保持她美丽的笑容，可是…也许cat说的对，无论是谁，都不能做到这一点，也许是我真的很傻，也许是我太在意她的心情她的笑容，也许是我太敏感…
     朝阳，Keep your smile.Happy every day!You are my spiritual pillar.
     写完这些又一点半了，最近真的很累，很烦心，很郁闷。又感到喘不过气了，怕顾及不到她怠慢了她，怕社区万劫不复，怕团队出现裂痕，怕…从什么时候开始我害怕这么多事情了？
     马上去更新“我心向阳”，不知道发些什么能让朝阳开心…南昌又开始下雨了，真是无比糟糕…

相关日志

• 网站…网站…网站… (0)
• 终于回来了，最近真是背的可以… (4)
• 站长！我向您致敬！ (0)
• 盗用wi-fi信号… (0)
• 永远在路上,永远的Beta… (0)