[GH-ISSUE #2116] 运行一段时间后就会提示listener is close,到底是客户端的问题还是服务端的问题 #1683

New issue

Closed

opened 2026-05-05 13:04:37 -06:00 by gitea-mirror · 1 comment

gitea-mirror commented

2026-05-05 13:04:37 -06:00

Owner

Originally created by @DaemonWong on GitHub (Nov 27, 2020).
Original GitHub issue: https://github.com/fatedier/frp/issues/2116

020/11/28 07:10:22 [I] [proxy.go:103] [d5e782eb16efc004] [proxy_frpc_shangda] get a new work connection: [111.43.128.139:12129]
2020/11/28 07:10:22 [I] [proxy.go:103] [d5e782eb16efc004] [proxy_frpc_shangda] get a new work connection: [111.43.128.139:12129]
2020/11/28 07:10:22 [I] [proxy.go:103] [d5e782eb16efc004] [proxy_frpc_shangda] get a new work connection: [111.43.128.139:12129]
2020/11/28 07:10:22 [I] [proxy.go:103] [d5e782eb16efc004] [proxy_frpc_shangda] get a new work connection: [111.43.128.139:12129]
2020/11/28 07:10:22 [I] [proxy.go:103] [d5e782eb16efc004] [proxy_frpc_shangda] get a new work connection: [111.43.128.139:12129]
2020/11/28 07:10:22 [I] [proxy.go:103] [d5e782eb16efc004] [proxy_frpc_shangda] get a new work connection: [111.43.128.139:12129]
2020/11/28 07:10:22 [I] [proxy.go:103] [d5e782eb16efc004] [proxy_frpc_shangda] get a new work connection: [111.43.128.139:12129]
2020/11/28 07:10:22 [I] [proxy.go:103] [d5e782eb16efc004] [proxy_frpc_shangda] get a new work connection: [111.43.128.139:12129]
2020/11/28 07:10:22 [I] [proxy.go:103] [d5e782eb16efc004] [proxy_frpc_shangda] get a new work connection: [111.43.128.139:12129]
2020/11/28 07:10:22 [I] [proxy.go:103] [d5e782eb16efc004] [proxy_frpc_shangda] get a new work connection: [111.43.128.139:12129]
2020/11/28 07:10:22 [I] [proxy.go:159] [d5e782eb16efc004] [proxy_frpc_shangda] listener is closed
2020/11/28 07:10:22 [I] [proxy.go:103] [d5e782eb16efc004] [proxy_frpc_shangda] get a new work connection: [111.43.128.139:12129]
2020/11/28 07:10:22 [I] [proxy.go:103] [d5e782eb16efc004] [proxy_frpc_shangda] get a new work connection: [111.43.128.139:12129]
2020/11/28 07:10:22 [I] [proxy.go:103] [d5e782eb16efc004] [proxy_frpc_shangda] get a new work connection: [111.43.128.139:12129]
2020/11/28 07:10:22 [I] [proxy.go:103] [d5e782eb16efc004] [proxy_frpc_shangda] get a new work connection: [111.43.128.139:12129]
2020/11/28 07:10:22 [I] [proxy.go:103] [d5e782eb16efc004] [proxy_frpc_shangda] get a new work connection: [111.43.128.139:12129]
2020/11/28 07:10:22 [I] [proxy.go:103] [d5e782eb16efc004] [proxy_frpc_shangda] get a new work connection: [111.43.128.139:12129]
2020/11/28 07:10:22 [I] [proxy.go:103] [d5e782eb16efc004] [proxy_frpc_shangda] get a new work connection: [111.43.128.139:12129]
2020/11/28 07:10:22 [I] [proxy.go:103] [d5e782eb16efc004] [proxy_frpc_shangda] get a new work connection: [111.43.128.139:12129]
2020/11/28 07:10:22 [I] [proxy.go:103] [d5e782eb16efc004] [proxy_frpc_shangda] get a new work connection: [111.43.128.139:12129]
2020/11/28 07:10:22 [I] [proxy.go:103] [d5e782eb16efc004] [proxy_frpc_shangda] get a new work connection: [111.43.128.139:12129]
2020/11/28 07:10:22 [I] [proxy.go:103] [d5e782eb16efc004] [proxy_frpc_shangda] get a new work connection: [111.43.128.139:12129]

Originally created by @DaemonWong on GitHub (Nov 27, 2020). Original GitHub issue: https://github.com/fatedier/frp/issues/2116 020/11/28 07:10:22 [I] [proxy.go:103] [d5e782eb16efc004] [proxy_frpc_shangda] get a new work connection: [111.43.128.139:12129] 2020/11/28 07:10:22 [I] [proxy.go:103] [d5e782eb16efc004] [proxy_frpc_shangda] get a new work connection: [111.43.128.139:12129] 2020/11/28 07:10:22 [I] [proxy.go:103] [d5e782eb16efc004] [proxy_frpc_shangda] get a new work connection: [111.43.128.139:12129] 2020/11/28 07:10:22 [I] [proxy.go:103] [d5e782eb16efc004] [proxy_frpc_shangda] get a new work connection: [111.43.128.139:12129] 2020/11/28 07:10:22 [I] [proxy.go:103] [d5e782eb16efc004] [proxy_frpc_shangda] get a new work connection: [111.43.128.139:12129] 2020/11/28 07:10:22 [I] [proxy.go:103] [d5e782eb16efc004] [proxy_frpc_shangda] get a new work connection: [111.43.128.139:12129] 2020/11/28 07:10:22 [I] [proxy.go:103] [d5e782eb16efc004] [proxy_frpc_shangda] get a new work connection: [111.43.128.139:12129] 2020/11/28 07:10:22 [I] [proxy.go:103] [d5e782eb16efc004] [proxy_frpc_shangda] get a new work connection: [111.43.128.139:12129] 2020/11/28 07:10:22 [I] [proxy.go:103] [d5e782eb16efc004] [proxy_frpc_shangda] get a new work connection: [111.43.128.139:12129] 2020/11/28 07:10:22 [I] [proxy.go:103] [d5e782eb16efc004] [proxy_frpc_shangda] get a new work connection: [111.43.128.139:12129] 2020/11/28 07:10:22 [I] [proxy.go:159] [d5e782eb16efc004] [proxy_frpc_shangda] listener is closed 2020/11/28 07:10:22 [I] [proxy.go:103] [d5e782eb16efc004] [proxy_frpc_shangda] get a new work connection: [111.43.128.139:12129] 2020/11/28 07:10:22 [I] [proxy.go:103] [d5e782eb16efc004] [proxy_frpc_shangda] get a new work connection: [111.43.128.139:12129] 2020/11/28 07:10:22 [I] [proxy.go:103] [d5e782eb16efc004] [proxy_frpc_shangda] get a new work connection: [111.43.128.139:12129] 2020/11/28 07:10:22 [I] [proxy.go:103] [d5e782eb16efc004] [proxy_frpc_shangda] get a new work connection: [111.43.128.139:12129] 2020/11/28 07:10:22 [I] [proxy.go:103] [d5e782eb16efc004] [proxy_frpc_shangda] get a new work connection: [111.43.128.139:12129] 2020/11/28 07:10:22 [I] [proxy.go:103] [d5e782eb16efc004] [proxy_frpc_shangda] get a new work connection: [111.43.128.139:12129] 2020/11/28 07:10:22 [I] [proxy.go:103] [d5e782eb16efc004] [proxy_frpc_shangda] get a new work connection: [111.43.128.139:12129] 2020/11/28 07:10:22 [I] [proxy.go:103] [d5e782eb16efc004] [proxy_frpc_shangda] get a new work connection: [111.43.128.139:12129] 2020/11/28 07:10:22 [I] [proxy.go:103] [d5e782eb16efc004] [proxy_frpc_shangda] get a new work connection: [111.43.128.139:12129] 2020/11/28 07:10:22 [I] [proxy.go:103] [d5e782eb16efc004] [proxy_frpc_shangda] get a new work connection: [111.43.128.139:12129] 2020/11/28 07:10:22 [I] [proxy.go:103] [d5e782eb16efc004] [proxy_frpc_shangda] get a new work connection: [111.43.128.139:12129]

gitea-mirror

2026-05-05 13:04:37 -06:00

closed this issue
added the
lifecycle/stale

need-issue-template
labels

gitea-mirror commented

2026-05-05 13:04:40 -06:00

Author

Owner

@github-actions[bot] commented on GitHub (Jan 15, 2021):

Issues go stale after 45d of inactivity. Stale issues rot after an additional 10d of inactivity and eventually close.

@github-actions[bot] commented on GitHub (Jan 15, 2021): Issues go stale after 45d of inactivity. Stale issues rot after an additional 10d of inactivity and eventually close.