Sonarqube 2025 LTA Developer image not working with elasticsearch

Hello, I recently upgraded Sonarqube to the 2025 Developer LTA release. The upgrade was successful. Later, I restarted the containers because I changed the database credentials but the Sonarqube containers kept crashing. I have reverted to the old database credentials but it is still not working. I deployed SonarQube using docker-compose.

I have tried deleting all the volumes, restarting the containers, and deploying to a fresh server, but none have worked. I have added a copy of the logs below

2025.02.23 18:01:05 INFO  app[][o.s.a.es.EsSettings] Elasticsearch listening on [HTTP: 127.0.0.1:9001, TCP: 127.0.0.1:{}]
2025.02.23 18:01:05 INFO  app[][o.s.a.ProcessLauncherImpl] Launch process[ELASTICSEARCH] from [/opt/sonarqube/elasticsearch]: /opt/java/openjdk/bin/java -Xms4m -Xmx64m -XX:+UseSerialGC -Dcli.name=server -Dcli.script=./bin/elasticsearch -Dcli.libs=lib/tools/server-cli -Des.path.home=/opt/sonarqube/elasticsearch -Des.path.conf=/opt/sonarqube/temp/conf/es -Des.distribution.type=tar -cp /opt/sonarqube/elasticsearch/lib/*:/opt/sonarqube/elasticsearch/lib/cli-launcher/* org.elasticsearch.launcher.CliToolLauncher
2025.02.23 18:01:05 INFO  app[][o.s.a.SchedulerImpl] Waiting for Elasticsearch to be up and running
Standard Commons Logging discovery in action with spring-jcl: please remove commons-logging.jar from classpath in order to avoid potential conflicts
java.nio.file.NoSuchFileException: /opt/sonarqube/temp/conf/es/elasticsearch.keystore.tmp
        at java.base/sun.nio.fs.UnixException.translateToIOException(Unknown Source)
        at java.base/sun.nio.fs.UnixException.rethrowAsIOException(Unknown Source)
        at java.base/sun.nio.fs.UnixException.rethrowAsIOException(Unknown Source)
        at java.base/sun.nio.fs.UnixFileAttributeViews$Posix.readAttributes(Unknown Source)
        at java.base/sun.nio.fs.UnixFileAttributeViews$Posix.readAttributes(Unknown Source)
        at java.base/sun.nio.fs.FileOwnerAttributeViewImpl.getOwner(Unknown Source)
        at java.base/java.nio.file.Files.getOwner(Unknown Source)
        at org.elasticsearch.common.settings.KeyStoreWrapper.save(KeyStoreWrapper.java:495)
        at org.elasticsearch.common.settings.KeyStoreWrapper.save(KeyStoreWrapper.java:434)
        at org.elasticsearch.common.settings.KeyStoreWrapper.bootstrap(KeyStoreWrapper.java:234)
        at org.elasticsearch.server.cli.KeyStoreLoader.bootstrap(KeyStoreLoader.java:38)
        at org.elasticsearch.server.cli.ServerCli.execute(ServerCli.java:93)
        at org.elasticsearch.common.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:55)
        at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:95)
        at org.elasticsearch.cli.Command.main(Command.java:52)
        at org.elasticsearch.launcher.CliToolLauncher.main(CliToolLauncher.java:65)
2025.02.23 18:01:25 WARN  app[][o.s.a.p.AbstractManagedProcess] Process exited with exit value [ElasticSearch]: 74
2025.02.23 18:01:25 INFO  app[][o.s.a.SchedulerImpl] Process[ElasticSearch] is stopped
2025.02.23 18:01:25 INFO  app[][o.s.a.SchedulerImpl] SonarQube is stopped

Hi,

Welcome to the community!

What do your other server logs, in particular es.log, say?

 
Ann

1 Like

I checked the web.log and found the root cause to be a database configuration issue. I fixed it, and everything is working fine now. Thank you very much.

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.