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
如果alist崩溃或者异常停止后,在界面无法启动,之前方法是只能通过重启解决,在手动命令启动后,发现报错; failed to listen unix: listen unix /var/run/alist.sock: bind: address already in use 推测是这个文件导致锁定无法确定, 随后删除这个文件rm -rf /var/run/alist.sock 顺利解决。成功无重启通过luci界面启动 推测是异常崩溃没删除这个文件,导致二次启动锁定有问题,没日志提示,所以无法定位问题
failed to listen unix: listen unix /var/run/alist.sock: bind: address already in use
rm -rf /var/run/alist.sock
The text was updated successfully, but these errors were encountered:
测试可行,我这边断电后就锁定了
Sorry, something went wrong.
No branches or pull requests
如果alist崩溃或者异常停止后,在界面无法启动,之前方法是只能通过重启解决,在手动命令启动后,发现报错;
failed to listen unix: listen unix /var/run/alist.sock: bind: address already in use
推测是这个文件导致锁定无法确定,
随后删除这个文件
rm -rf /var/run/alist.sock
顺利解决。成功无重启通过luci界面启动
推测是异常崩溃没删除这个文件,导致二次启动锁定有问题,没日志提示,所以无法定位问题
The text was updated successfully, but these errors were encountered: