Process[Web Server] is stopped Process[ElasticSearch] is stopped SonarQube is stopped

I am facing issues regarding SonarQube server as it gets automatically stopped after every 2 weeks, sometimes there is a issue regarding the elastic search.
I also attached log files of es, sonar and web respectively.
Below is showing a logs:

2023.02.27 15:41:18 INFO  app[x][o.s.a.AppFileSystem] Cleaning or creating temp directory C:\Software\sonarqube\temp
2023.02.27 15:41:18 INFO  app[x][] Elasticsearch listening on [HTTP:, TCP:]
2023.02.27 15:41:18 INFO  app[x][o.s.a.ProcessLauncherImpl] Launch process[ELASTICSEARCH] from [C:\Software\sonarqube\elasticsearch]: C:\Program Files\Java\jdk-\bin\java -XX:+UseG1GC\Software\sonarqube\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:\Software\sonarqube\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:\Software\sonarqube\elasticsearch -Des.path.conf=C:\Software\sonarqube\temp\conf\es -cp lib/* org.elasticsearch.bootstrap.Elasticsearch
2023.02.27 15:41:18 INFO  app[x][o.s.a.SchedulerImpl] Waiting for Elasticsearch to be up and running
2023.02.27 15:41:27 INFO  app[x][o.s.a.SchedulerImpl] Process[es] is up
2023.02.27 15:41:27 INFO  app[x][o.s.a.ProcessLauncherImpl] Launch process[WEB_SERVER] from [C:\Software\sonarqube]: C:\Program Files\Java\jdk-\bin\java -Djava.awt.headless=true -Dfile.encoding=UTF-8\Software\sonarqube\temp -XX:-OmitStackTraceInFastThrow --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/ --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/ -Dcom.redhat.fips=false -Xmx512m -Xms128m -XX:+HeapDumpOnOutOfMemoryError -Dhttp.nonProxyHosts=localhost|127.*|[::1] -cp ./lib/sonar-application-;C:\Software\sonarqube\lib\jdbc\h2\h2-2.1.212.jar C:\Software\sonarqube\temp\sq-process9721664470803007133properties
2023.02.27 15:41:28 INFO  app[x][o.s.a.SchedulerImpl] Process[Web Server] is stopped
2023.02.27 15:41:28 INFO  app[x][o.s.a.SchedulerImpl] Process[ElasticSearch] is stopped
2023.02.27 15:41:28 INFO  app[x][o.s.a.SchedulerImpl] SonarQube is stopped

es.log (47.0 KB)
sonar.log (29.6 KB)
web.log (48.3 KB)


According to the app logging you posted, the failure is in the web process:

So it makes sense to go straight to web.log, where I see this:

2023.02.27 11:47:04 INFO  web[][o.s.p.ProcessEntryPoint] Starting Web Server
2023.02.27 11:47:05 ERROR web[][o.s.s.a.EmbeddedTomcat] Fail to start web server
org.apache.catalina.LifecycleException: Protocol handler initialization failed
Caused by: Cannot assign requested address: bind

It looks like either something is already using the address you’ve assigned to the web process (a zombie thread from a previous attempt to run the server? another process?) or the process simply isn’t allowed to use it.


Yes, there is a problem from my side, where I have provided the wrong IP address which is associated with the server, which is caused due to change in Place of seating. When I changed my place it will automatically change the associated IP address.

1 Like

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