search

OpenShiftDemos / sonarqube-openshift-docker

An OpenShift-focused Docker build of Sonarqube
41 stars 205 forks source link

Sonarqube startup problem when redeployed for the second time #14

Open saikirandusari opened 5 years ago

saikirandusari commented 5 years ago

I have provisioned Sonarqube on OpenShift platform, the first deployment is always successful when I create using the Sonarqube template (Sonarqube and Postgres containers will spin up with no errors), only when the container restarts/when redeployed it fails with below error. Please help. Stuck for a while now.

java.lang.IllegalStateException: ClusterService was close during health call

  | at org.elasticsearch.action.admin.cluster.health.TransportClusterHealthAction$3.onClusterServiceClose(TransportClusterHealthAction.java:180)   | at org.elasticsearch.cluster.ClusterStateObserver$ContextPreservingListener.onClusterServiceClose(ClusterStateObserver.java:304)   | at org.elasticsearch.cluster.ClusterStateObserver$ObserverClusterStateListener.onClose(ClusterStateObserver.java:224)   | at org.elasticsearch.cluster.service.ClusterService.doStop(ClusterService.java:230)   | at org.elasticsearch.common.component.AbstractLifecycleComponent.stop(AbstractLifecycleComponent.java:88)   | at org.elasticsearch.node.Node.stop(Node.java:787)   | at org.elasticsearch.node.Node.close(Node.java:809)   | at org.apache.lucene.util.IOUtils.close(IOUtils.java:89)   | at org.apache.lucene.util.IOUtils.close(IOUtils.java:76)   | at org.elasticsearch.bootstrap.Bootstrap$4.run(Bootstrap.java:209)   | 2019.02.23 00:04:21 WARN app[][o.s.a.p.AbstractProcessMonitor] Process exited with exit value [es]: 143   | 2019.02.23 00:04:21 INFO app[][o.s.a.SchedulerImpl] Process [es] is stopped   | 2019.02.23 00:04:21 INFO app[][o.s.a.SchedulerImpl] SonarQube is stopped

flickerfly commented 5 years ago

Did you ever figure this out?

maxirobledo commented 11 months ago

Hi! I encountered the same problem. You have solved the problem?

flickerfly commented 11 months ago

Hi! I encountered the same problem. You have solved the problem?

Sorry, I don't remember how this was handled, but I don't see it outside OpenShift so I'm betting it has something to do with the way OpenShift handles UID. We may have just set a static idea and stepped away from the dynamic UID.

https://xkcd.com/979/

maxirobledo commented 11 months ago

Tanks for reply to me