-
Notifications
You must be signed in to change notification settings - Fork 385
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
快速安装完整版本,安装失败 #235
Comments
错误日志:kubectl logs sreworks-appmanager-cluster-initjob-xf829 -n sreworks
The above exception was the direct cause of the following exception: Traceback (most recent call last): The above exception was the direct cause of the following exception: Traceback (most recent call last): During handling of the above exception, another exception occurred: Traceback (most recent call last): |
关键点在 sreworks-mysql-0 和 sreworks-redis-master-0 没有正常启动 |
导致其他pod没法正常运行。 |
从当前截图看已经mysql已经重启两次了,是否当前资源(比如内存),不是很充分,导致OOM反复重启?继而依赖mysql的服务都没法正常工作。 |
虚拟机我给的26g内存 |
是否要搭建私有docker仓库才能起来呢 |
私有docker仓库不是必要条件。快速安装流程中,已经把所有镜像预置到公网可访问的docker镜像路径中。 |
用kubectl describe 看一下mysql的最近几次重启的原因。 |
https://www.yuque.com/sreworks-doc/docs/rr5g10 |
[root@smu1 sreworks-chart]# kubectl describe pod sreworks-mysql-0 -n sreworks Normal Scheduled 23h default-scheduler Successfully assigned sreworks/sreworks-mysql-0 to minikube |
你的集群挂载的存储卷可能出现了兼容问题。可以尝试取消mysql的data磁盘挂载测试。 |
我执行的该命令,我的版本是centos8.6
helm install sreworks ./ --create-namespace --namespace sreworks --set global.accessMode="nodePort" --set appmanager.home.url="http://127.0.0.1:30767" --set appmanager.server.jwtSecretKey="123321"
The text was updated successfully, but these errors were encountered: