这是网站被攻击了吗
[root@linux usr2006]# netstat -n
Active Internet connections (w/o servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 ****:80 61.47.131.71:1894 SYN_RECV
tcp 1 0 127.0.0.1:80 127.0.0.1:35072 CLOSE_WAIT
tcp 1 0 127.0.0.1:80 127.0.0.1:35073 CLOSE_WAIT
tcp 1 0 ****:80 222.64.208.52:1185 CLOSE_WAIT
tcp 1 0 127.0.0.1:80 127.0.0.1:35074 CLOSE_WAIT
tcp 1 0 127.0.0.1:80 127.0.0.1:35075 CLOSE_WAIT
tcp 1 0 127.0.0.1:80 127.0.0.1:35076 CLOSE_WAIT
tcp 1 0 127.0.0.1:80 127.0.0.1:35077 CLOSE_WAIT
tcp 1 0 ****:80 61.154.9.45:37823 CLOSE_WAIT
tcp 1 0 127.0.0.1:80 127.0.0.1:35078 CLOSE_WAIT
tcp 1 0 127.0.0.1:80 127.0.0.1:35079 CLOSE_WAIT
tcp 1 0 127.0.0.1:80 127.0.0.1:35080 CLOSE_WAIT
tcp 1 0 127.0.0.1:80 127.0.0.1:35081 CLOSE_WAIT
tcp 1 0 127.0.0.1:80 127.0.0.1:35082 CLOSE_WAIT
tcp 1 0 127.0.0.1:80 127.0.0.1:35083 CLOSE_WAIT
tcp 1 0 127.0.0.1:80 127.0.0.1:35084 CLOSE_WAIT
tcp 0 0 ****:80 221.193.200.6:1029 ESTABLISHED
tcp 1 0 127.0.0.1:80 127.0.0.1:35085 CLOSE_WAIT
tcp 1 0 127.0.0.1:80 127.0.0.1:35086 CLOSE_WAIT
tcp 1 0 127.0.0.1:80 127.0.0.1:35087 CLOSE_WAIT
tcp 1 0 127.0.0.1:80 127.0.0.1:35088 CLOSE_WAIT
tcp
tcp 1 0 127.0.0.1:80 127.0.0.1:35102 CLOSE_WAIT
tcp 1 0 127.0.0.1:80 127.0.0.1:35103 CLOSE_WAIT
tcp 0 0 ****:80 60.208.112.3:47546 ESTABLISHED
tcp 1 0 127.0.0.1:80 127.0.0.1:35104 CLOSE_WAIT
tcp 1 0 127.0.0.1:80 127.0.0.1:35105 CLOSE_WAIT
tcp 1 0 127.0.0.1:80 127.0.0.1:35106 CLOSE_WAIT
tcp 1 0 127.0.0.1:80 127.0.0.1:35107 CLOSE_WAIT
tcp 1 0 127.0.0.1:80 127.0.0.1:35108 CLOSE_WAIT
tcp 1 0 127.0.0.1:80 127.0.0.1:35109 CLOSE_WAIT
tcp 1 0 127.0.0.1:80 127.0.0.1:35114 CLOSE_WAIT
tcp 1 0 127.0.0.1:80 127.0.0.1:35115 CLOSE_WAIT
tcp 1 0 127.0.0.1:80 127.0.0.1:35116 CLOSE_WAIT
tcp 1 0 127.0.0.1:80 127.0.0.1:35117 CLOSE_WAIT
tcp 1 0 ****:80 222.184.88.58:2803 CLOSE_WAIT
tcp 1 0 127.0.0.1:80 127.0.0.1:35118 CLOSE_WAIT
tcp 1 0 127.0.0.1:80 127.0.0.1:35119 CLOSE_WAIT
tcp 1 0 127.0.0.1:80 127.0.0.1:35120 CLOSE_WAIT
tcp 1 0 127.0.0.1:80 127.0.0.1:35121 CLOSE_WAIT
tcp 1 0 127.0.0.1:80 127.0.0.1:35122 CLOSE_WAIT
tcp 1 0 127.0.0.1:80 127.0.0.1:35123 CLOSE_WAIT
tcp 1 0 127.0.0.1:80 127.0.0.1:35124 CLOSE_WAIT
tcp 0 0 ****:80 222.191.92.17:2252 ESTABLISHED
tcp 0 0 ****:80 222.191.92.17:2253 FIN_WAIT2
tcp 0 0 ****:80 219.142.223.171:1876 ESTABLISHED
tcp 371 0 ****:80 219.142.223.171:1890 ESTABLISHED
tcp 370 0 ****:80 219.142.223.171:1891 ESTABLISHED
tcp 0 0 ****:80 219.142.223.171:1888 TIME_WAIT
tcp 0 0 ****:80 66.151.181.4:23621 ESTABLISHED
tcp 376 0 ****:80 219.142.223.171:1892 ESTABLISHED
tcp 377 0 ****:80 219.142.223.171:1893 ESTABLISHED
tcp 325 0 ****:80 61.136.144.94:2617 ESTABLISHED
tcp 0 0 ****:80 219.130.184.109:1748 TIME_WAIT
tcp 1 0 ****:80 218.80.79.163:4811 CLOSE_WAIT
tcp 348 0 ****:80 121.22.58.70:45555 ESTABLISHED
tcp 341 0 ****:80 219.142.223.171:1961 ESTABLISHED
tcp 0 0 ****:80 124.192.28.74:1327 TIME_WAIT
tcp 0 0 ****:80 124.192.28.74:1371 ESTABLISHED
tcp 0 0 ****:80 222.184.216.233:33212 ESTABLISHED
tcp 360 0 ****:80 124.192.28.74:1373 ESTABLISHED
tcp 0 0 ****:80 124.192.28.74:1372 TIME_WAIT
tcp 1 0 ****:80 222.184.88.58:2825 CLOSE_WAIT
tcp 0 0 127.0.0.1:35064 127.0.0.1:80 FIN_WAIT2
tcp 0 0 127.0.0.1:35065 127.0.0.1:80 FIN_WAIT2
tcp 0 0 127.0.0.1:35066 127.0.0.1:80 FIN_WAIT2
tcp 0 0 127.0.0.1:35067 127.0.0.1:80 FIN_WAIT2
tcp 0 0 127.0.0.1:35068 127.0.0.1:80 FIN_WAIT2
tcp 0 0 127.0.0.1:35069 127.0.0.1:80 FIN_WAIT2
tcp 0 0 127.0.0.1:35062 127.0.0.1:80 FIN_WAIT2
tcp 0 0 127.0.0.1:35063 127.0.0.1:80 FIN_WAIT2
tcp 0 0 127.0.0.1:35048 127.0.0.1:80 TIME_WAIT
tcp 0 0 127.0.0.1:35049 127.0.0.1:80 TIME_WAIT
tcp 0 0 127.0.0.1:35050 127.0.0.1:80 TIME_WAIT
tcp 0 0 127.0.0.1:35106 127.0.0.1:80 FIN_WAIT2
tcp 0 0 127.0.0.1:35109 127.0.0.1:80 FIN_WAIT2
tcp 0 0 127.0.0.1:35108 127.0.0.1:80 FIN_WAIT2
tcp 0 0 127.0.0.1:35111 127.0.0.1:80 FIN_WAIT2
tcp 0 0 127.0.0.1:35110 127.0.0.1:80 FIN_WAIT2
tcp 1 0 ****:80 222.184.88.58:2823 CLOSE_WAIT
tcp 0 0 ****:80 124.192.28.74:1357 TIME_WAIT
tcp 1 0 ****:80 219.142.223.171:1251 CLOSE_WAIT
tcp 0 0 ****:80 219.142.223.171:1760 ESTABLISHED
tcp 0 1 ****:80 221.131.61.97:32560 FIN_WAIT1
tcp 277 0 ****:80 59.46.37.146:1931 ESTABLISHED
tcp 1 0 127.0.0.1:80 127.0.0.1:35054 CLOSE_WAIT
tcp 1 0 127.0.0.1:80 127.0.0.1:35055 CLOSE_WAIT
tcp 1 0 127.0.0.1:80 127.0.0.1:35056 CLOSE_WAIT
tcp 1 0 127.0.0.1:80 127.0.0.1:35057 CLOSE_WAIT
tcp 1 0 127.0.0.1:80 127.0.0.1:35058 CLOSE_WAIT
tcp 1 0 127.0.0.1:80 127.0.0.1:35059 CLOSE_WAIT
tcp 1 0 127.0.0.1:80 127.0.0.1:35060 CLOSE_WAIT
tcp 1 0 127.0.0.1:80 127.0.0.1:35063 CLOSE_WAIT
tcp 1 0 127.0.0.1:80 127.0.0.1:35064 CLOSE_WAIT
tcp 1 0 127.0.0.1:80 127.0.0.1:35065 CLOSE_WAIT
tcp 1 0 ****:80 222.169.71.173:4162 CLOSE_WAIT
tcp 1 0 127.0.0.1:80 127.0.0.1:35066 CLOSE_WAIT
打开网页特别慢,SSH上去也特别慢,TOP显示
[root@linux usr2006]# top
15:30:50 up 4:05, 1 user, load average: 82.28, 78.98, 67.29
124 processes: 54 sleeping, 70 running, 0 zombie, 0 stopped
CPU states: 78.7% user 1.2% system 0.0% nice 0.0% iowait 19.9% idle
Mem: 1030888k av, 576008k used, 454880k free, 0k shrd, 40640k buff
502312k actv, 14028k in_d, 8648k in_c
Swap: 2040244k av, 1000k used, 2039244k free 224772k cached
PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME CPU COMMAND
7379 nobody 16 0 12672 12M 4172 R 6.4 1.2 1:58 0 httpd
7911 nobody 19 0 12036 11M 4240 R 5.1 1.1 0:28 0 httpd
7193 nobody 16 0 11904 11M 4176 R 5.0 1.1 1:11 0 httpd
7495 nobody 16 0 8732 8732 4168 R 4.8 0.8 1:16 0 httpd
7597 nobody 16 0 8968 8968 4288 R 3.9 0.8 1:02 0 httpd
7854 nobody 19 0 11920 11M 4148 R 3.3 1.1 0:17 0 httpd
6781 nobody 19 0 12064 11M 4208 R 3.2 1.1 1:35 0 httpd
7752 nobody 16 0 9016 9016 4112 R 2.9 0.8 0:35 0 httpd
6991 nobody 20 0 12060 11M 4208 R 2.2 1.1 0:53 0 httpd
7590 nobody 16 0 8920 8920 4232 R 2.2 0.8 0:21 0 httpd
7416 nobody 19 0 16884 16M 4204 R 2.1 1.6 0:27 0 httpd
6794 nobody 19 0 11948 11M 4112 R 2.0 1.1 1:37 0 httpd
7197 nobody 19 0 16880 16M 4120 R 2.0 1.6 0:36 0 httpd
7924 nobody 16 0 8760 8760 4148 R 2.0 0.8 0:13 0 httpd
CPU的状态有时能达到98%左右,SSH输入的命令根本没有反应。不知应该怎么解决,谢谢帮忙!127.0.0.1的80和大于35000的连接删除了一堆,说字数太长了。
[ 本帖最后由 wlacf 于 2007-2-8 15:33 编辑 ]
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(9)
再发
复制代码
[ 本帖最后由 wlacf 于 2007-2-8 15:32 编辑 ]
复制代码
CPU 为什么只要一开apache就占这么高呢,关了就没事,而且以前没有这种情况。怪
八成是有人在攻击你!
那应该怎么办?从哪方面入手进行安全设置呢。又怎么样来判断一个服务器是不是被攻击了?从哪可以看到攻击日志呢,/var/log/messages里的系统登录日志好像正常,apache里的error_log不会看,太乱,全是些访问路径、IP地址、时间等。
[root@linux logs]# tail -n 300 /var/log/messages
Feb 8 12:47:54 linux network: Bringing up interface eth1: succeeded
Feb 8 12:47:56 linux sendmail: sendmail startup succeeded
Feb 8 12:47:57 linux sendmail: sm-client startup succeeded
Feb 8 12:47:57 linux crond: crond startup succeeded
Feb 8 12:47:57 linux logger: (oracleusr CSSD will be run out of init)
Feb 8 12:48:03 linux su(pam_unix)[3311]: session opened for user oracleusr by (uid=0)
Feb 8 12:48:03 linux su(pam_unix)[3311]: session closed for user oracleusr
Feb 8 13:24:33 linux proftpd[5067]: linux.test.com (219.142.*.*[219.142.*.*]) - FTP session opened.
Feb 8 13:24:25 linux PAM_pwdb[5067]: (ftp) session opened for user ftpuploadusr by (uid=0)
Feb 8 13:47:47 linux proftpd[5394]: linux.test.com (219.142.*.*[219.142.*.*]) - FTP session opened.
Feb 8 13:47:42 linux PAM_pwdb[5394]: (ftp) session opened for user ftpuploadusr by (uid=0)
Feb 8 13:56:52 linux proftpd[5394]: linux.test.com (219.142.*.*[219.142.*.*]) - FTP no transfer timeout, disconnected
Feb 8 13:56:58 linux proftpd[5394]: linux.test.com (219.142.*.*[219.142.*.*]) - FTP session closed.
Feb 8 14:14:38 linux sshd[5706]: Accepted publickey for usertoroot from 219.142.*.* port 4029 ssh2
Feb 8 14:19:58 linux proftpd[5067]: linux.test.com (219.142.*.*[219.142.*.*]) - FTP no transfer timeout, disconnected
Feb 8 14:20:04 linux proftpd[5067]: linux.test.com (219.142.*.*[219.142.*.*]) - FTP session closed.
Feb 8 14:26:01 linux proftpd[5909]: linux.test.com (219.142.*.*[219.142.*.*]) - FTP session opened.
Feb 8 14:25:52 linux PAM_pwdb[5909]: (ftp) session opened for user ftpuploadusr by (uid=0)
Feb 8 14:32:57 linux proftpd[5909]: linux.test.com (219.142.*.*[219.142.*.*]) - FTP no transfer timeout, disconnected
Feb 8 14:32:57 linux proftpd[5909]: linux.test.com (219.142.*.*[219.142.*.*]) - FTP session closed.
Feb 8 14:38:40 linux kernel: tcpdump uses obsolete (PF_INET,SOCK_PACKET)
Feb 8 14:39:06 linux su(pam_unix)[6052]: session opened for user root by usertoroot(uid=514)
Feb 8 14:39:10 linux kernel: device eth0 entered promiscuous mode
Feb 8 14:39:15 linux kernel: device eth0 left promiscuous mode
Feb 8 15:05:02 linux PAM_pwdb[6322]: (ftp) session opened for user ftpuploadusr by (uid=0)
Feb 8 15:08:56 linux sshd[6377]: Did not receive identification string from 219.235.231.105
Feb 8 15:08:56 linux sshd[6378]: Did not receive identification string from 219.235.231.105
Feb 8 15:12:13 linux sshd[6400]: Invalid user staff from 219.235.231.105
Feb 8 15:12:13 linux sshd[6402]: Invalid user sales from 219.235.231.105
Feb 8 15:12:13 linux sshd[6404]: Invalid user recruit from 219.235.231.105
Feb 8 15:12:15 linux sshd[6423]: Invalid user cyrus from 219.235.231.105
Feb 8 15:12:16 linux sshd[6428]: Invalid user michael from 219.235.231.105
Feb 8 15:12:16 linux sshd[6430]: User ftp from 219.235.231.105 not allowed because not listed in AllowUsers
Feb 8 15:12:16 linux sshd[6433]: Invalid user test from 219.235.231.105
Feb 8 15:12:17 linux sshd[6441]: User postgres not allowed because account is locked
Feb 8 15:12:17 linux sshd[6445]: Invalid user paul from 219.235.231.105
Feb 8 15:12:17 linux sshd[6447]: User root from 219.235.231.105 not allowed because not listed in AllowUsers
Feb 8 15:12:17 linux sshd[6449]: Invalid user guest from 219.235.231.105
Feb 8 15:12:18 linux sshd[6451]: Invalid user admin from 219.235.231.105
Feb 8 15:12:18 linux sshd[6453]: Invalid user linux from 219.235.231.105
Feb 8 15:12:18 linux sshd[6455]: Invalid user user from 219.235.231.105
Feb 8 15:12:20 linux sshd[6471]: Invalid user core from 219.235.231.105
Feb 8 15:12:20 linux sshd[6473]: Invalid user newsletter from 219.235.231.105
Feb 8 15:12:20 linux sshd[6475]: User named not allowed because account is locked
Feb 8 15:12:21 linux sshd[6477]: Invalid user visitor from 219.235.231.105
Feb 8 15:12:21 linux sshd[6479]: Invalid user ftpuser from 219.235.231.105
Feb 8 15:12:21 linux sshd[6481]: Invalid user username from 219.235.231.105
Feb 8 15:12:25 linux sshd[6483]: Invalid user administrator from 219.235.231.105
Feb 8 15:12:25 linux sshd[6485]: Invalid user library from 219.235.231.105
oracleusr ftpuploadusr usertoroot 属于正常用户
[root@linux logs]# tail -n 200 /var/log/messages
Feb 8 18:42:41 linux sshd[9728]: Invalid user linux from 61.54.68.16
Feb 8 18:42:41 linux sshd[9728]: reverse mapping checking getaddrinfo for hn.kd.dhcp failed - POSSIBLE BREAKIN ATTEMPT!
Feb 8 18:42:42 linux sshd[9730]: Invalid user debian from 61.54.68.16
Feb 8 18:42:42 linux sshd[9730]: reverse mapping checking getaddrinfo for hn.kd.dhcp failed - POSSIBLE BREAKIN ATTEMPT!
Feb 8 18:42:43 linux sshd[9732]: Invalid user darwin from 61.54.68.16
Feb 8 18:42:44 linux sshd[9732]: reverse mapping checking getaddrinfo for hn.kd.dhcp failed - POSSIBLE BREAKIN ATTEMPT!
Feb 8 18:42:45 linux sshd[9734]: Invalid user redhat from 61.54.68.16
Feb 8 18:42:45 linux sshd[9734]: reverse mapping checking getaddrinfo for hn.kd.dhcp failed - POSSIBLE BREAKIN ATTEMPT!
Feb 8 18:43:05 linux sshd[9773]: Invalid user ghost from 61.54.68.16
Feb 8 18:43:05 linux sshd[9773]: reverse mapping checking getaddrinfo for hn.kd.dhcp failed - POSSIBLE BREAKIN ATTEMPT!
Feb 8 18:43:07 linux sshd[9777]: reverse mapping checking getaddrinfo for hn.kd.dhcp failed - POSSIBLE BREAKIN ATTEMPT!
Feb 8 18:43:08 linux sshd[9779]: Invalid user erwin from 61.54.68.16
Feb 8 18:43:08 linux sshd[9779]: reverse mapping checking getaddrinfo for hn.kd.dhcp failed - POSSIBLE BREAKIN ATTEMPT!
Feb 8 18:43:09 linux sshd[9781]: Invalid user update from 61.54.68.16
Feb 8 18:43:09 linux sshd[9781]: reverse mapping checking getaddrinfo for hn.kd.dhcp failed - POSSIBLE BREAKIN ATTEMPT!
Feb 8 18:43:10 linux sshd[9783]: Invalid user kiss from 61.54.68.16
Feb 8 18:43:10 linux sshd[9783]: reverse mapping checking getaddrinfo for hn.kd.dhcp failed - POSSIBLE BREAKIN ATTEMPT!
Feb 8 18:43:11 linux sshd[9785]: Invalid user army from 61.54.68.16
[root@linux logs]# tail -n 200 /var/log/messages
Feb 8 18:43:24 linux sshd[9822]: User root from 61.54.68.16 not allowed because not listed in AllowUsers
Feb 8 18:43:25 linux sshd[9824]: reverse mapping checking getaddrinfo for hn.kd.dhcp failed - POSSIBLE BREAKIN ATTEMPT!
Feb 8 18:43:25 linux sshd[9824]: User root from 61.54.68.16 not allowed because not listed in AllowUsers
Feb 8 18:43:27 linux sshd[9828]: User root from 61.54.68.16 not allowed because not listed in AllowUsers
Feb 8 18:43:28 linux sshd[9830]: reverse mapping checking getaddrinfo for hn.kd.dhcp failed - POSSIBLE BREAKIN ATTEMPT!
Feb 8 18:43:28 linux sshd[9830]: User root from 61.54.68.16 not allowed because not listed in AllowUsers
Feb 8 18:43:29 linux sshd[9832]: reverse mapping checking getaddrinfo for hn.kd.dhcp failed - POSSIBLE BREAKIN ATTEMPT!
Feb 8 18:43:37 linux sshd[9851]: reverse mapping checking getaddrinfo for hn.kd.dhcp failed - POSSIBLE BREAKIN ATTEMPT!
Feb 8 18:43:37 linux sshd[9851]: User root from 61.54.68.16 not allowed because not listed in AllowUsers
Feb 8 18:43:38 linux sshd[9853]: reverse mapping checking getaddrinfo for hn.kd.dhcp failed - POSSIBLE BREAKIN ATTEMPT!
Feb 8 18:43:38 linux sshd[9853]: User root from 61.54.68.16 not allowed because not listed in AllowUsers
Feb 8 18:43:54 linux sshd[9881]: reverse mapping checking getaddrinfo for hn.kd.dhcp failed - POSSIBLE BREAKIN ATTEMPT!
Feb 8 18:43:54 linux sshd[9881]: User root from 61.54.68.16 not allowed because not listed in AllowUsers
Feb 8 18:43:55 linux sshd[9883]: reverse mapping checking getaddrinfo for hn.kd.dhcp failed - POSSIBLE BREAKIN ATTEMPT!
Feb 8 18:43:55 linux sshd[9883]: User root from 61.54.68.16 not allowed because not listed in AllowUsers
Feb 8 18:43:59 linux sshd[9888]: reverse mapping checking getaddrinfo for hn.kd.dhcp failed - POSSIBLE BREAKIN ATTEMPT!
Feb 8 18:43:59 linux sshd[9888]: User root from 61.54.68.16 not allowed because not listed in AllowUsers
Feb 8 18:44:01 linux sshd[9890]: reverse mapping checking getaddrinfo for hn.kd.dhcp failed - POSSIBLE BREAKIN ATTEMP
中间有删改,所字数超过限制
貌似在dos啦
被SYN ddos了.没有根治的方法,加syn硬防.如果一心想搞挎你,你只有打119了.
74.6.*.* 这一段地址属于僵尸网络的? 碰到过它们在CC
亚洲的多。 .