作者归档：John

说说alienvps

4条回复

上次在wht看到alienvps的openvz促销，256内存只要4刀一个月，就搞了个拿来做后端，结果烦心事不断

ps:这里所谓烦心事都是真实发生的物理状况，绝非个人感觉

首先，vps在我12月4号付款以后是可以自动开通的，可惜开通以后给分配到了一个不能访问的ip（不是撞墙，而是根本就是down掉的ip），写ticket过去，46分钟后给换了新ip，开始正常访问

好景不长，12月7号，ip再次down掉，写ticket过去，4小时后回复了“your VPS will be back online soon”，6小时候，换上了新ip，解释说他们有个ip段有问题，而我刚好受影响，给了承诺“Your IP will not need to change anymore.”。

这次折腾以后，稳定了很长一段时间，一直到大概一周前，我发现内存还剩一半没用的时候，就不能启动新进程，直接报错内存不足，于是写ticket问，结果居然过了两天没答复，结果我自己google到了答案，要求他们协助，更改privvmpages和shmpages的值，这一等就是5天，我也没抱任何希望了，反正到期就move，结果昨天（20号），有回复了，说已经调整了，结果我冲上去cat /proc/user_beancounters ，看到的那两个值依旧是65536.

以上这些都还算温柔，最生猛的在下面。

一小时左右前，我正在shell上编辑文件，突然就看到系统即将halt的广播消息，我想可能只是他们要重启下服务器，就没管，过了5分钟，依旧不能登陆回去，就冲到panel看，服务器状态正常，以为又是什么抽风bug，就手动重启了，结果已经不能登陆。

然后就小小的试了试ping，结果：

92 bytes from 209.188.5.226: Time to live exceeded
Vr HL TOS  Len   ID Flg  off TTL Pro  cks      Src      Dst
4  5  00 5400 19c8   0 0000  01  01 7ec6 192.168.1.3  184.171.166.196

从来没看到过ping是这样的结果，就很好奇的traceroute了一下，结果看到包在两个ip之间跳来跳去，直到ttl- –

traceroute to 184.171.166.196 (184.171.166.196), 32 hops max, 52 byte packets
1  router (192.168.1.1)  66.777 ms  0.935 ms  0.895 ms
2  reverse.gdsz.cncnet.net (220.249.240.1)  54.543 ms  46.624 ms  31.539 ms
3  120.80.199.209 (120.80.199.209)  25.083 ms  26.228 ms  25.491 ms
4  120.80.198.161 (120.80.198.161)  26.260 ms  25.815 ms  32.681 ms
5  120.82.0.161 (120.82.0.161)  30.528 ms  30.764 ms  29.982 ms
6  219.158.10.37 (219.158.10.37)  31.689 ms  32.575 ms  32.063 ms
7  219.158.3.78 (219.158.3.78)  123.173 ms  119.879 ms  116.987 ms
8  * * *
9  te2-4.mpd01.sjc03.atlas.cogentco.com (154.54.6.85)  331.383 ms  333.725 ms  333.047 ms
10  te2-2.mpd01.sjc01.atlas.cogentco.com (66.28.4.73)  291.021 ms
te3-2.mpd01.sjc01.atlas.cogentco.com (154.54.6.81)  342.749 ms *
11  * te0-3-0-2.mpd21.lax01.atlas.cogentco.com (154.54.2.129)  354.663 ms  351.331 ms
12  * * *
13  vl3512.na41.b023003-0.phx02.atlas.cogentco.com (38.20.49.214)  346.059 ms *  351.909 ms
14  * 38.104.116.186 (38.104.116.186)  312.681 ms *
15  * cr1.ss.122.3.1.phx0.cwie.net (174.138.168.2)  355.872 ms  355.699 ms
16  209.188.5.226 (209.188.5.226)  360.190 ms * *
17  * * *
18  209.188.5.226 (209.188.5.226)  360.637 ms *  359.814 ms
19  * 174.138.175.145 (174.138.175.145)  357.932 ms *
20  209.188.5.226 (209.188.5.226)  360.983 ms *  358.027 ms
21  * 174.138.175.145 (174.138.175.145)  357.900 ms  358.292 ms
22  209.188.5.226 (209.188.5.226)  359.140 ms  365.133 ms  358.821 ms
23  174.138.175.145 (174.138.175.145)  356.940 ms  359.810 ms *
24  209.188.5.226 (209.188.5.226)  358.559 ms  359.547 ms  356.870 ms
25  174.138.175.145 (174.138.175.145)  356.949 ms  358.005 ms *
26  * * *
27  174.138.175.145 (174.138.175.145)  359.024 ms *  358.757 ms
28  * * *
29  174.138.175.145 (174.138.175.145)  360.654 ms  357.546 ms *
30  * * 209.188.5.226 (209.188.5.226)  357.501 ms

