检查 统计 异常 通信 time_wait
[root@hadoop1 conf]# netstat -n | grep -v 127.0.0.1 | grep -v :3306 | grep TIME_WAIT | sort -k 5n |uniq -f 5 -c
33 tcp 0 0 192.168.2.51:45792 14.215.178.77:80 TIME_WAIT
5 tcp 0 0 192.168.2.51:56624 27.148.182.135:80 TIME_WAIT
1 tcp 0 0 192.168.2.51:44206 42.62.119.69:443 TIME_WAIT
4 tcp 0 0 192.168.2.51:45603 43.247.184.242:80 TIME_WAIT
8 tcp 0 0 192.168.2.51:54266 58.17.85.89:80 TIME_WAIT
33 tcp 0 0 192.168.2.51:39524 58.211.137.80:80 TIME_WAIT
64 tcp 0 0 192.168.2.51:34909 58.22.108.30:80 TIME_WAIT
10 tcp 0 0 192.168.2.51:47820 58.23.103.203:80 TIME_WAIT
6 tcp 0 0 192.168.2.51:32801 58.58.81.141:80 TIME_WAIT
12 tcp 0 0 192.168.2.51:48509 61.135.186.152:80 TIME_WAIT
14 tcp 0 0 192.168.2.51:51475 61.188.37.201:80 TIME_WAIT
2 tcp 0 0 192.168.2.51:54732 61.54.47.129:80 TIME_WAIT
1 tcp 0 0 192.168.2.51:41692 106.11.249.143:80 TIME_WAIT
14 tcp 0 0 192.168.2.51:55881 106.11.172.41:80 TIME_WAIT
21 tcp 0 0 192.168.2.51:54285 107.151.129.28:80 TIME_WAIT
3 tcp 0 0 192.168.2.51:32779 112.65.69.50:443 TIME_WAIT
5 tcp 0 0 192.168.2.51:43531 112.90.216.101:80 TIME_WAIT
26 tcp 0 0 192.168.2.51:45554 112.90.58.190:80 TIME_WAIT
1 tcp 0 0 192.168.2.51:50208 112.90.32.1:80 TIME_WAIT
15 tcp 0 0 192.168.2.51:53542 112.90.32.200:80 TIME_WAIT
32 tcp 0 0 192.168.2.51:43478 113.105.245.108:80 TIME_WAIT
1 tcp 0 0 192.168.2.51:42405 113.96.139.38:80 TIME_WAIT
2 tcp 0 0 192.168.2.51:56533 114.236.141.197:80 TIME_WAIT
4 tcp 0 0 192.168.2.51:56974 115.100.61.100:80 TIME_WAIT
8 tcp 0 0 192.168.2.51:40910 116.211.121.149:80 TIME_WAIT
5 tcp 0 0 192.168.2.51:40940 117.27.142.28:80 TIME_WAIT
13 tcp 0 0 192.168.2.51:49132 117.34.14.80:80 TIME_WAIT
2 tcp 0 0 192.168.2.51:34077 119.146.74.48:80 TIME_WAIT
37 tcp 0 0 192.168.2.51:40705 119.146.74.49:443 TIME_WAIT
3 tcp 0 0 192.168.2.51:49027 121.9.212.242:80 TIME_WAIT
1 tcp 0 0 192.168.2.51:52736 122.136.32.134:80 TIME_WAIT
2 tcp 0 0 192.168.2.51:41766 123.125.52.0:80 TIME_WAIT
2 tcp 0 0 192.168.2.51:60388 123.125.142.41:80 TIME_WAIT
4 tcp 0 0 192.168.2.51:50569 123.129.244.226:80 TIME_WAIT
50 tcp 0 0 192.168.2.51:35253 123.58.33.69:80 TIME_WAIT
6 tcp 0 0 192.168.2.51:33775 125.46.65.105:80 TIME_WAIT
5 tcp 0 0 192.168.2.51:49940 125.46.65.75:80 TIME_WAIT
5 tcp 0 0 192.168.2.51:59930 125.46.65.105:80 TIME_WAIT
1 tcp 0 0 192.168.2.51:59389 140.205.172.22:443 TIME_WAIT
11 tcp 0 0 192.168.2.51:56088 140.207.234.48:80 TIME_WAIT
58 tcp 0 0 192.168.2.51:32909 157.255.128.111:80 TIME_WAIT
1 tcp 0 0 192.168.2.51:35178 157.255.144.90:80 TIME_WAIT
2 tcp 0 0 192.168.2.51:35331 157.255.128.111:80 TIME_WAIT
1 tcp 0 0 192.168.2.51:35366 157.255.144.90:80 TIME_WAIT
7 tcp 0 0 192.168.2.51:35471 157.255.128.111:80 TIME_WAIT
32 tcp 0 0 192.168.2.51:35826 157.255.26.45:80 TIME_WAIT
1 tcp 0 0 192.168.2.51:37188 157.255.144.90:80 TIME_WAIT
25 tcp 0 0 192.168.2.51:37199 157.255.26.45:80 TIME_WAIT
1 tcp 0 0 192.168.2.51:38627 157.255.144.90:80 TIME_WAIT
18 tcp 0 0 192.168.2.51:38631 157.255.26.45:80 TIME_WAIT
244 tcp 0 0 192.168.2.51:47322 157.255.26.160:80 TIME_WAIT
13 tcp 0 0 192.168.2.51:60252 157.255.128.111:80 TIME_WAIT
30 tcp 0 0 192.168.2.51:35275 163.177.151.81:80 TIME_WAIT
5 tcp 0 0 192.168.2.51:41042 163.177.8.34:443 TIME_WAIT
9 tcp 0 0 192.168.2.51:42605 163.177.8.48:80 TIME_WAIT
1 tcp 0 0 192.168.2.51:43457 163.177.8.34:443 TIME_WAIT
6 tcp 0 0 192.168.2.51:43519 163.177.8.48:80 TIME_WAIT
1 tcp 0 0 192.168.2.51:43529 163.177.8.34:443 TIME_WAIT
1 tcp 0 0 192.168.2.51:43529 163.177.8.48:80 TIME_WAIT
1 tcp 0 0 192.168.2.51:43562 163.177.8.34:443 TIME_WAIT
14 tcp 0 0 192.168.2.51:43621 163.177.8.48:80 TIME_WAIT
1 tcp 0 0 192.168.2.51:43707 163.177.8.34:443 TIME_WAIT
17 tcp 0 0 192.168.2.51:43751 163.177.8.48:80 TIME_WAIT
1 tcp 0 0 192.168.2.51:43819 163.177.8.34:443 TIME_WAIT
6 tcp 0 0 192.168.2.51:43861 163.177.8.48:80 TIME_WAIT
3 tcp 0 0 192.168.2.51:43882 163.177.8.34:443 TIME_WAIT
17 tcp 0 0 192.168.2.51:43971 163.177.8.48:80 TIME_WAIT
4 tcp 0 0 192.168.2.51:44329 163.177.8.34:443 TIME_WAIT
275 tcp 0 0 192.168.2.51:44969 163.177.8.48:80 TIME_WAIT
2 tcp 0 0 192.168.2.51:49643 163.177.8.49:443 TIME_WAIT
4 tcp 0 0 192.168.2.51:49669 163.177.8.34:80 TIME_WAIT
3 tcp 0 0 192.168.2.51:51058 163.177.8.49:443 TIME_WAIT
2 tcp 0 0 192.168.2.51:53572 163.177.8.45:80 TIME_WAIT
1 tcp 0 0 192.168.2.51:42464 180.149.138.197:80 TIME_WAIT
6 tcp 0 0 192.168.2.51:40324 180.97.76.151:80 TIME_WAIT
1 tcp 0 0 192.168.2.51:43040 183.3.226.69:80 TIME_WAIT
23 tcp 0 0 192.168.2.51:58716 192.168.2.51:9000 TIME_WAIT
16 tcp 0 0 192.168.2.51:47697 202.91.251.98:80 TIME_WAIT
9 tcp 0 0 192.168.2.51:43935 203.208.39.237:80 TIME_WAIT
8 tcp 0 0 192.168.2.51:51661 203.208.51.57:80 TIME_WAIT
6 tcp 0 0 192.168.2.51:54117 203.208.39.235:80 TIME_WAIT
4 tcp 0 0 192.168.2.51:56466 207.176.216.246:80 TIME_WAIT
13 tcp 0 0 192.168.2.51:33635 210.22.248.148:80 TIME_WAIT
22 tcp 0 0 192.168.2.51:50167 218.29.14.66:80 TIME_WAIT
4 tcp 0 0 192.168.2.51:49117 219.138.202.5:80 TIME_WAIT
8 tcp 0 0 192.168.2.51:34454 220.170.186.169:443 TIME_WAIT
10 tcp 0 0 192.168.2.51:45702 220.170.186.169:80 TIME_WAIT
2 tcp 0 0 192.168.2.51:34331 221.10.205.150:80 TIME_WAIT
70 tcp 0 0 192.168.2.51:37536 221.238.248.9:80 TIME_WAIT
[root@hadoop1 conf]#
检查 统计 异常 通信 time_wait的更多相关文章
- Java检查型异常和非检查型异常
1.代码 public class ExcepTest { /** * @param args */ public static void main(String[] args) { System.e ...
- java 检查抛出的异常是否是要捕获的检查性异常或运行时异常或错误
/** * Return whether the given throwable is a checked exception: * that is, neither a RuntimeExcepti ...
- 检查型异常（Checked Exception）与非检查型异常（Unchecked Exception）
这两个概念看了忘,碰着了又看,老是傻傻的分不清楚,今天把心得结合从网上搜的资料简单整理一下,希望帮自己明确区分开这两个概念,并牢牢的记住 1.检查型异常(Checked Exception) 个人理解 ...
- java 把被检查的异常转换为不检查的异常
一.当我们不知道该怎么处理这个异常,但是也不想把它"吞"了,或者打印一些无用的信息,可以使用异常链的思路解决.可以直接报"被检查的异常"包装进RuntimeEx ...
- Java中Error和Exception的异同以及运行时异常（Runtime exception)与检查型异常（checked exception）的区别
一:Error和Exception的基本概念: 首先Exception和Error都是继承于Throwable 类,在 Java 中只有 Throwable 类型的实例才可以被抛出(throw)或者捕 ...
- 检查型异常和非检查型异常——Java
文章目录 检查型异常和非检查型异常--Java 检查型异常 非检查型异常 结语 检查型异常和非检查型异常--Java Java语言规范将派生于Error类或RuntimeExceprion类的所有异常 ...
- 应急分析异常通信的小思路和自己写的小工具（查询CNAME和A记录）
一.背景: 在很多时候,应急会发现.卧槽,异常连接,只有一个域名或者IP. 怎么办?上防火墙看记录,查域名对应的记录累成狗,自己把之前的代码改了改,写了个小工具,一条命令查询DNS相关记录,也可以指定 ...
- LeetCode 5272. 5272. 统计参与通信的服务器 Count Servers that Communicate
地址 https://leetcode-cn.com/problems/count-servers-that-communicate/ 题目描述这里有一幅服务器分布图,服务器的位置标识在 m * n ...
- 浏览器的云加速可能导致IP统计异常
前段时间弄个流量统计相关的东西,请求展示图片时根据请求的IP进行 md5 签名生成点击链接的验证参数,结果发现一个莫名其妙的问题 发现点击日志中有一小部分点击的IP居然不一致,如果是开放给别人用可能存 ...
随机推荐
- InnoDB体系架构总结（一）
缓冲池: 是一块内存区域,通过内存的速度来弥补磁盘速度较慢对数据库性能的影响.在数据库中读取的页数据会存放到缓冲池中,下次再读取相同页的时候,会首先判断该页是否在缓冲池中.对于数据库中页的修改操 ...
- MySQL数据类型与操作
内容提要: 建表完整语法规范(create table 表格(字段名1 类型 (宽度) 约束条件)) MySQL数据库数据类型(整型.浮点型.字符类型(char与varchar).日期类型.枚举与集合 ...
- 给Django中的url起名字
url反转 =>reverse 1.from django.shortcuts import reverse 2. 利用reverse函数对URL名称进行反转 reverse(url名称 ...
- 洛谷2016 战略游戏 （0/1状态的普通树形Dp）
题意: 给出一个树,覆盖树上某一个点的花费为w[i],求树上每一条边至少有一个点覆盖的最小花费. 细节: 1.一条边的两端可以均被覆盖,但是不能存在一条边的两端都不被覆盖. 2.可能存在 分析: 对于 ...
- jquery取当前节点的上级ID
- oracle 恢复中的switch datafile all是什么意思
使用rman进行恢复时,如果使用了set name修改文件路径,那么恢复后,控制文件里面的信息是没有修改该的,如果要同步控制文件的信息那么就需要使用 switch datafile allall这个可 ...
- bzoj5106 [CodePlus2017]汀博尔 二分
[CodePlus2017]汀博尔 Time Limit: 10 Sec Memory Limit: 512 MBSubmit: 202 Solved: 75[Submit][Status][Di ...
- Error:Uninitialized object exists on backward branch 70 Exception Details:
网上下载了一个demo,编译出现如下错误: Gradle sync failed: Uninitialized object exists on backward branch 70 Exceptio ...
- python监控tomcat日记文件
最近写了一个用python监控tomcat日记文件的功能 实现的功能: 监控日记文件中实时过来的记录,统计每分钟各个接口调用次数,统计结果插入oracle #!/usr/bin/python # -* ...
- msp430入门编程25
msp430中C语言开发环境搭建 msp430入门学习 msp430入门编程