What happening with 10.5 SonarQube Developer E

I move from 10.4 to 10.5 SonarQube to run it with Java21. First when i change to 10.5, server stoped. I needed 3 days to fix it. I don’t know what happened, but it’s strat to work. Now i change certificate, and restart sonar service, and still have same issue. Sonar work, but can’t bu used on web.

Before was problem solved usning:
sudo sysctl -w vm.max_map_count=524288
sudo sysctl -w fs.file-max=131072
ulimit -n 131072
ulimit -u 8192

But now it’s not helping. Sonar, Posgres and Nginx working(systemctl status), not much on logs.
I try to delete /data/es8/, but nothing helped.

es.log

`

2024.04.24 12:28:33 INFO  es[][o.e.i.r.RecoverySettings] using rate limit [40mb] with [default=40mb, read=0b, write=0b, max=0b]
2024.04.24 12:28:33 INFO  es[][o.e.d.DiscoveryModule] using discovery type [single-node] and seed hosts providers [settings]
2024.04.24 12:28:34 INFO  es[][o.e.n.Node] initialized
2024.04.24 12:28:34 INFO  es[][o.e.n.Node] starting ...
2024.04.24 12:28:34 INFO  es[][o.e.t.TransportService] publish_address {127.0.0.1:45015}, bound_addresses {127.0.0.1:45015}
2024.04.24 12:28:34 INFO  es[][o.e.b.BootstrapChecks] explicitly enforcing bootstrap checks
2024.04.24 12:28:34 INFO  es[][o.e.c.c.ClusterBootstrapService] this node is locked into cluster UUID [oB-7vzOxRgCJ6oG28TrRCw] and will not attempt further cluster bootstrapping
2024.04.24 12:28:34 INFO  es[][o.e.c.s.MasterService] elected-as-master ([1] nodes joined in term 2)[_FINISH_ELECTION_, {sonarqube}{H4ADXzE_TmCEXD5_G1pwhw}{i0bIrURuQkWKwXs3xQ9gxw}{sonarqube}{127.0.0.1}{127.0.0.1:45015}{cdfhilmrstw}{8.11.0}{7000099-8500003} completing election], term: 2, version: 2, delta: master node changed {previous [], current [{sonarqube}{H4ADXzE_TmCEXD5_G1pwhw}{i0bIrURuQkWKwXs3xQ9gxw}{sonarqube}{127.0.0.1}{127.0.0.1:45015}{cdfhilmrstw}{8.11.0}{7000099-8500003}]}
2024.04.24 12:28:34 INFO  es[][o.e.c.s.ClusterApplierService] master node changed {previous [], current [{sonarqube}{H4ADXzE_TmCEXD5_G1pwhw}{i0bIrURuQkWKwXs3xQ9gxw}{sonarqube}{127.0.0.1}{127.0.0.1:45015}{cdfhilmrstw}{8.11.0}{7000099-8500003}]}, term: 2, version: 2, reason: Publication{term=2, version=2}
2024.04.24 12:28:34 INFO  es[][o.e.c.f.AbstractFileWatchingService] starting file watcher ...
2024.04.24 12:28:34 INFO  es[][o.e.c.f.AbstractFileWatchingService] file settings service up and running [tid=37]
2024.04.24 12:28:34 INFO  es[][o.e.c.c.NodeJoinExecutor] node-join: [{sonarqube}{H4ADXzE_TmCEXD5_G1pwhw}{i0bIrURuQkWKwXs3xQ9gxw}{sonarqube}{127.0.0.1}{127.0.0.1:45015}{cdfhilmrstw}{8.11.0}{7000099-8500003}] with reason [completing election]
2024.04.24 12:28:34 INFO  es[][o.e.h.AbstractHttpServerTransport] publish_address {127.0.0.1:9001}, bound_addresses {127.0.0.1:9001}
2024.04.24 12:28:34 INFO  es[][o.e.n.Node] started {sonarqube}{H4ADXzE_TmCEXD5_G1pwhw}{i0bIrURuQkWKwXs3xQ9gxw}{sonarqube}{127.0.0.1}{127.0.0.1:45015}{cdfhilmrstw}{8.11.0}{7000099-8500003}{xpack.installed=true, rack_id=sonarqube}

`

sonar.log


2024.04.24 12:26:10 INFO  app[][o.s.a.SchedulerImpl] Waiting for Elasticsearch to be up and running
2024.04.24 12:27:24 INFO  app[][o.s.a.SchedulerImpl] Stopping SonarQube
2024.04.24 12:27:24 INFO  app[][o.s.a.SchedulerImpl] Sonarqube has been requested to stop
2024.04.24 12:27:24 INFO  app[][o.s.a.SchedulerImpl] Stopping [Compute Engine] process...
2024.04.24 12:27:24 INFO  app[][o.s.a.SchedulerImpl] Stopping [Web Server] process...
2024.04.24 12:27:24 INFO  app[][o.s.a.SchedulerImpl] Stopping [ElasticSearch] process...
2024.04.24 12:27:24 WARN  app[][o.s.a.p.AbstractManagedProcess] Process exited with exit value [ElasticSearch]: 143
2024.04.24 12:27:24 INFO  app[][o.s.a.SchedulerImpl] Process[ElasticSearch] is stopped
2024.04.24 12:27:24 INFO  app[][o.s.a.SchedulerImpl] SonarQube is stopped
2024.04.24 12:28:18 INFO  app[][o.s.a.AppFileSystem] Cleaning or creating temp directory /opt/sonarqube/temp
2024.04.24 12:28:18 INFO  app[][o.s.a.es.EsSettings] Elasticsearch listening on [HTTP: 127.0.0.1:9001, TCP: 127.0.0.1:45015]
2024.04.24 12:28:18 INFO  app[][o.s.a.ProcessLauncherImpl] Launch process[ELASTICSEARCH] from [/opt/sonarqube/elasticsearch]: /usr/lib/jvm/java-21-openjdk-amd64/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
2024.04.24 12:28:19 INFO  app[][o.s.a.SchedulerImpl] Waiting for Elasticsearch to be up and running


nohup.log

2024.04.24 12:28:18 INFO  app[][o.s.a.AppFileSystem] Cleaning or creating temp directory /opt/sonarqube/temp
2024.04.24 12:28:18 INFO  app[][o.s.a.es.EsSettings] Elasticsearch listening on [HTTP: 127.0.0.1:9001, TCP: 127.0.0.1:45015]
2024.04.24 12:28:18 INFO  app[][o.s.a.ProcessLauncherImpl] Launch process[ELASTICSEARCH] from [/opt/sonarqube/elasticsearch]: /usr/lib/jvm/java-21-openjdk-amd64/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
2024.04.24 12:28:19 INFO  app[][o.s.a.SchedulerImpl] Waiting for Elasticsearch to be up and running
Apr 24, 2024 12:28:24 PM sun.util.locale.provider.LocaleProviderAdapter <clinit>
WARNING: COMPAT locale provider will be removed in a future release

I dont know do you need any more logs to help?

Ok, if anyone have this problem like me, it’s all right to find this.
I assume that i can run java 21 on my ubuntu instance to run sonar 10.5.

Problem was that on :Server requirements & SonarQube
java 17 is still main java for sonarqube to work.
Just take it back on jdk 17.

Still not sure how was working on java 21 for while.

Sorry if i took someones time.

1 Like

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