mirror of
https://github.com/fatedier/frp.git
synced 2026-05-15 08:05:49 -06:00
[GH-ISSUE #658] 多次重启 frpc 后出现 start error: custom listener for [cc.1] is repeated #514
Labels
No labels
In Progress
WIP
WaitingForInfo
bug
doc
duplicate
easy
enhancement
future
help wanted
invalid
lifecycle/stale
need-issue-template
need-usage-help
no plan
proposal
pull-request
question
todo
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/frp#514
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Hirozy on GitHub (Mar 8, 2018).
Original GitHub issue: https://github.com/fatedier/frp/issues/658
Issue is only used for submiting bug report and documents typo. If there are same issues or answers can be found in documents, we will close it directly.
(为了节约时间,提高处理问题的效率,不按照格式填写的 issue 将会直接关闭。)
Use the commands below to provide key information from your environment:
You do NOT have to include this information if this is a FEATURE REQUEST
What version of frp are you using (./frpc -v or ./frps -v)?
0.16.0
What operating system and processor architecture are you using (
go env)?Linux and macOS
Configures you used:
Server
Client on Linux
Client on macOS
Steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Error on Server
Error on Client on Linux
Describe the results you expected:
Additional information you deem important (e.g. issue happens only occasionally):
简单测试了一下 0.15.1 ,没有上述问题
Can you point out what caused this issue (optional)
@fatedier commented on GitHub (Mar 14, 2018):
本地没有复现。
服务端日志里停止服务的顺序应该是:
之后重新启动服务的日志顺序:
可以抓一下这部分完整的日志,主要是服务端程序,从停止到重启的这部分,检查一下和我列的顺序有没有什么不同,然后贴出来。理论上这个 proxy 会被 close,之后就可以被重新注册了。
@Hirozy commented on GitHub (Mar 19, 2018):
感谢回答,不好意思,本地同样没能再次复现,推测当时运行的环境有关。下面是当时的完整日志,再次表示感谢!
下面是从服务端开启时的日志
@fatedier commented on GitHub (Mar 20, 2018):
从服务端的日志来看,是前一个 frpc 还没有关闭的情况下,就启动了新的 frpc,至于原因不是很清楚。重启时最好等前一个进程完全退出后,再启动新的。
@Hirozy commented on GitHub (Mar 20, 2018):
我大概也猜到这点了,手动给 frp 的 restart 加了几秒的延时,暂时没发现问题。
PS: 我这里不能复现,应当就是因为在 restart 上加了延时
@fatedier commented on GitHub (Mar 20, 2018):
这个和你加延时应该关系不大,可以看 facc31e74000562d 这个 runId 对应的日志,这个是最先连接上来的 client,到最后都没有它关闭的相关日志,这里可能存在着某种特殊情况,导致你当时没有正常关闭那个进程?
@Hirozy commented on GitHub (Mar 20, 2018):
我这里总使用了三个 Client,
A, B, C,其中一个A配置全为 visitor,用来连接B, C,并且A一直保持连接 ,是这个特殊情况?@fatedier commented on GitHub (Mar 20, 2018):
没法猜测,如果暂时没有问题, 就不细究了,等能复现的时候再排查下原因。
@Geker commented on GitHub (Jul 17, 2018):
你是不是使用kcp了。我注释掉kcp协议,貌似没这个问题了