We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
在一台主机上启用多个redis-shake时,第一个启动成功,后面的提示6479端口被占用。
如果有错误日志或其他相关日志,请在这里提供。
2024-03-05 17:07:11 INF not set pprof port 2024-03-05 17:07:11 INF no function script 2024-03-05 17:07:11 INF create SyncStandaloneReader: 10.10.1.2:32181 2024-03-05 17:07:11 INF create RedisStandaloneWriter: 10.10.1.248:6379 2024-03-05 17:07:11 INF status information: http://localhost:6479 2024-03-05 17:07:11 INF status information: watch -n 0.3 'curl -s http://localhost:6479 | python -m json.tool' 2024-03-05 17:07:11 INF start syncing... 2024-03-05 17:07:11 ERR listen tcp :6479: bind: address already in use RedisShake/internal/status/handler.go:46 -> setStatusPort.func1() runtime/asm_amd64.s:1598 -> goexit()
The text was updated successfully, but these errors were encountered:
status_port 配置改成 0
Sorry, something went wrong.
谢谢,从代码里看到了,改成非6479就行了。
No branches or pull requests
问题描述(Issue Description)
在一台主机上启用多个redis-shake时,第一个启动成功,后面的提示6479端口被占用。
环境信息(Environment)
日志信息(Logs)
如果有错误日志或其他相关日志,请在这里提供。
2024-03-05 17:07:11 INF not set pprof port
2024-03-05 17:07:11 INF no function script
2024-03-05 17:07:11 INF create SyncStandaloneReader: 10.10.1.2:32181
2024-03-05 17:07:11 INF create RedisStandaloneWriter: 10.10.1.248:6379
2024-03-05 17:07:11 INF status information: http://localhost:6479
2024-03-05 17:07:11 INF status information: watch -n 0.3 'curl -s http://localhost:6479 | python -m json.tool'
2024-03-05 17:07:11 INF start syncing...
2024-03-05 17:07:11 ERR listen tcp :6479: bind: address already in use
RedisShake/internal/status/handler.go:46 -> setStatusPort.func1()
runtime/asm_amd64.s:1598 -> goexit()
The text was updated successfully, but these errors were encountered: