Trouble Set up Sonarqube 8.2 on OEl 7.7

Must-share information (formatted with Markdown):

  • which versions are you using (SonarQube, Scanner, Plugin, and any relevant extension)
    I want to get the Latest Version of Sonarqube 8.2

  • what are you trying to achieve
    I want to set up Sonarqube 8.2 to be able to scan code with Azure DevOps on an OEl 7.7 server

  • what have you tried so far to achieve this
    I was able to get PostgresSQL 12 installed and Java-11 as well and I was able to get the Sonarqube 8.2 file on the server but the web app does not appear when I try to find it. I need help with this as soon as possible. If you need the logs I can get the logs to see what issue I am having.

Thank you.

Hi,

Welcome to the community!

Could you add some details around this part? Did you start the server?

 
Ann

Yes the server was started and it said it was active thats why I was confused on why I couldn’t find the web app.

And where did you look for it? :slightly_smiling_face:

I have my web server set to this

address will be used for listening on the specified ports.
# By default, ports will be used on all IP addresses associated with the server.
sonar.web.host=0.0.0.0

# Web context. When set, it must start with forward slash (for example /sonarqu$
# The default value is root context (empty value).
sonar.web.context=/opt/sonar
# TCP port for incoming HTTP connections. Default value is 9000.
sonar.web.port=9000

Also here are my logs from sonar.logs

2020.03.23 16:30:54 INFO  app[][o.s.a.AppFileSystem] Cleaning or creating temp directory /opt/sonar/temp
2020.03.23 16:30:54 INFO  app[][o.s.a.es.EsSettings] Elasticsearch listening on /127.0.0.1:9001
2020.03.23 16:30:54 INFO  app[][o.s.a.ProcessLauncherImpl] Launch process[[key='es', ipcIndex=1, logFilenamePrefix=es]] from [/opt/sonar/elasticsearch]: /opt/sonar/elasticsearch/bin/elasticsearch
2020.03.23 16:30:54 INFO  app[][o.s.a.SchedulerImpl] Waiting for Elasticsearch to be up and running
2020.03.23 16:30:56 INFO  app[][o.e.p.PluginsService] no modules loaded
2020.03.23 16:30:56 INFO  app[][o.e.p.PluginsService] loaded plugin [org.elasticsearch.transport.Netty4Plugin]
OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release.
2020.03.23 16:31:48 INFO  app[][o.s.a.SchedulerImpl] Process[es] is up
2020.03.23 16:31:48 INFO  app[][o.s.a.ProcessLauncherImpl] Launch process[[key='web', ipcIndex=2, logFilenamePrefix=web]] from [/opt/sonar]: /usr/lib/jvm/java-11-openjdk-11.0.6.10-1.0.1.el7_7.x86_64/bin/java -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djava.io.tmpdir=/opt/sonar/temp --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.io=ALL-UNNAMED --add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED -Xmx512m -Xms128m -XX:+HeapDumpOnOutOfMemoryError -Dhttp.nonProxyHosts=localhost|127.*|[::1] -cp ./lib/common/*:/opt/sonar/lib/jdbc/postgresql/postgresql-42.2.8.jar org.sonar.server.app.WebServer /opt/sonar/temp/sq-process570278698711471968properties

Hi,

Try commenting sonar.web.host back out. You should be able to find it on localhost:9000 then.

 
HTH,
Ann

Hello when you say Try commenting sonar.web.host back out what do you mean ?

Hi,

I mean replace the # at the beginning of that line so that the default kicks back in.

 
Ann

Oh ok so add the # at the start of sonar.web.host? and it should go back to the default?

Yes.

 
Ann

Ok I changed it and at least I got this. what would be the next step?

Here are the new logs.

2020.03.24 15:37:47 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.
2020.03.24 15:37:48 INFO  app[][o.e.p.PluginsService] no modules loaded
2020.03.24 15:37:48 INFO  app[][o.e.p.PluginsService] loaded plugin [org.elasticsearch.transport.Netty4Plugin]
2020.03.24 15:39:05 INFO  app[][o.s.a.SchedulerImpl] Process[es] is up
2020.03.24 15:39:05 INFO  app[][o.s.a.ProcessLauncherImpl] Launch process[[key='web', ipcIndex=2, logFilenamePrefix=web]] from [/opt/sonar]: /usr/lib/jvm/java-11-openjdk-11.0.6.10-1.0.1.el7_7.x86_64/bin/java -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djava.io.tmpdir=/opt/sonar/temp --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.io=ALL-UNNAMED --add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED -Xmx512m -Xms128m -XX:+HeapDumpOnOutOfMemoryError -Dhttp.nonProxyHosts=localhost|127.*|[::1] -cp ./lib/common/*:/opt/sonar/lib/jdbc/postgresql/postgresql-42.2.8.jar org.sonar.server.app.WebServer /opt/sonar/temp/sq-process5271680945573454937properties
2020.03.24 15:39:50 INFO  app[][o.s.a.SchedulerImpl] Process[web] is up
2020.03.24 15:39:50 INFO  app[][o.s.a.ProcessLauncherImpl] Launch process[[key='ce', ipcIndex=3, logFilenamePrefix=ce]] from [/opt/sonar]: /usr/lib/jvm/java-11-openjdk-11.0.6.10-1.0.1.el7_7.x86_64/bin/java -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djava.io.tmpdir=/opt/sonar/temp --add-opens=java.base/java.util=ALL-UNNAMED -Xmx512m -Xms128m -XX:+HeapDumpOnOutOfMemoryError -Dhttp.nonProxyHosts=localhost|127.*|[::1] -cp ./lib/common/*:/opt/sonar/lib/jdbc/postgresql/postgresql-42.2.8.jar org.sonar.ce.app.CeServer /opt/sonar/temp/sq-process17829307523506852319properties
2020.03.24 15:40:18 INFO  app[][o.s.a.SchedulerImpl] Process[ce] is up
2020.03.24 15:40:18 INFO  app[][o.s.a.SchedulerImpl] SonarQube is up

Hi,

The 404 error code indicates that a web server (probably SonarQube’s!) is running, but doesn’t have anything at that address to give you. And in fact when I go back to your server properties, I notice this:

Which means you’ve told SonarQube to put itself at the path /opt/sonar, i.e. http://localhost:9000/opt/sonar.

 
HTH,
Ann

Yes that was it ! thank you so much!