ygrek / mldonkey

cross-platform multi-network p2p daemon (previously at http://mldonkey.sourceforge.net/)
Other
251 stars 46 forks source link

Same IP makes many connects to the tracker buildin #43

Closed ed29 closed 4 years ago

ed29 commented 4 years ago

Hi:

There are many connects of same ip estableshed to the tracker buildin.I print the netstat and export to the file below.

For an example,ip 49.205.40.85 make 262 connects to the tracker.

netstat-report.txt

ed29 commented 4 years ago

image The count of connects (mainly to tracker)

ygrek commented 4 years ago

I don't see why is this mldonkey problem? It depends what that other ip is doing, e.g. I can imagine it is a NAT gateway and all those connections are actually different clients, or it can be even one client with many torrents tracking on this instance and doing many simultaneous connections.

ed29 commented 4 years ago

Ok

ed29 commented 4 years ago

@ygrek Hi,the mldonkey stoped,the log file:http://files.ed29.com/mlnet.log (for tmp)

2020/03/16 20:06:02 [Ip] async_ip : unexpected exn socket failed: Too many open files 2020/03/16 20:06:02 Exception (socket failed: Too many open files) before connect to host 192.184.90.232:6881 2020/03/16 20:06:02 [Ip] async_ip : unexpected exn socket failed: Too many open files 2020/03/16 20:06:02 Exception (socket failed: Too many open files) before connect to host 192.184.90.232:6881 2020/03/16 20:06:02 [Ip] async_ip : unexpected exn socket failed: Too many open files 2020/03/16 20:06:02 Exception (socket failed: Too many open files) before connect to host 192.184.90.232:6881 2020/03/16 20:06:02 [Ip] async_ip : unexpected exn socket failed: Too many open files 2020/03/16 20:06:02 Exception (socket failed: Too many open files) before connect to host 192.184.90.232:6881 2020/03/16 20:06:02 [Ip] async_ip : unexpected exn socket failed: Too many open files 2020/03/16 20:06:02 [Gettext] save_strings: Error Sys_error("mlnet_strings.zh_CN.UTF-8: Too many open files")

ed29 commented 4 years ago

图片

ed29 commented 4 years ago

@ygrek Hi,sorry for that,i think it's caused by my configure of the default tracker.I filled in the default tracker in hostname style before. Now,i clear it,just leave empty,the connecting looks ok.