- I upgraded SonarQube 7.9 to 8.1 on an Ubuntu 18.04 (100k line paid edition)
- I found that I got a new server ID, thus I had to contact the friendly folks at SonarQube support to get a new license file.
- I configured the new 8.1 on the same Linux box as where I had the 7.9 version. I made an error with my tokens and chose to redo the 8.1 installation since I was not very far into it.
- I moved the 8.1 away and installed in the same with into the same /opt/sonarqube-126.96.36.199237/ as where I started.
- When I then checked the new instance it was identified with a new yet another server ID - even though the first and second installation of SonarQube 8.1 was made on the same server, same directory etc. Very odd!
- After reverting back to the first 8.1 installation - I managed to delete the wrong tokens, and got back on track, but I was a bit annoyed to see yet another server ID after both of the two re-installs.
Have others seen this behaviour?
Server ID is expected to change if the DB JDBC URL string changes or if data in the DB is changed (fresh dataset for example). Did any of those happen in your case?
Ok, could you explain how your database is set up?
Also what do you mean with making an error with your tokens and later deleting them?
I have not set up any database - just using the default embedded H2 database.
I have not seen a real need for e.g. postgresql (yet).
I have some C based projects where I authenticate the scanner towards sonarqube via a token - generated in the sonarqube web UI.
Ok, thanks for clarifying. The default H2 setup is be based on the installation directory so changes to it might affect the server ID. We don’t recommend that setup for production instances.
Maybe one of the developers can try the following:
- Install sonarqube-188.8.131.52237 into /opt/sonarqube-184.108.40.206237/ (or similar if there is another build)
- Install sonarqube-220.127.116.11929 into /opt/sonarqube-18.104.22.168929/
In /opt/sonarqube-*/conf/sonar.properties add three values e.g. on the top (or outcomment)
(I use Nginx as a frontend - you can most likely skip sonar.web.context)
I get different server ID for the two installations. Yes - I know that I should replace the H2 database with e.g. some better database - but I have not done that.
This is intended, or else you could use the same license for infinite installations of SonarQube embedded database. Your license entitles you to one.
Aaah your call - fair enough if you want that this requires e.g. me to connect to customer support to upgrade a developer edition.
While we are at it, what is the terms for upgrading a developer license. https://www.sonarqube.org/trial-request/developer-edition/ could/should describe for how long I am entitled to upgrade licenses.
Especially since the installation flashes the new editions at
There is typically no Server ID change when you upgrade SonarQube – you are using the embedded database that’s only supposed to be used for evaluation.
If you start using an external database, your problem is solved
@Colin ok - I will give it a spin with PostgressSql.
Will this require a new license when “upgrading” from H2 to PostgressSql?
Yep! Feel free to link to this topic when you get in touch with firstname.lastname@example.org. Might smooth things a little
I did write this post in accordance with emails with @Elizabeth_Gunderson