Hi y’all,
Before purchasing a Developer’s License for SonarQube, my company spent 2 weeks with a trial key that we spun up on an on-prem server. Once we were satisfied with the results SonarQube was giving us, we purchased the full license and started the process of getting it set up on a brand new Azure Virtual Machine dedicated solely for SonarQube, its database, and the scanner. Despite following the same steps we followed when setting up the trial key (and before that, the community edition), we are unable to get SonarQube to spin up fully.
A standard console log from the command prompt after running the StartSonar command is:
--> Wrapper Started as Console
Launching a JVM...
Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org
Copyright 1999-2006 Tanuki Software, Inc. All Rights Reserved.
2021.12.17 15:21:31 INFO app[][o.s.a.AppFileSystem] Cleaning or creating temp directory C:\Users\kp\Desktop\sonarqube\..\SonarQube_Data\temp
2021.12.17 15:21:31 INFO app[][o.s.a.es.EsSettings] Elasticsearch listening on [HTTP: 127.0.0.1:9002, TCP: 127.0.0.1:64243]
2021.12.17 15:21:32 INFO app[][o.s.a.ProcessLauncherImpl] Launch process[[key='es', ipcIndex=1, logFilenamePrefix=es]] from [C:\Users\kp\Desktop\sonarqube\elasticsearch]: C:\Program Files\Java\jdk-11.0.12\bin\java -XX:+UseG1GC -Djava.io.tmpdir=C:\Users\kp\Desktop\sonarqube\..\SonarQube_Data\temp -XX:ErrorFile=../logs/es_hs_err_pid%p.log -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 -Dio.netty.allocator.numDirectArenas=0 -Dlog4j.shutdownHookEnabled=false -Dlog4j2.disable.jmx=true -Djava.locale.providers=COMPAT -Dcom.redhat.fips=false -Des.enforce.bootstrap.checks=true -Xmx512m -Xms512m -XX:MaxDirectMemorySize=256m -XX:+HeapDumpOnOutOfMemoryError -Delasticsearch -Des.path.home=C:\Users\kp\Desktop\sonarqube\elasticsearch -Des.path.conf=C:\Users\kp\Desktop\sonarqube\..\SonarQube_Data\temp\conf\es -cp lib/* org.elasticsearch.bootstrap.Elasticsearch
2021.12.17 15:21:32 INFO app[][o.s.a.SchedulerImpl] Waiting for Elasticsearch to be up and running
2021.12.17 15:21:51 INFO app[][o.s.a.SchedulerImpl] Process[es] is up
2021.12.17 15:21:51 INFO app[][o.s.a.ProcessLauncherImpl] Launch process[[key='web', ipcIndex=2, logFilenamePrefix=web]] from [C:\Users\kp\Desktop\sonarqube]: C:\Program Files\Java\jdk-11.0.12\bin\java -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djava.io.tmpdir=C:\Users\kp\Desktop\sonarqube\..\SonarQube_Data\temp -XX:-OmitStackTraceInFastThrow --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 --add-exports=java.base/jdk.internal.ref=ALL-UNNAMED --add-opens=java.base/java.nio=ALL-UNNAMED --add-opens=java.base/sun.nio.ch=ALL-UNNAMED --add-opens=java.management/sun.management=ALL-UNNAMED --add-opens=jdk.management/com.sun.management.internal=ALL-UNNAMED -Dcom.redhat.fips=false -Xmx512m -Xms128m -XX:+HeapDumpOnOutOfMemoryError -Dhttp.nonProxyHosts=localhost|127.*|[::1] -cp ./lib/sonar-application-9.2.1.49989.jar;C:\Users\kp\Desktop\sonarqube\lib\jdbc\mssql\mssql-jdbc-9.2.0.jre11.jar org.sonar.server.app.WebServer C:\Users\kp\Desktop\sonarqube\..\SonarQube_Data\temp\sq-process11783157654702250184properties
Before on the on-prem server and before locally with the community edition, simply using StartSonar would have the system take about 10 seconds to boot up and open sonarqube in localhost, but now after printing the “Launch Process [key=‘web’]” line, the startup just hangs until it is Ctrl-C trapped and shutdown ungracefully. Is there something simple we’re missing here (such as, more resources dedicated for it in the Virtual Machine’s settings?)
We’d appreciate any amount of help here!
Thank you!