然后再去看panel，发现ip居然变了，然后邮箱就收到信了：“We apologize for the inconvenience, we have new IP space and have no choice but to change the IP address of your VPS.”

够简洁明了吧？靠，居然可以这样不负责任的突然换掉一个跑了半个月多的vps的主ip也是唯一一个ip，幸好只是个后端，只需要在前端稍微改改配置就可以恢复访问，不然，就是好几个小时的downtime了

不过因祸得福，新ip网通走的是比较nb的nlayer线路，电信走xo，原来ping要350左右，现在居然降到了250左右，电信更nb，只有190，和直连网通的xeex有的一拼

不过，这样的服务商，还是躲远点好。。说不定什么时候再给你换个ip，气死你

cs说了一句很无语的话：Thanks for bearing with us as we are still learning the ropes.好吧，你们慢慢折腾，我先走了

The connection was reset

发表评论

The connection to the server was reset while the page was loading.
* The site could be temporarily unavailable or too busy. Try again in a few
moments.

* If you are unable to load any pages, check your computer’s network
connection.

* If your computer or network is protected by a firewall or proxy, make sure
that Firefox is permitted to access the Web.

你见过TTL这么低的vps么？

发表评论

当时我就震惊了，居然有vps可以在24跳之后

ping -c 10 69.194.193.10
PING 69.194.193.10 (69.194.193.10): 56 data bytes
64 bytes from 69.194.193.10: icmp_seq=0 ttl=39 time=346.678 ms
64 bytes from 69.194.193.10: icmp_seq=1 ttl=39 time=347.852 ms
Request timeout for icmp_seq 2
64 bytes from 69.194.193.10: icmp_seq=3 ttl=39 time=346.919 ms
64 bytes from 69.194.193.10: icmp_seq=4 ttl=39 time=347.288 ms
64 bytes from 69.194.193.10: icmp_seq=5 ttl=39 time=347.643 ms
64 bytes from 69.194.193.10: icmp_seq=6 ttl=39 time=347.530 ms
64 bytes from 69.194.193.10: icmp_seq=7 ttl=39 time=347.325 ms
64 bytes from 69.194.193.10: icmp_seq=8 ttl=39 time=350.973 ms

— 69.194.193.10 ping statistics —
10 packets transmitted, 8 packets received, 20.0% packet loss
round-trip min/avg/max/stddev = 346.678/347.776/350.973/1.259 ms

