Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

accpet error,the conn has closed #763

Open
sumerzhang opened this issue Mar 18, 2021 · 3 comments
Open

accpet error,the conn has closed #763

sumerzhang opened this issue Mar 18, 2021 · 3 comments
Labels
bug Something isn't working

Comments

@sumerzhang
Copy link

Describe the bug
A clear and concise description of what the bug is.

2021/03/18 11:25:33.524 [D] [client.go:216] new tcp connection with the goal of 221.204.188.112:443, remote address:102.85.217.62:36094
2021/03/18 11:25:33.540 [D] [client.go:216] new tcp connection with the goal of 42.7.50.240:443, remote address:102.85.217.62:36102
2021/03/18 11:25:33.544 [D] [client.go:216] new tcp connection with the goal of 101.26.38.88:443, remote address:102.85.217.62:36106
2021/03/18 11:25:34.381 [W] [client.go:213] connect to 192.168.2.181:80 error dial tcp 192.168.2.181:80: connect: no route to host
2021/03/18 15:04:03.809 [D] [client.go:216] new tcp connection with the goal of 192.168.2.220:22, remote address:102.85.217.62:13113
2021/03/18 15:24:25 mux: ping time out, checktime 2 threshold 1
2021/03/18 15:24:25 close mux
2021/03/18 15:24:25.739 [W] [client.go:165] accpet error,the conn has closed
2021/03/18 15:24:25.739 [E] [client.go:92] Accept server data error read tcp 192.168.2.220:56550->252.146.216.63:8024: use of closed network connection, end this service
2021/03/18 15:24:26 mux: read session unpack from connection err read tcp 192.168.2.220:56552->252.146.216.63:8024: use of closed network connection

Expected behavior
accpet error,the conn has closed,
有10个客户端程序,只有其中这个程序运行中,但是假死,客户端掉线状态,
查看了#567, 但是在新版的0.26.9也会出现这种情况,是不是其他问题呢?

期待大佬解答,谢谢

npc.conf文件里面设置了

[common]
server_addr=xxx.xxx.xxx.xxx:8024
conn_type=tcp
vkey=honon6s44jhd3sm3
auto_connection=true
max_conn=10000
crypt=true
compress=true
disconnect_timeout=1

[socks5]
mode=socks5
server_port=8026

Screenshots or logs
Add screenshots or logs to help explain your problem.

Server (please complete the following information):

  • OS: Centos7
  • ARCH: Amd64, Arm
  • Tunnel TCP, HTTP
  • Version 0.26.9

Client (please complete the following information):

  • OS:Ubuntu18
  • ARCH: Amd64
  • Tunnel TCP
  • Version 0.26.9
@sumerzhang sumerzhang added the bug Something isn't working label Mar 18, 2021
@ffdfgdfg
Copy link
Contributor

ffdfgdfg commented Apr 7, 2021

disconnect_timeout为什么要设置1,网络波动掉了

@sumerzhang
Copy link
Author

之前这么设置主要想让掉线时,及时发现,自动重连。那里的disconnect_time一般设置成多少比较好?有什么建议?谢谢

@peaceanddemocracy
Copy link

默认的就可以

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants