我在AWS EKS上运行Sonarqube 6.7作为部署,1个副本由RDS数据库支持,EFS用于持久卷。
当我编辑部署文件以使副本计数为2时,新的pod正在进入CrashLoopBackOff。
让我知道你需要什么信息,我很乐意提供。
CrashLoopBackOff Pod日志:
2019.01.21 06:20:15 INFO app[][o.s.a.AppFileSystem] Cleaning or creating temp directory /opt/sonarqube/temp
2019.01.21 06:20:15 INFO app[][o.s.a.es.EsSettings] Elasticsearch listening on /127.0.0.1:9001
2019.01.21 06:20:15 INFO app[][o.s.a.p.ProcessLauncherImpl] Launch process[[key='es', ipcIndex=1, logFilenamePrefix=es]] from [/opt/sonarqube/elasticsearch]: /opt/sonarqube/elasticsearch/bin/elasticsearch -Epath.conf=/opt/sonarqube/temp/conf/es
2019.01.21 06:20:15 INFO app[][o.s.a.SchedulerImpl] Waiting for Elasticsearch to be up and running
2019.01.21 06:20:17 INFO app[][o.e.p.PluginsService] no modules loaded
2019.01.21 06:20:17 INFO app[][o.e.p.PluginsService] loaded plugin [org.elasticsearch.transport.Netty4Plugin]
2019.01.21 06:20:22 WARN app[][o.s.a.p.AbstractProcessMonitor] Process exited with exit value [es]: 1
2019.01.21 06:20:22 INFO app[][o.s.a.SchedulerImpl] Process [es] is stopped
2019.01.21 06:20:22 INFO app[][o.s.a.SchedulerImpl] SonarQube is stopped发布于 2019-01-31 16:16:55
我得到了同样的错误,并通过在spec.template.spec中的部署yaml中添加以下内容来解决
securityContext: fsGroup: 999
https://stackoverflow.com/questions/54305479
复制相似问题