traceroute 69.194.193.10
traceroute to 69.194.193.10 (69.194.193.10), 64 hops max, 52 byte packets
1  router (192.168.1.1)  2.081 ms  0.780 ms  0.745 ms
2  reverse.gdsz.cncnet.net (220.249.240.1)  159.016 ms  14.006 ms  30.284 ms
3  120.80.199.209 (120.80.199.209)  7.601 ms  8.884 ms  8.398 ms
4  120.80.198.161 (120.80.198.161)  9.629 ms  8.127 ms  9.853 ms
5  120.80.0.177 (120.80.0.177)  14.498 ms  13.422 ms  13.361 ms
6  219.158.19.77 (219.158.19.77)  15.434 ms  13.862 ms  14.777 ms
7  219.158.4.89 (219.158.4.89)  84.508 ms  67.957 ms  67.473 ms
8  219.158.4.162 (219.158.4.162)  68.866 ms  68.720 ms  69.484 ms
9  sl-st20-sj-15-0-1.sprintlink.net (144.223.242.81)  271.461 ms  273.240 ms  277.230 ms
10  sl-st30-sj-0-0-2-0.sprintlink.net (144.232.0.208)  272.401 ms  273.826 ms  277.634 ms
11  sl-st31-sj-0-8-0-0.sprintlink.net (144.232.3.29)  242.735 ms
sl-st31-sj-0-8-2-0.sprintlink.net (144.232.3.30)  225.602 ms
sl-st31-sj-0-12-0-3.sprintlink.net (144.232.3.33)  229.353 ms
12  * sl-xocomm-337432-0.sprintlink.net (144.223.1.2)  375.140 ms  471.434 ms
13  vb2000d1.rar3.sanjose-ca.us.xo.net (207.88.13.98)  408.976 ms  412.283 ms  407.439 ms
14  te-2-0-0.rar3.washington-dc.us.xo.net (207.88.12.70)  439.822 ms  441.770 ms  444.518 ms
15  ae0d0.mcr1.newark-nj.us.xo.net (216.156.0.22)  476.545 ms  473.820 ms  473.274 ms
16  ae1d0.mcr1.nyc-ny.us.xo.net (216.156.1.9)  463.897 ms  464.069 ms  461.836 ms
17  207.239.51.86 (207.239.51.86)  303.557 ms  304.349 ms  305.248 ms
18  edge-09-teb1.us.as19318.net (66.45.224.183)  305.153 ms  305.844 ms  304.002 ms
19  209.250.226.70 (209.250.226.70)  305.978 ms  307.005 ms  306.427 ms
20  66.45.226.114 (66.45.226.114)  306.943 ms  304.059 ms  304.846 ms
21  testipnj.vpscolo.com (69.194.193.10)  304.967 ms  305.429 ms  304.949 ms

install php zend optimizer with yum on centos

发表评论

Contents: atomic.repo

# Name: Atomic Rocket Turtle RPM Repository for CentOS / Red Hat Enterprise Linux 5 –
# URL: http://www.atomicrocketturtle.com/
[atomic]
name = CentOS / Red Hat Enterprise Linux $releasever – atomicrocketturtle.com
mirrorlist = http://www.atomicorp.com/mirrorlist/atomic/centos-5-$basearch
#mirrorlist = http://www.atomicorp.com/channels/atomic/centos/5/mirrors-atomic
enabled = 1
priority = 1
protect = 0
gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY.art.txt
gpgcheck = 1

# Almost Stable, release candidates for [atomic]
[atomic-testing]
name = CentOS / Red Hat Enterprise Linux $releasever – atomicrocketturtle.com – (Testing)
mirrorlist = http://www.atomicorp.com/mirrorlist/atomic-testing/centos-5-$basearch
enabled = 0
priority = 1
protect = 0
gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY.art.txt
gpgcheck = 1

# Untested, Unstable, known buggy, and incomplete packages.
#[atomic-bleeding]
#name = CentOS / Red Hat Enterprise Linux $releasever – atomicrocketturtle.com – (Bleeding)
#baseurl = http://www.atomicorp.com/channels/atomic-bleeding/centos/5/$basearch/
#enabled = 0
#priority = 1
#protect = 0
#gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY.art.txt
#gpgcheck = 1

yum install php-zend-optimizer

用组策略+文件权限干掉QQ的安全组件

发表评论

恩，传说中会扫硬盘的QQ，还是要防着点的好，考虑到中文版的Q太过于庞大，对于我这种只需要基本交流功能的人来说，英文版的Q的功能已经足够了，自己折腾了一下，用组策略搞定了弹窗，彻底干掉了安全模块。废话不多说，开工

首先，开始～运行，gpedit.msc

展开计算机配置>Windows设置>安全设置>软件限制策略>附加规则>右键新建哈希规则

添加qq安装目录下\bin下的这几个文件

auclt.exe
bugreport.exe
QQSafeUD.exe
TXOPShow.exe
TXPlatform.exe

另外还有临时文件夹下也有点货，在添加文件时候，直接输入下面这两个地址点确定

%temp%\qqsafeud.exe

%temp%\selfupdate.exe

最后，打开资源管理器，输入地址%userprofile%\AppData\Roaming\Tencent\QQ，回车后设置safebase的权限为拒绝everyone，done