Question: "Error on proxy: Failed to read full" error every 5 minutes
RedKage opened this issue · comments
TacticalFreak commented
Every 5 minutes I get this output on the console:
2019/10/13 17:32:08 Error on proxy: Failed to read full, 0 != 2: EOF
This occurs whether or not someone is connected to the proxy.
go-ss2 is ran like this:
go-shadowsocks2 -s 'ss://AEAD_CHACHA20_POLY1305:_STUFF_@:1234' &
I'm on a VPS Gentoo box. No root.
This error message doesn't seem to cause any issue, the proxy works fine.
So, what gives?
TacticalFreak commented
2019/10/21 12:18:53 tcp.go:101: listening TCP on :8888
2019/10/21 12:18:53 udp.go:135: listening UDP on :8888
2019/10/21 12:19:12 tcp.go:128: proxy [XXXXX]:46718 <-> [XXXXX]:443
2019/10/21 12:19:12 tcp.go:128: proxy [XXXXX]:46724 <-> [XXXXX]:8335
2019/10/21 12:19:12 tcp.go:128: proxy [XXXXX]:46730 <-> [XXXXX]:443
2019/10/21 12:19:12 tcp.go:128: proxy [XXXXX]:46712 <-> [XXXXX]:5222
2019/10/21 12:19:13 tcp.go:128: proxy [XXXXX]:46734 <-> [XXXXX]:8335
2019/10/21 12:19:13 tcp.go:128: proxy [XXXXX]:46740 <-> [XXXXX]:443
2019/10/21 12:19:14 tcp.go:128: proxy [XXXXX]:46746 <-> [XXXXX]:443
2019/10/21 12:19:17 tcp.go:128: proxy [XXXXX]:46752 <-> [XXXXX]:5228
2019/10/21 12:19:18 tcp.go:128: proxy [XXXXX]:46758 <-> [XXXXX]:443
2019/10/21 12:19:18 tcp.go:128: proxy [XXXXX]:46764 <-> [XXXXX]:443
2019/10/21 12:19:20 tcp.go:128: proxy [XXXXX]:46770 <-> [XXXXX]:443
2019/10/21 12:21:19 tcp.go:116: failed to get target address: EOF
2019/10/21 12:26:19 tcp.go:116: failed to get target address: EOF
2019/10/21 12:31:19 tcp.go:116: failed to get target address: EOF
2019/10/21 12:36:19 tcp.go:116: failed to get target address: EOF
TacticalFreak commented
OK my bad, this Error on proxy: Failed to read full, 0 != 2: EOF
was not a message from go-shadowsocks, it was an another go script I had running which was spamming my stdout.