Sonarqube 7.9.1 refuses to start

Hi all,

The previous version of Sonarqube was 6.7.7 LTS, so i upgraded to 7.9.1 LTS. I installed a new JDK

    > java version "11.0.4" 2019-07-16 LTS
    > Java(TM) SE Runtime Environment 18.9 (build 11.0.4+10-LTS)
    > Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.4+10-LTS, mixed mode)
    > ```

but still Sonarqube stopped. This is a snippet of the sonar.log

   >      2019.08.01 14:50:19 INFO  app[][o.s.a.AppFileSystem] Cleaning or creating                   temp directory /data/sonarqube/sonarqube-7.9.1/temp
>         2019.08.01 14:50:19 INFO  app[][o.s.a.es.EsSettings] Elasticsearch listening on /127.0.0.1:9001
    >         2019.08.01 14:50:19 INFO  app[][o.s.a.ProcessLauncherImpl] Launch process[[key='es', ipcIndex=1, logFilenamePrefix=es]] from [/data/sonarqube/sonarqube-7.9.1/elasticsearch]: /data/sonarqube/sonarqube-````7.9.1/elasticsearch/bin/elasticsearch
    >         2019.08.01 14:50:19 INFO  app[][o.s.a.SchedulerImpl] Waiting for Elasticsearch to be up and running
>     Java HotSpot(TM) 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release.
>         2019.08.01 14:50:20 INFO  app[][o.e.p.PluginsService] no modules loaded
>         2019.08.01 14:50:20 INFO  app[][o.e.p.PluginsService] loaded plugin [org.elasticsearch.transport.Netty4Plugin]
>         2019.08.01 14:50:22 WARN  app[][o.s.a.p.AbstractManagedProcess] Process exited with exit value [es]: 1
>         2019.08.01 14:50:22 INFO  app[][o.s.a.SchedulerImpl] Process[es] is stopped
>         2019.08.01 14:50:22 INFO  app[][o.s.a.SchedulerImpl] SonarQube is stopped
>         2019.08.01 14:50:22 INFO  app[][o.e.c.t.TransportClientNodesService] failed to get node info for {#transport#-1}{GK1cYpSNTM-eycINcVQsOA}{127.0.0.1}{127.0.0.1:9001}, disconnecting...
>     java.lang.IllegalStateException: Future got interrupted

and a snippet of es.log

> 2019.08.01 14:50:22 ERROR es[][o.e.b.Bootstrap] Exception
> java.lang.RuntimeException: can not run elasticsearch as root
>         at org.elasticsearch.bootstrap.Bootstrap.initializeNatives(Bootstrap.java:103) ~[elasticsearch-6.8.0.jar:6.8.0]
>         at org.elasticsearch.bootstrap.Bootstrap.setup(Bootstrap.java:170) ~[elasticsearch-6.8.0.jar:6.8.0]
>         at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:333) [elasticsearch-6.8.0.jar:6.8.0]
>         at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:159) [elasticsearch-6.8.0.jar:6.8.0]
>         at org.elasticsearch.bootstrap.Elasticsearch.execute(Elasticsearch.java:150) [elasticsearch-6.8.0.jar:6.8.0]
>         at org.elasticsearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:86) [elasticsearch-6.8.0.jar:6.8.0]
>         at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:124) [elasticsearch-cli-6.8.0.jar:6.8.0]
>         at org.elasticsearch.cli.Command.main(Command.java:90) [elasticsearch-cli-6.8.0.jar:6.8.0]
>         at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:116) [elasticsearch-6.8.0.jar:6.8.0]
>         at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:93) [elasticsearch-6.8.0.jar:6.8.0]

of course i start Sonarqube with a non-root user. That’s why i don’t understand the error in es.log

I can’t find the solution at all. Please, can you help me?

With kind regards, William

Hi William,

How exactly are you starting SonarQube? As a service? With a script? Manually as yourself?

 
Ann

Hi Ann, with a script located in /etc/init.d, but i start Sonarqube manually in the bin directory (sonar.sh) i got the same error

Hi William,

This message is being passed through from Elasticsearch, which somehow detects that it is being run by root. I’m sorry, but I don’t have much additional advice for you except perhaps to make sure the users in question aren’t in the root group.

 
Ann

Hi William,

Output of a following command should allow you to see which user is actually used

sonarqube-7.9.1/bin/linux-x86-64/sonar.sh start && sleep 2s && ps aux | grep "org.elasticsearch.bootstrap.Elasticsearch"

here is example from my machine

evgeny.mandrikov 25529 268.1  1.9  8008824 647488   ??  R     7:17PM   0:01.49 /Users/evgeny.mandrikov/.java-select/versions/jdk-11.0.3_osx-x64_bin/bin/java -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly -Des.networkaddress.cache.ttl=60 -Des.networkaddress.cache.negative.ttl=10 -XX:+AlwaysPreTouch -Xss1m -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djna.nosys=true -XX:-OmitStackTraceInFastThrow -Dio.netty.noUnsafe=true -Dio.netty.noKeySetOptimization=true -Dio.netty.recycler.maxCapacityPerThread=0 -Dlog4j.shutdownHookEnabled=false -Dlog4j2.disable.jmx=true -Djava.io.tmpdir=/private/tmp/sonarqube-7.9.1/temp -XX:ErrorFile=../logs/es_hs_err_pid%p.log -Xms512m -Xmx512m -XX:+HeapDumpOnOutOfMemoryError -Des.path.home=/private/tmp/sonarqube-7.9.1/elasticsearch -Des.path.conf=/private/tmp/sonarqube-7.9.1/temp/conf/es -Des.distribution.flavor=default -Des.distribution.type=tar -cp /private/tmp/sonarqube-7.9.1/elasticsearch/lib/* org.elasticsearch.bootstrap.Elasticsearch
evgeny.mandrikov 25545   0.0  0.0  4268016    644 s001  R+    7:17PM   0:00.00 grep --colour=auto org.elasticsearch.bootstrap.Elasticsearch

showing that java process for Elasticsearch is using user evgeny.mandrikov

and command whoami shows that this is my current user

User having id 0 is the “root”, however output of command id -u evgeny.mandrikov shows 502 - this user is not “root”.

What is the output of the above three commands for you?

Hi Evgeny,

this is my output:

root      3866 87.0 10.1 3029004 610880 ?      Sl   17:26   0:00 /usr/java/jdk-11.0.4/bin/java -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly -Des.networkaddress.cache.ttl=60 -Des.networkaddress.cache.negative.ttl=10 -XX:+AlwaysPreTouch -Xss1m -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djna.nosys=true -XX:-OmitStackTraceInFastThrow -Dio.netty.noUnsafe=true -Dio.netty.noKeySetOptimization=true -Dio.netty.recycler.maxCapacityPerThread=0 -Dlog4j.shutdownHookEnabled=false -Dlog4j2.disable.jmx=true -Djava.io.tmpdir=/data/sonarqube/sonarqube-7.9.1/temp -XX:ErrorFile=../logs/es_hs_err_pid%p.log -Des.enforce.bootstrap.checks=true -Xms512m -Xmx512m -XX:+HeapDumpOnOutOfMemoryError -Des.path.home=/data/sonarqube/sonarqube-7.9.1/elasticsearch -Des.path.conf=/data/sonarqube/sonarqube-7.9.1/temp/conf/es -Des.distribution.flavor=default -Des.distribution.type=tar -cp /data/sonarqube/sonarqube-7.9.1/elasticsearch/lib/* org.elasticsearch.bootstrap.Elasticsearch
root      3937  0.0  0.0 103320   872 pts/0    S+   17:26   0:00 grep org.elasticsearch.bootstrap.Elasticsearch

It seems that java proces is using root. Correct?

Btw, everything does have user sonar

drwxr-xr-x 6 sonar sonar 4096 Jul 10 12:21 bin
drwxr-xr-x 2 sonar sonar 4096 Aug  7 17:53 conf
-rw-r--r-- 1 sonar sonar 7651 Jul 10 12:21 COPYING
drwxr-xr-x 2 sonar sonar 4096 Jul 10 12:21 data
drwxr-xr-x 7 sonar sonar 4096 Aug  1 14:04 elasticsearch
drwxr-xr-x 4 sonar sonar 4096 Jul 10 12:21 extensions
drwxr-xr-x 6 sonar sonar 4096 Jul 10 12:32 lib
drwxr-xr-x 2 sonar sonar 4096 Aug  7 17:31 logs
drwxr-xr-x 4 sonar sonar 4096 Aug  7 18:00 temp
drwxr-xr-x 7 sonar sonar 4096 Jul 10 12:33 web

Yes.


And to be sure that

What is the output of command whoami ?


Also please provide output of following two commands

sha256sum sonarqube-7.9.1/bin/linux-x86-64/sonar.sh
cat sonarqube-7.9.1/bin/linux-x86-64/sonar.sh | grep "RUN_AS_USER"

Hi Evgeny,

Of course i am root (whoami), but user sonar is owner of Sonarqube.

This is the output:

ae7648f7ef21d4f5cc691e7457c70394d1a01c8588356c3853c3eafeef7c74d2 /data/sonarqube/sonarqube-7.9.1/bin/linux-x86-64/sonar.sh

and

#RUN_AS_USER=
if [ “X$RUN_AS_USER” != “X” ]
if [ “$IDEXE -u -n” = “$RUN_AS_USER” ]
RUN_AS_USER=“”
if [ “X$RUN_AS_USER” != “X” ]
# If LOCKPROP and $RUN_AS_USER are defined then the new user will most likely not be
RUN_AS_GROUP=groups $RUN_AS_USER | awk '{print $3}' | tail -1
RUN_AS_GROUP=$RUN_AS_USER
chown $RUN_AS_USER:$RUN_AS_GROUP $LOCKFILE
su -m $RUN_AS_USER -c “"$REALPATH" $2”

I really hope this is ok for you.

Kind regards

:tada:

Doesn’t matter who owns files - process is executed by the user that launches/starts this process.

And so it is expected to see can not run elasticsearch as root - here is the same on my machine:

# ls -lAh sonarqube-7.9.1
total 8.0K
-rw-r--r--  1 evgeny.mandrikov wheel 7.5K Jul 10 12:21 COPYING
drwxr-xr-x  6 evgeny.mandrikov wheel  192 Jul 10 12:21 bin
drwxr-xr-x  4 evgeny.mandrikov wheel  128 Jul 10 12:21 conf
drwxr-xr-x  3 evgeny.mandrikov wheel   96 Jul 10 12:21 data
drwxr-xr-x 10 evgeny.mandrikov wheel  320 Jul 10 12:21 elasticsearch
drwxr-xr-x  4 evgeny.mandrikov wheel  128 Jul 10 12:21 extensions
drwxr-xr-x  8 evgeny.mandrikov wheel  256 Jul 10 12:32 lib
drwxr-xr-x  3 evgeny.mandrikov wheel   96 Jul 10 12:21 logs
drwxr-xr-x  3 evgeny.mandrikov wheel   96 Jul 10 12:21 temp
drwxr-xr-x 23 evgeny.mandrikov wheel  736 Jul 10 12:33 web

# ls -lah sonarqube-7.9.1/bin/linux-x86-64/
total 132K
drwxr-xr-x 5 evgeny.mandrikov wheel  160 Jul 10 12:21 .
drwxr-xr-x 6 evgeny.mandrikov wheel  192 Jul 10 12:21 ..
drwxr-xr-x 3 evgeny.mandrikov wheel   96 Jul 10 12:21 lib
-rwxr-xr-x 1 evgeny.mandrikov wheel  17K Jul 10 12:21 sonar.sh
-rwxr-xr-x 1 evgeny.mandrikov wheel 109K Jul 10 12:21 wrapper

# sudo su root

# whoami
root

# sonarqube-7.9.1/bin/linux-x86-64/sonar.sh start

# cat sonarqube-7.9.1/logs/es.log
2019.08.08 12:37:17 ERROR es[][o.e.b.Bootstrap] Exception
java.lang.RuntimeException: can not run elasticsearch as root

So now I’m pretty sure that
if you switch to sonar user using command su sonar
then execution of sonarqube-7.9.1/bin/linux-x86-64/sonar.sh start will not show message can not run elasticsearch as root


sonarqube-7.9.1/bin/linux-x86-64/sonar.sh can do su sonar for you before starting java, but for this you must change in it

#RUN_AS_USER=

on

RUN_AS_USER=sonar
2 Likes

Hi Evgeny,

The fact that the owner of the file nothing has to do with the executor of the process…i didn’t know. Now i know :wink: thank you.

I think it makes perfect sense you told me, but when i changed in the sonar.sh script RUN_AS_USER=sonar sonarqube wont’t start at all. It stops immediately.

What’s next step?

Kind regards

Could you please be more specific - what exactly you did after changing RUN_AS_USER and execution of sonarqube-7.9.1/bin/linux-x86-64/sonar.sh start ? One can only hope that you actually checked the logs, are you? And nothing at all was written into logs about this start?

Why so can happen? Let me guess again - before you was using root, so at least log files were created by root and now owned by root. Now you use sonar user and it can not write to files owned by root, i.e. can not even write logs. Makes sense?

Use following command to check owner of log files:

ls -lAh sonarqube-7.9.1/logs/

Use following command to check owner of all files:

find sonarqube-7.9.1 -type d -exec ls -lAh \{\} \;

Use following command to change owner of all files:

chown -R sonar:sonar sonarqube-7.9.1

Or you can even consider to redo installation/upgrade procedure from the beginning by unpacking into absolutely fresh/new directory and by immediately changing RUN_AS_USER before start.

Hi Evgeny,

After i changed RUN_AS_USER i checked the logfiles. Your guess was absolutely right. The log files were last described during the previous start. It made sense you told me. In fact, yesterday i checked the logfiles as user is sonar, but i also went to root as owner and checked the logfiles if they were described, but the logfiles there were still untouched.That’s what i mean with ‘stopped immediately’.
Tomorrow or sunday i will be able to check this again like you told me.
Before i asked this question i reinstalled/upgraded Sonarqube 7.9.1… Maybe its a consideration to install Sonarqube 7.9.1 and JDK11.x on a new and clean system with RedHat.:frowning:

When i tried and checked this all again and checked it like you told me, you’ll will see me again. For now i wish you have a nice weekend.

With kind regards, William

Hi Evgeny,

When i started Sonarqube after i changed RUN_AS_USER nothinh was written in the logfiles 9with the owner root). I removed the logfiles and i started Sonarqube again and what i expected was right…the logfiles were present again (but now with the owner ‘sonar’).
Unfortunately Sonarqube stopped again. In the new es.log appears the error that seccomp is unavailable: CONFIG_SECCOMP not compiled into kernel. I set the bootstrap.system_call_filter to false, but that didn’t succeed. At that time i decided to request a new virtual with the latest kernel and installed with Red Hat 8. On that brand new system i install Sonarqube 7.9.1 with JDK11.x
Thank you very much for your help. You helped me a lot.

With kind regards, William

CONFIG_SECCOMP is mentioned in documentation - https://docs.sonarqube.org/7.9/requirements/requirements/

But anyway thank you for sharing your experience, hope this will be useful for further readers in addition to everything else in this thread. And very glad to hear that your problems were resolved.

I am too facing issue in starting Sonarqube 7.9.1 community edition.

I am using ubuntu LTS 18.04 operatig system and PostgreSQL 11.6 database.

Below are the steps i followed:

Already have postgresql database running in my machine:

  1. Switch to the postgres user.
    su - postgres

  2. Create a new user by typing:
    createuser sonarqube

  3. Switch to the PostgreSQL shell.
    psql

  4. Set a password for the newly created user for SonarQube database.
    ALTER USER sonarqube WITH ENCRYPTED password ‘some_secure_password’;

  5. Create a new database for PostgreSQL database by running:
    CREATE DATABASE sonarqube OWNER sonarqube;

  6. Exit from the psql shell:
    \q

  7. Switch back to the sudo user by running the exit command.
    exit

Sonarqube Installation:

  1. Downloaded sonarqube 7.9.1 community edition from:
    https://binaries.sonarsource.com/Distribution/sonarqube/sonarqube-7.9.1.zip

  2. Extracted the zip file.

  3. Moved all the contents inside the extracted folder sonarqube-7.9.1, to /opt/sonarqube

  4. create the sonarqube user:
    sudo adduser --system --no-create-home --group --disabled-login sonarqube

  5. Finally, update the permissions so that the sonarqube user will own these files, and be able to read and write files in this directory:
    sudo chown -R sonarqube:sonarqube /opt/sonarqube

  6. sudo nano /sonarqube/conf/sonar.properties
    sonar.jdbc.username=sonarqube
    sonar.jdbc.password=some_secure_password
    sonar.jdbc.url=jdbc:postgresql://localhost/sonarqube
    sonar.web.javaAdditionalOpts=-server

Configure Systemd service:

  1. sudo nano /etc/systemd/system/sonarqube.service

  2. Included below scripts

[Unit]
Description=SonarQube service
After=syslog.target network.target

[Service]
Type=simple
User=sonarqube
Group=sonarqube
PermissionsStartOnly=true

ExecStart=/opt/sonarqube/bin/linux-x86-64/sonar.sh start
ExecStop=/opt/sonarqube/bin/linux-x86-64/sonar.sh stop

StandardOutput=syslog
LimitNOFILE=65536
LimitNPROC=8192
TimeoutStartSec=5
Restart=always
SuccessExitStatus=143

[Install]
WantedBy=multi-user.target
  1. Start the application by running:

    sudo systemctl start sonarqube

  2. Enable the SonarQube service to automatically start at boot time.

    sudo systemctl enable sonarqube

  3. To check if the service is running, run:

   sudo systemctl status sonarqube

sonarqube.service - SonarQube service
   Loaded: loaded (/etc/systemd/system/sonarqube.service; enabled; vendor preset: enabled)
   Active: deactivating (stop-sigterm) (Result: exit-code) since Sat 2019-11-16 21:08:12 IST; 1s ago
  Process: 20140 ExecStop=/opt/sonarqube/bin/linux-x86-64/sonar.sh stop (code=exited, status=1/FAILURE)
  Process: 20058 ExecStart=/opt/sonarqube/bin/linux-x86-64/sonar.sh start (code=exited, status=0/SUCCESS)
 Main PID: 20058 (code=exited, status=0/SUCCESS)
    Tasks: 49 (limit: 4915)
   CGroup: /system.slice/sonarqube.service
           ├─20108 /opt/sonarqube/bin/linux-x86-64/./wrapper /opt/sonarqube/bin/linux-x86-64/../../conf/wrapper.conf wrapper.syslog.ident=SonarQube wrapper.pidfile=/opt/sonarqube/bin/linux-x86-64/./SonarQube.pid
           ├─20110 java -Dsonar.wrapped=true -Djava.awt.headless=true -Xms8m -Xmx32m -Djava.library.path=./lib -classpath ../../lib/jsw/wrapper-3.2.3.jar:../../lib/common/jackson-dataformat-smile-2.8.11.jar:../.
           └─20208 /usr/lib/jvm/java-11-openjdk-amd64/bin/java -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly -Des.networkaddress.cache.ttl=60 -Des.networkaddres
Nov 16 21:08:11 yuvarajvelmurugan-B250M-D3H systemd[1]: Started SonarQube service.
Nov 16 21:08:11 yuvarajvelmurugan-B250M-D3H sonar.sh[20058]: Starting SonarQube...
Nov 16 21:08:12 yuvarajvelmurugan-B250M-D3H sonar.sh[20058]: Started SonarQube.
Nov 16 21:08:12 yuvarajvelmurugan-B250M-D3H su[20188]: Successful su for sonarqube by root
Nov 16 21:08:12 yuvarajvelmurugan-B250M-D3H su[20188]: + ??? root:sonarqube
Nov 16 21:08:12 yuvarajvelmurugan-B250M-D3H su[20188]: pam_unix(su:session): session opened for user sonarqube by (uid=0)
Nov 16 21:08:12 yuvarajvelmurugan-B250M-D3H su[20188]: pam_unix(su:session): session closed for user sonarqube
Nov 16 21:08:12 yuvarajvelmurugan-B250M-D3H sonar.sh[20140]: This account is currently not available.
Nov 16 21:08:12 yuvarajvelmurugan-B250M-D3H systemd[1]: sonarqube.service: Control process exited, code=exited status=1

sonar.log:

--> Wrapper Started as Daemon
Launching a JVM...
Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org
  Copyright 1999-2006 Tanuki Software, Inc.  All Rights Reserved.

TERM trapped.  Shutting down.
2019.11.16 20:33:22 INFO  app[][o.s.a.AppFileSystem] Cleaning or creating temp directory /opt/sonarqube/temp
2019.11.16 20:33:22 INFO  app[][o.s.a.es.EsSettings] Elasticsearch listening on /127.0.0.1:9001
2019.11.16 20:33:22 INFO  app[][o.s.a.ProcessLauncherImpl] Launch process[[key='es', ipcIndex=1, logFilenamePrefix=es]] from [/opt/sonarqube/elasticsearch]: /opt/sonarqube/elasticsearch/bin/elasticsearch
2019.11.16 20:33:22 INFO  app[][o.s.a.SchedulerImpl] Waiting for Elasticsearch to be up and running
OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release.
2019.11.16 20:33:22 INFO  app[][o.e.p.PluginsService] no modules loaded
2019.11.16 20:33:22 INFO  app[][o.e.p.PluginsService] loaded plugin [org.elasticsearch.transport.Netty4Plugin]
2019.11.16 20:33:24 WARN  app[][o.s.a.p.AbstractManagedProcess] Process exited with exit value [es]: 143
2019.11.16 20:33:24 INFO  app[][o.s.a.SchedulerImpl] Process[es] is stopped
2019.11.16 20:33:24 INFO  app[][o.s.a.SchedulerImpl] SonarQube is stopped
<-- Wrapper Stopped

After Debugging enabled in log level:

--> Wrapper Started as Daemon
Launching a JVM...
Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org
  Copyright 1999-2006 Tanuki Software, Inc.  All Rights Reserved.

TERM trapped.  Shutting down.
2019.11.16 20:03:44 INFO  app[][o.s.a.AppFileSystem] Cleaning or creating temp directory /opt/sonarqube/temp
2019.11.16 20:03:44 INFO  app[][o.s.a.es.EsSettings] Elasticsearch listening on /127.0.0.1:9001
2019.11.16 20:03:44 INFO  app[][o.s.a.ProcessLauncherImpl] Launch process[[key='es', ipcIndex=1, logFilenamePrefix=es]] from [/opt/sonarqube/elasticsearch]: /opt/sonarqube/elasticsearch/bin/elasticsearch
2019.11.16 20:03:45 INFO  app[][o.s.a.SchedulerImpl] Waiting for Elasticsearch to be up and running
OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release.
2019.11.16 20:03:45 INFO  app[][o.e.p.PluginsService] no modules loaded
2019.11.16 20:03:45 INFO  app[][o.e.p.PluginsService] loaded plugin [org.elasticsearch.transport.Netty4Plugin]
2019.11.16 20:03:45 DEBUG app[][o.e.t.ThreadPool] created thread pool: name [force_merge], size [1], queue size [unbounded]
2019.11.16 20:03:45 DEBUG app[][o.e.t.ThreadPool] created thread pool: name [fetch_shard_started], core [1], max [8], keep alive [5m]
2019.11.16 20:03:45 DEBUG app[][o.e.t.ThreadPool] created thread pool: name [listener], size [2], queue size [unbounded]
2019.11.16 20:03:45 DEBUG app[][o.e.t.ThreadPool] created thread pool: name [index], size [4], queue size [200]
2019.11.16 20:03:45 DEBUG app[][o.e.t.ThreadPool] created thread pool: name [refresh], core [1], max [2], keep alive [5m]
2019.11.16 20:03:45 DEBUG app[][o.e.t.ThreadPool] created thread pool: name [generic], core [4], max [128], keep alive [30s]
2019.11.16 20:03:45 DEBUG app[][o.e.t.ThreadPool] created thread pool: name [warmer], core [1], max [2], keep alive [5m]
2019.11.16 20:03:45 DEBUG app[][o.e.c.u.c.QueueResizingEsThreadPoolExecutor] thread pool [_client_/search] will adjust queue by [50] when determining automatic queue size
2019.11.16 20:03:45 DEBUG app[][o.e.t.ThreadPool] created thread pool: name [search], size [7], queue size [1k]
2019.11.16 20:03:45 DEBUG app[][o.e.t.ThreadPool] created thread pool: name [flush], core [1], max [2], keep alive [5m]
2019.11.16 20:03:45 DEBUG app[][o.e.t.ThreadPool] created thread pool: name [fetch_shard_store], core [1], max [8], keep alive [5m]
2019.11.16 20:03:45 DEBUG app[][o.e.t.ThreadPool] created thread pool: name [management], core [1], max [5], keep alive [5m]
2019.11.16 20:03:45 DEBUG app[][o.e.t.ThreadPool] created thread pool: name [get], size [4], queue size [1k]
2019.11.16 20:03:45 DEBUG app[][o.e.t.ThreadPool] created thread pool: name [analyze], size [1], queue size [16]
2019.11.16 20:03:45 DEBUG app[][o.e.t.ThreadPool] created thread pool: name [write], size [4], queue size [200]
2019.11.16 20:03:45 DEBUG app[][o.e.t.ThreadPool] created thread pool: name [snapshot], core [1], max [2], keep alive [5m]
2019.11.16 20:03:45 DEBUG app[][o.e.c.u.c.QueueResizingEsThreadPoolExecutor] thread pool [_client_/search_throttled] will adjust queue by [50] when determining automatic queue size
2019.11.16 20:03:45 DEBUG app[][o.e.t.ThreadPool] created thread pool: name [search_throttled], size [1], queue size [100]
2019.11.16 20:03:45 DEBUG app[][i.n.u.i.PlatformDependent0] -Dio.netty.noUnsafe: false
2019.11.16 20:03:45 DEBUG app[][i.n.u.i.PlatformDependent0] Java version: 11
2019.11.16 20:03:45 DEBUG app[][i.n.u.i.PlatformDependent0] sun.misc.Unsafe.theUnsafe: available
2019.11.16 20:03:45 DEBUG app[][i.n.u.i.PlatformDependent0] sun.misc.Unsafe.copyMemory: available
2019.11.16 20:03:45 DEBUG app[][i.n.u.i.PlatformDependent0] java.nio.Buffer.address: available
2019.11.16 20:03:45 DEBUG app[][i.n.u.i.PlatformDependent0] direct buffer constructor: unavailable
java.lang.UnsupportedOperationException: Reflective setAccessible(true) disabled
	at io.netty.util.internal.ReflectionUtil.trySetAccessible(ReflectionUtil.java:31)
	at io.netty.util.internal.PlatformDependent0$4.run(PlatformDependent0.java:224)
	at java.base/java.security.AccessController.doPrivileged(Native Method)
	at io.netty.util.internal.PlatformDependent0.<clinit>(PlatformDependent0.java:218)
	at io.netty.util.internal.PlatformDependent.isAndroid(PlatformDependent.java:212)
	at io.netty.util.internal.PlatformDependent.<clinit>(PlatformDependent.java:80)
	at io.netty.util.ConstantPool.<init>(ConstantPool.java:32)
	at io.netty.util.AttributeKey$1.<init>(AttributeKey.java:27)
	at io.netty.util.AttributeKey.<clinit>(AttributeKey.java:27)
	at org.elasticsearch.transport.netty4.Netty4Transport.<clinit>(Netty4Transport.java:219)
	at org.elasticsearch.transport.Netty4Plugin.getSettings(Netty4Plugin.java:57)
	at org.elasticsearch.plugins.PluginsService.lambda$getPluginSettings$0(PluginsService.java:89)
	at java.base/java.util.stream.ReferencePipeline$7$1.accept(ReferencePipeline.java:271)
	at java.base/java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1654)
	at java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:484)
	at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:474)
	at java.base/java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:913)
	at java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
	at java.base/java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:578)
	at org.elasticsearch.plugins.PluginsService.getPluginSettings(PluginsService.java:89)
	at org.elasticsearch.client.transport.TransportClient.buildTemplate(TransportClient.java:147)
	at org.elasticsearch.client.transport.TransportClient.<init>(TransportClient.java:277)
	at org.sonar.application.es.EsConnectorImpl$MinimalTransportClient.<init>(EsConnectorImpl.java:103)
	at org.sonar.application.es.EsConnectorImpl.buildTransportClient(EsConnectorImpl.java:89)
	at org.sonar.application.es.EsConnectorImpl.getTransportClient(EsConnectorImpl.java:74)
	at org.sonar.application.es.EsConnectorImpl.getClusterHealthStatus(EsConnectorImpl.java:61)
	at org.sonar.application.process.EsManagedProcess.checkStatus(EsManagedProcess.java:88)
	at org.sonar.application.process.EsManagedProcess.checkOperational(EsManagedProcess.java:73)
	at org.sonar.application.process.EsManagedProcess.isOperational(EsManagedProcess.java:58)
	at org.sonar.application.process.ManagedProcessHandler.refreshState(ManagedProcessHandler.java:201)
	at org.sonar.application.process.ManagedProcessHandler$EventWatcher.run(ManagedProcessHandler.java:258)
2019.11.16 20:03:45 DEBUG app[][i.n.u.i.PlatformDependent0] java.nio.Bits.unaligned: available, true
2019.11.16 20:03:45 DEBUG app[][i.n.u.i.PlatformDependent0] jdk.internal.misc.Unsafe.allocateUninitializedArray(int): unavailable
java.lang.IllegalAccessException: class io.netty.util.internal.PlatformDependent0$6 cannot access class jdk.internal.misc.Unsafe (in module java.base) because module java.base does not export jdk.internal.misc to unnamed module @515f550a
	at java.base/jdk.internal.reflect.Reflection.newIllegalAccessException(Reflection.java:361)
	at java.base/java.lang.reflect.AccessibleObject.checkAccess(AccessibleObject.java:591)
	at java.base/java.lang.reflect.Method.invoke(Method.java:558)
	at io.netty.util.internal.PlatformDependent0$6.run(PlatformDependent0.java:334)
	at java.base/java.security.AccessController.doPrivileged(Native Method)
	at io.netty.util.internal.PlatformDependent0.<clinit>(PlatformDependent0.java:325)
	at io.netty.util.internal.PlatformDependent.isAndroid(PlatformDependent.java:212)
	at io.netty.util.internal.PlatformDependent.<clinit>(PlatformDependent.java:80)
	at io.netty.util.ConstantPool.<init>(ConstantPool.java:32)
	at io.netty.util.AttributeKey$1.<init>(AttributeKey.java:27)
	at io.netty.util.AttributeKey.<clinit>(AttributeKey.java:27)
	at org.elasticsearch.transport.netty4.Netty4Transport.<clinit>(Netty4Transport.java:219)
	at org.elasticsearch.transport.Netty4Plugin.getSettings(Netty4Plugin.java:57)
	at org.elasticsearch.plugins.PluginsService.lambda$getPluginSettings$0(PluginsService.java:89)
	at java.base/java.util.stream.ReferencePipeline$7$1.accept(ReferencePipeline.java:271)
	at java.base/java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1654)
	at java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:484)
	at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:474)
	at java.base/java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:913)
	at java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
	at java.base/java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:578)
	at org.elasticsearch.plugins.PluginsService.getPluginSettings(PluginsService.java:89)
	at org.elasticsearch.client.transport.TransportClient.buildTemplate(TransportClient.java:147)
	at org.elasticsearch.client.transport.TransportClient.<init>(TransportClient.java:277)
	at org.sonar.application.es.EsConnectorImpl$MinimalTransportClient.<init>(EsConnectorImpl.java:103)
	at org.sonar.application.es.EsConnectorImpl.buildTransportClient(EsConnectorImpl.java:89)
	at org.sonar.application.es.EsConnectorImpl.getTransportClient(EsConnectorImpl.java:74)
	at org.sonar.application.es.EsConnectorImpl.getClusterHealthStatus(EsConnectorImpl.java:61)
	at org.sonar.application.process.EsManagedProcess.checkStatus(EsManagedProcess.java:88)
	at org.sonar.application.process.EsManagedProcess.checkOperational(EsManagedProcess.java:73)
	at org.sonar.application.process.EsManagedProcess.isOperational(EsManagedProcess.java:58)
	at org.sonar.application.process.ManagedProcessHandler.refreshState(ManagedProcessHandler.java:201)
	at org.sonar.application.process.ManagedProcessHandler$EventWatcher.run(ManagedProcessHandler.java:258)
2019.11.16 20:03:45 DEBUG app[][i.n.u.i.PlatformDependent0] java.nio.DirectByteBuffer.<init>(long, int): unavailable
2019.11.16 20:03:45 DEBUG app[][i.n.u.i.PlatformDependent] sun.misc.Unsafe: available
2019.11.16 20:03:45 DEBUG app[][i.n.u.i.PlatformDependent] maxDirectMemory: 33554432 bytes (maybe)
2019.11.16 20:03:45 DEBUG app[][i.n.u.i.PlatformDependent] -Dio.netty.tmpdir: /tmp (java.io.tmpdir)
2019.11.16 20:03:45 DEBUG app[][i.n.u.i.PlatformDependent] -Dio.netty.bitMode: 64 (sun.arch.data.model)
2019.11.16 20:03:45 DEBUG app[][i.n.u.i.PlatformDependent] -Dio.netty.maxDirectMemory: -1 bytes
2019.11.16 20:03:45 DEBUG app[][i.n.u.i.PlatformDependent] -Dio.netty.uninitializedArrayAllocationThreshold: -1
2019.11.16 20:03:45 DEBUG app[][i.n.u.i.CleanerJava9] java.nio.ByteBuffer.cleaner(): available
2019.11.16 20:03:45 DEBUG app[][i.n.u.i.PlatformDependent] -Dio.netty.noPreferDirect: false
2019.11.16 20:03:46 DEBUG app[][o.s.a.SchedulerImpl] Stopping [ce]...
2019.11.16 20:03:46 DEBUG app[][o.s.a.SchedulerImpl] Stopping [web]...
2019.11.16 20:03:46 DEBUG app[][o.s.a.SchedulerImpl] Stopping [es]...
2019.11.16 20:03:46 WARN  app[][o.s.a.p.AbstractManagedProcess] Process exited with exit value [es]: 143
2019.11.16 20:03:46 INFO  app[][o.s.a.SchedulerImpl] Process[es] is stopped
2019.11.16 20:03:46 INFO  app[][o.s.a.SchedulerImpl] SonarQube is stopped
<-- Wrapper Stopped

Hi, could you alter the sonarqube user so you could login with it and start Sonar manually?

two sonarqube is using
sonarqube6.5 is working fine but sonarqube 8.9 getting error sonar properties also added java11 path

Hi @Irfanulla_M,

This topic is two years old and about a different version. Please create a new thread and provide your log details.

 
Ann