Siege端口被重用

时间:2013-11-04 14:06:09

标签: http traffic siege

我正在运行多个围攻实例,所以围攻重用端口作为结果,一些请求没有通过。有没有办法让不同的围攻实例可以使用不同的端口范围?

   HTTP/1.1 200   0.00 secs:     146 bytes ==> 
   HTTP/1.1 200   0.00 secs:     146 bytes ==> 
   HTTP/1.1 200   0.00 secs:     146 bytes ==> 
   HTTP/1.1 200   0.00 secs:     146 bytes ==> 
   HTTP/1.1 200   0.01 secs:     146 bytes ==> 
   HTTP/1.1 200   0.00 secs:     146 bytes ==> 
   HTTP/1.1 200   0.01 secs:     146 bytes ==> 
   [alert] socket: 671299328 select timed out: Connection timed out
   [alert] socket: 788797184 select timed out: Connection timed out
   [alert] socket: 721655552 select timed out: Connection timed out
   [alert] socket: 738440960 select timed out: Connection timed out
   HTTP/1.1 200   0.01 secs:     146 bytes ==> /
   HTTP/1.1 200   0.01 secs:     146 bytes ==> /
   [alert] socket: 822368000 select timed out: Connection timed out
   HTTP/1.1 200   0.01 secs:     146 bytes ==> /
   HTTP/1.1 200   0.01 secs:     146 bytes ==> /
   HTTP/1.1 200   0.01 secs:     146 bytes ==> /

2 个答案:

答案 0 :(得分:0)

我看到你有很多请求,你认为你可以遇到KeepAlive的问题。

在服务器套接字上打开的时间比单独连接要长一点。如果KeepAlive设置为高值,则可以完全耗尽端口。

答案 1 :(得分:0)

你可以设置 net.ipv4.tcp_tw_reuse = 1 net.ipv4.tcp_tw_recycle = 1 在/ etc / sysctl文件中运行#sysctl -p以激活它。 请试一试。希望这可以帮到你。