Upgrading SonarQube 7.9 -> 8.1 gives a new server id

  • 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-8.1.0.31237/ 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?

Hi Peter.
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?

No same same.

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.