openmptcprouter icon indicating copy to clipboard operation
openmptcprouter copied to clipboard

getpeername: Transport endpoint is not connected

Open hehh2001 opened this issue 1 year ago • 4 comments

VPS----------SERVER

OS: Ubuntu 20.04.6 LTS x86_64 Host: VMware Virtual Platform None Kernel: 5.4.207-mptcp Uptime: 1 day Packages: 829 (dpkg), 4 (snap) Shell: bash 5.0.17 CPU: Intel Xeon E7- 4830 (1) @ 2.128GHz Memory: 337MiB / 1995MiB

############################## router

Model: Raspberry Pi Compute Module 4 Rev 1.0

Architecture: ARMv8 Processor rev 3

Firmware version: openmptcprouter v0.59.1-5.4 r0+16594-ce92de8c8c

########################## Dec 15 15:23:42 zzb ss-server[914]: getpeername: Transport endpoint is not connected Dec 15 15:23:44 zzb ss-server[914]: getpeername: Transport endpoint is not connected Dec 15 15:23:46 zzb ss-server[914]: remote recv: Connection reset by peer Dec 15 15:23:51 zzb ss-server[914]: getpeername: Transport endpoint is not connected Dec 15 15:23:51 zzb ss-server[914]: remote recv: Connection reset by peer Dec 15 15:23:53 zzb ss-server[914]: getpeername: Transport endpoint is not connected Dec 15 15:23:57 zzb ss-server[914]: getpeername: Transport endpoint is not connected Dec 15 15:23:59 zzb ss-server[914]: getpeername: Transport endpoint is not connected Dec 15 15:24:01 zzb ss-server[914]: getpeername: Transport endpoint is not connected Dec 15 15:24:07 zzb ss-server[914]: getpeername: Transport endpoint is not connected Dec 15 15:24:10 zzb ss-server[914]: getpeername: Transport endpoint is not connected Dec 15 15:24:10 zzb ss-server[914]: getpeername: Transport endpoint is not connected Dec 15 15:24:11 zzb ss-server[914]: getpeername: Transport endpoint is not connected Dec 15 15:24:11 zzb ss-server[914]: getpeername: Transport endpoint is not connected Dec 15 15:24:11 zzb ss-server[914]: getpeername: Transport endpoint is not connected Dec 15 15:24:12 zzb ss-server[914]: getpeername: Transport endpoint is not connected Dec 15 15:24:13 zzb ss-server[914]: getpeername: Transport endpoint is not connected Dec 15 15:24:15 zzb ss-server[914]: getpeername: Transport endpoint is not connected Dec 15 15:24:15 zzb ss-server[914]: getpeername: Transport endpoint is not connected Dec 15 15:24:15 zzb ss-server[914]: getpeername: Transport endpoint is not connected

hehh2001 avatar Dec 15 '23 07:12 hehh2001

The aggregation router is working normally, the network is normal, and the vps reports an error! ! ! ! Thanks for your great project, I’d like to buy you a coffee

hehh2001 avatar Dec 15 '23 07:12 hehh2001

This mean a website can't be reached. Maybe an IP used in OMR-Tracker to check proxy connectivity is not answering anymore.

Edit: Seems to be 1.0.0.1 that doesn't answer anymore on port 80

Ysurac avatar Dec 15 '23 17:12 Ysurac

Getting quite a few of these too, even after 1.0.0.1 was removed from OMR-Tracker.

What is this looking for? 198.41.212.162 has a curl exit code of 0, for example, but the cloudflare page exhibits an error 1003 (Direct IP access not allowed).

Most of the others on the list give "unsatisfactory" results such as HTTP 301 (moved permanently) type hypertext, though curl still has an exit code of 0. I guess it all depends on what the tracker is looking for... any result at all that doesn't explicitly result in an process error code from the process on fetch?

The rate of the errors is rather high. This 6.-1based VPS was built from snapshot on 14 Dec.


