SonarQube in Azure container insance

Joao_Paulo_Fernandes · June 15, 2020, 3:38pm

Hi,

After installing and seeing running sonarqube inside an azure container instance, I’ve saw today that is no long working over web browser.
When I try to open I get a timeout.
I’ve tried to restart / stop many times and always get the same on logs.
I’m using SonarQube version 8.3.1-community
Here some information grab from log files
sonar.log:
2020.06.15 15:15:05 DEBUG app[o.s.a.p.ManagedProcessLifecycle] EventWatcher[web] tryToMoveTo ce from STARTING to STARTED => true
2020.06.15 15:15:12 INFO app[o.s.a.SchedulerImpl] Process[ce] is up
2020.06.15 15:15:12 DEBUG app[o.s.a.p.ManagedProcessLifecycle] EventWatcher[ce] tryToMoveTo es from STARTED to STARTING => false
2020.06.15 15:15:12 DEBUG app[o.s.a.p.ManagedProcessLifecycle] EventWatcher[ce] tryToMoveTo web from STARTED to STARTING => false
2020.06.15 15:15:12 DEBUG app[o.s.a.p.ManagedProcessLifecycle] EventWatcher[ce] tryToMoveTo ce from STARTED to STARTING => false
2020.06.15 15:15:12 DEBUG app[o.s.a.NodeLifecycle] EventWatcher[ce] tryToMoveTo from STARTING to OPERATIONAL => true
2020.06.15 15:15:12 INFO app[o.s.a.SchedulerImpl] SonarQube is up

Web.log:
2020.06.15 15:13:02 DEBUG web[o.s.s.a.TomcatAccessLog] Tomcat is started
2020.06.15 15:13:02 INFO web[o.s.s.a.EmbeddedTomcat] HTTP connector enabled on port 9000

Thank you for your help

Regards
Joao Fernandes

ganncamp · June 15, 2020, 7:01pm

Hi,

Welcome to the community!

What do your other server logs say?

Ann

Joao_Paulo_Fernandes · June 16, 2020, 6:24am

Hi,
Thank you for your feedback,
No other message on server site. Beside to this post have open a ticket on MS site in order to obtain too more details.

ganncamp · June 16, 2020, 12:20pm

Hi,

If there are no errors or shutdown messages in your logs, then I guess your server is up. Maybe talk to your network folks?

Ann

Rouke.Broersma.IS · June 16, 2020, 1:04pm

We actually also run sonarqube 8.3.1 in azure container instances but we have no problems. What exactly is the problem you’re seeing?

Joao_Paulo_Fernandes · June 17, 2020, 7:40am

Hi Rouke,

The problem is after re-start de instance, I’m not able to open the sonar from a browser. I’ve opened a ticket too at Microsoft. This is not the first time I have this issue; in February I’ve face the same issue in a different tenant:

https://social.msdn.microsoft.com/Forums/en-US/7852cafd-a4e7-4d2a-8f48-56bf551c9a4f/azure-container-instance-unable-to-know-what-appends-after-starting-instance?forum=AzureContainerServices
I’ve configured my container instance with the following parameters:
os_type = “Linux”
image = “sonarqube:latest”
port = 9000
protocol = “TCP”
cpu = “2”
memory = “4”
ocation = “westeurope”

Regards
Joao Fernandes

Rouke.Broersma.IS · June 17, 2020, 8:03am

Mhm I have never seen that behavior before and we’ve been running ~10 sonarqube instances in azure container instance for about a year now. But we use container instance in private vnet with app gateway as ingress, not public IP ingress.