Hello,
I guess i have a similar error, but i dont understand. I’ve been working just fine last couple of weeks with SonarQube, but when i started working today it throwed me a similar error. I also work on Windows and i maked sure there’s no other process running.
Here are the logs:
sonar.txt (13.7 KB)
es.txt (9.8 KB)
Aprecciate any help.
I’ve moved your topic to a new thread because it seems unrelated to the thread you posted on.
2020.04.22 17:33:07 ERROR es[o.e.b.Bootstrap] Exception
org.elasticsearch.transport.BindTransportException: Failed to bind to [9001]
…
Caused by: java.net.BindException: Address already in use: bind
It looks like SonarQube can’t start its Elasticsearch process on Port 9001 because something else is already running there. Maybe another SonarQube instance?
You can use a tool like netstat to find out what’s running there.
I’ve already done that. It seems the “System” (with PID 4) is using that port, but no other SonarQube process.
The thing is that i didnt change anything. I just started working as usual.
While you figure out what’s going on with that port, you might try changing the Elasticsearch port in your conf/sonar.properties file (sonar.search.port) to a different port and see if the rest of the startup succeeds (or any new errors show up that help pinpoint the issue)
I changed the port in my conf/sonar.properties and it worked. I dont undestand what changed from other days, i literally did same thing.
Thanks for your soon reply, appreciate it.
Best regards!