Dec 26 07:11:36 vps ss-server[738]: getpeername: Transport endpoint is not connected Dec 26 07:11:42 vps ss-server[738]: getpeername: Transport endpoint is not connected Dec 26 07:11:42 vps ss-server[738]: getpeername: Transport endpoint is not connected Dec 26 07:11:42 vps ss-server[738]: getpeername: Transport endpoint is not connected Dec 26 07:12:09 vps ss-server[738]: server recv: Broken pipe Dec 26 07:12:13 vps ss-server[738]: server recv: Broken pipe Dec 26 07:12:25 vps ss-server[738]: getpeername: Transport endpoint is not connected Dec 26 07:12:35 vps ss-server[738]: getpeername: Transport endpoint is not connected Dec 26 07:12:35 vps ss-server[738]: server recv: Broken pipe Dec 26 07:12:58 vps ss-server[738]: getpeername: Transport endpoint is not connected Dec 26 07:12:58 vps ss-server[738]: getpeername: Transport endpoint is not connected Dec 26 07:13:06 vps ss-server[738]: server recv: Broken pipe Dec 26 07:13:08 vps ss-server[738]: getpeername: Transport endpoint is not connected Dec 26 07:13:08 vps ss-server[738]: getpeername: Transport endpoint is not connected Dec 26 07:13:08 vps ss-server[738]: getpeername: Transport endpoint is not connected Dec 26 07:13:16 vps ss-server[738]: getpeername: Transport endpoint is not connected Dec 26 07:13:16 vps ss-server[738]: getpeername: Transport endpoint is not connected Dec 26 07:13:20 vps ss-server[738]: server recv: Broken pipe Dec 26 07:13:24 vps ss-server[738]: getpeername: Transport endpoint is not connected Dec 26 07:13:37 vps ss-server[738]: server recv: Broken pipe Dec 26 07:13:41 vps ss-server[738]: getpeername: Transport endpoint is not connected Dec 26 07:13:59 vps ss-server[738]: server recv: Broken pipe Dec 26 07:14:01 vps ss-server[738]: getpeername: Transport endpoint is not connected Dec 26 07:14:01 vps ss-server[738]: getpeername: Transport endpoint is not connected Dec 26 07:14:01 vps ss-server[738]: server recv: Broken pipe Dec 26 07:14:10 vps ss-server[738]: getpeername: Transport endpoint is not connected Dec 26 07:14:10 vps ss-server[738]: getpeername: Transport endpoint is not connected Dec 26 07:14:12 vps ss-server[738]: getpeername: Transport endpoint is not connected Dec 26 07:14:12 vps ss-server[738]: getpeername: Transport endpoint is not connected Dec 26 07:14:16 vps ss-server[738]: getpeername: Transport endpoint is not connected Dec 26 07:14:36 vps ss-server[738]: getpeername: Transport endpoint is not connected Dec 26 07:14:38 vps ss-server[738]: getpeername: Transport endpoint is not connected Dec 26 07:14:51 vps ss-server[738]: getpeername: Transport endpoint is not connected Dec 26 07:15:03 vps ss-server[738]: getpeername: Transport endpoint is not connected Dec 26 07:15:03 vps ss-server[738]: server recv: Broken pipe Dec 26 07:15:05 vps ss-server[738]: server recv: Broken pipe Dec 26 07:15:09 vps ss-server[738]: getpeername: Transport endpoint is not connected Dec 26 07:15:13 vps ss-server[738]: getpeername: Transport endpoint is not connected Dec 26 07:15:15 vps ss-server[738]: server recv: Broken pipe Dec 26 07:15:17 vps ss-server[738]: getpeername: Transport endpoint is not connected Dec 26 07:15:17 vps ss-server[738]: getpeername: Transport endpoint is not connected

xzjq avatar Dec 26 '23 15:12 xzjq

@xzjq it's not directly related as the question is on 0.59.1 release using kernel 5.4 Test are done with curl -I -w %{http_code} <ip>, if the answer is not "000" then it's ok.

Ysurac avatar Dec 28 '23 09:12 Ysurac

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days

github-actions[bot] avatar Mar 27 '24 18:03 github-actions[bot]