New issue
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
最新版本alist重启时有很大概率无法启动,提示s3服务端口冲突 #6391
Comments
Thanks for opening your first issue here! Be sure to follow the issue template! |
config.json配置文件有3个端口,如果你有多个alist服务的话可以把这3个端口的端口号改一下就可正常启动 |
我只有1个alist服务。 |
只是s3服务端口冲突 "s3": { 这段配置文件不能删,删了还会自动加回来,只能改端口。 |
很难理解这是在干嘛 |
开发版已经修复了 |
我也是自动化流水 每天自动重新部署alist,确保自动拉取最新版本和相关自定义脚本 |
fixed in 3.34.0 |
Please make sure of the following things
I have read the documentation.
我已经阅读了文档。
I'm sure there are no duplicate issues or discussions.
我确定没有重复的issue或讨论。
I'm sure it's due to
AList
and not something else(such as Network ,Dependencies
orOperational
).我确定是
AList
的问题,而不是其他原因(例如网络,依赖
或操作
)。I'm sure this issue is not fixed in the latest version.
我确定这个问题在最新版本中没有被修复。
AList Version / AList 版本
3.33.0
Driver used / 使用的存储驱动
/
Describe the bug / 问题描述
平时使用通过AList Desktop管理alist,最近发现不论是使用软件自带的定时重启,还是人工点击重启,都有很大概率无法启动,具体报错如下:
FATA[2024-04-24 23:07:26] failed to start http: listen tcp 0.0.0.0:5246: bind: Only one usage of each socket address (protocol/network address/port) is normally permitted.
我尝试解决:
1确认主机并没有其他程序监听5246端口
2尝试更换过默认的5246端口,依然无效
3重启操作并非每次都无法启动,多重启几次可能有概率就能起来
4日志文件没有异常
配置文件没有做过改动,通过AList Desktop配置每天0点自动重启一次alist,早期版本没发现这个问题,最近每天早晨都有概率出现服务已停止,故判断是最新版本才出现。
希望可以得到确认回复,非常感谢。
Reproduction / 复现链接
/
Config / 配置
/
Logs / 日志
The text was updated successfully, but these errors were encountered: