SonarQube service stopping itself immediately after start

Using Windows 10, Java 11, sonarqube-9.8.0.63668. It used to work fine. I am not sure what is wrong or what I changed. Please help. I see that other people were asked to post the logs, so I’ll be sure to add them.

This is what happens in command prompt:

Starting SonarQube…
2023.02.17 07:17:26 INFO app[o.s.a.AppFileSystem] Cleaning or creating temp directory C:\Users\mayhe\Documents\sonarqube-9.8.0.63668\sonarqube-9.8.0.63668\temp
2023.02.17 07:17:26 INFO app[o.s.a.es.EsSettings] Elasticsearch listening on [HTTP: 127.0.0.1:9001, TCP: 127.0.0.1:57937]
2023.02.17 07:17:26 INFO app[o.s.a.ProcessLauncherImpl] Launch process[ELASTICSEARCH] from [C:\Users\mayhe\Documents\sonarqube-9.8.0.63668\sonarqube-9.8.0.63668\elasticsearch]: C:\Program Files\Eclipse Adoptium\jdk-17.0.5.8-hotspot\bin\java -XX:+UseG1GC -Djava.io.tmpdir=C:\Users\mayhe\Documents\sonarqube-9.8.0.63668\sonarqube-9.8.0.63668\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 -Djna.tmpdir=C:\Users\mayhe\Documents\sonarqube-9.8.0.63668\sonarqube-9.8.0.63668\temp -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 -Dlog4j2.formatMsgNoLookups=true -Djava.locale.providers=COMPAT -Dcom.redhat.fips=false -Xmx512m -Xms512m -XX:MaxDirectMemorySize=256m -XX:+HeapDumpOnOutOfMemoryError -Delasticsearch -Des.path.home=C:\Users\mayhe\Documents\sonarqube-9.8.0.63668\sonarqube-9.8.0.63668\elasticsearch -Des.path.conf=C:\Users\mayhe\Documents\sonarqube-9.8.0.63668\sonarqube-9.8.0.63668\temp\conf\es -cp lib/* org.elasticsearch.bootstrap.Elasticsearch
2023.02.17 07:17:26 INFO app[o.s.a.SchedulerImpl] Waiting for Elasticsearch to be up and running
2023.02.17 07:17:35 INFO app[o.s.a.SchedulerImpl] Process[es] is up
2023.02.17 07:17:35 INFO app[o.s.a.ProcessLauncherImpl] Launch process[WEB_SERVER] from [C:\Users\mayhe\Documents\sonarqube-9.8.0.63668\sonarqube-9.8.0.63668]: C:\Program Files\Eclipse Adoptium\jdk-17.0.5.8-hotspot\bin\java -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djava.io.tmpdir=C:\Users\mayhe\Documents\sonarqube-9.8.0.63668\sonarqube-9.8.0.63668\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.8.0.63668.jar;C:\Users\mayhe\Documents\sonarqube-9.8.0.63668\sonarqube-9.8.0.63668\lib\jdbc\h2\h2-2.1.214.jar org.sonar.server.app.WebServer C:\Users\mayhe\Documents\sonarqube-9.8.0.63668\sonarqube-9.8.0.63668\temp\sq-process8367949625542920735properties
WARNING: A terminally deprecated method in java.lang.System has been called
WARNING: System::setSecurityManager has been called by org.sonar.process.PluginSecurityManager (file:/C:/Users/mayhe/Documents/sonarqube-9.8.0.63668/sonarqube-9.8.0.63668/lib/sonar-application-9.8.0.63668.jar)
WARNING: Please consider reporting this to the maintainers of org.sonar.process.PluginSecurityManager
WARNING: System::setSecurityManager will be removed in a future release
2023.02.17 07:17:37 INFO app[o.s.a.SchedulerImpl] Process[Web Server] is stopped
2023.02.17 07:17:37 INFO app[o.s.a.SchedulerImpl] Process[ElasticSearch] is stopped
2023.02.17 07:17:37 INFO app[o.s.a.SchedulerImpl] SonarQube is stopped

es.log (110.1 KB)
sonar.log (76.5 KB)
web.log (199.9 KB)