Change SonarQube from Community Edition to Enterprise Edition in Azure VM

pthomas1997 2019-07-10 18:08:47 UTC #1

Keywords: SonarQube - Microsoft Azure - How to - Other
Description:
I set up a VM in Azure from the Bitnami Certified SonarQube resource, and it runs the Community Edition. I want to run Enterprise Edition on the VM, using SQL and all the other things that come along with the Bitnami setup. How can I change from Community Edition to Enterprise?

Thanks!

jota 2019-07-11 07:22:34 UTC #2

Hi @pthomas1997,

Thank you for using Bitnami. As you mentioned, we provide the Community edition of the application and we also have this guide to update the solution to a newer version.

https://docs.bitnami.com/azure/apps/sonarqube/administration/upgrade/#upgrade-only-sonarqube-in-the-bitnami-sonarqube-stack

I think those steps also work when moving between plans of the application but I suggest you ask for confirmation to the SonarQube developers. Once they confirm that those steps are compatible with the Developer edition, you can go ahead with the migration. In order to recover the installation easily, you can create a backup of the installation directory before starting the process.

https://docs.bitnami.com/azure/apps/sonarqube/administration/backup-restore

Do not hesitate to write us if you have any questions about our solution

SonarQube Certified by Bitnami ARM in Azure

pthomas1997 2019-07-11 12:46:12 UTC #3

Hey @jota,

I followed the instructions in the link you provided, and got the following error (paraphrased):
tail: error opening /opt/bitnami/sonarqube/sonarqube/logs/sonar.log: file not found

So I touched sonar.log and that error went away, however, the ctlscript is still not able to start SonarQube. Any ideas?

jota 2019-07-12 07:20:41 UTC #4

Hi @pthomas1997,

We have a Support Tool that will gather relevant information for us to analyze your configuration and logs. Could you please download and execute it on the machine where the stack is running by following the steps described in the guide below?

How to Run the Bitnami Support Tool

Please note that you need to paste the code outputted by the tool in your reply.

pthomas1997 2019-07-12 12:12:17 UTC #5

Ok @jota here's the code:
dbcaedc2-2ef2-d5e6-b7e8-f64f3884ebf4

Thanks for the help

jota 2019-07-15 11:10:44 UTC #6

Hi @pthomas1997

The SonarQube's logs are inside the /opt/bitnami/apps/sonarqube/sonarqube/logs/ folder, not inside the /opt/bitnami/sonarqube/sonarqube/logs one. Please set this value in the SonarQube's configuration and set the permissions correctly

sudo chown -R sonarqube:sonarqube /opt/bitnami/apps/sonarqube/sonarqube/logs/*

Happy to help!

Was my answer helpful? Click on

jota 2019-07-15 11:12:15 UTC #7

Hi again @pthomas1997,

Regarding the way to upgrade SonarQube, I just found that they have this guide.

https://docs.sonarqube.org/display/SONARQUBE67/Enterprise+Edition

Just in case you want to recover your backup and follow that process to perform the upgrade. If you have any other questions, I suggest you ask the SonarQube's developers to know more about how to proceed.

Thanks

pthomas1997 2019-07-16 12:28:58 UTC #8

@jota,
In sonar.properties I have the log path set as sonar.path.logs=/opt/bitnami/apps/sonarqube/sonarqube/logs/

Did you mean that I should set it to the other one?

jota 2019-07-17 09:44:39 UTC #9

Hi @pthomas1997,

What I'm saying is that you mentioned a different path above

The correct one is /opt/bitnami/apps/sonarqube/sonarqube/logs/. When did you obtain the error related to the wrong path of the log file (/opt/bitnami/sonarqube/sonarqube/logs/sonar.log)?

pthomas1997 2019-07-17 12:15:01 UTC #10

@jota,
I'm not sure. Somewhere along the line when I attempted to start SonarQube. Should I try changing the log path to /opt/bitnami/sonarqube/sonarqube/logs/? I'm not getting the error anymore, or any errors, it just doesn't start.

jota 2019-07-18 09:42:13 UTC #11

Hi @pthomas1997,

No, I don't want you to change the logs folder but I suggest you check the configuration files of SonarQube to ensure that it's using the correct path. Once you do that, continue with the process.