SonarQube Container Stopped/Exited Without Error

SonarQube
,
1

SonarQube Version: 8.1
Host OS: Centos 7

Partial logs entry:
2020.08.13 22:31:15 INFO app[o.s.a.SchedulerImpl] Stopping SonarQube
2020.08.13 22:31:16 INFO ce[o.s.p.ProcessEntryPoint] Gracefully stopping process
2020.08.13 22:31:17 INFO ce[o.s.ce.app.CeServer] Compute Engine is stopping…
2020.08.13 22:31:18 INFO ce[o.s.c.t.CeProcessingSchedulerImpl] Gracefully stopping workers…
2020.08.13 22:31:18 INFO ce[o.s.ce.app.CeServer] Compute Engine is stopped
2020.08.13 22:31:19 INFO app[o.s.a.SchedulerImpl] Process[ce] is stopped
2020.08.13 22:31:19 INFO web[o.s.p.ProcessEntryPoint] Gracefully stopping process
2020.08.13 22:31:20 INFO web[o.s.s.n.NotificationDaemon] Notification service stopped

Note that there is no error being showed within the log file before the log entry above

Docker exit status code: 143

Thanks

2

Hi @SlackOng95 ,

this log indicates that someone (or something) send a stop signal (SIGTERM) to this container so sonarqube shut down gracefully. sadly the bundled elasticsearch is sometimes not stopped in time which results in:

nothing to worry about and sadly nothing we can do about (see elastics statement in this issue)

3

Possible to track that someone/something that caused the sonarqube container shutdown?

From our side, we can assure that there is nobody shut it down manually and instead it goes down automatically

4

there could be indicators within dmesg or the system log. I also found a network related bug on centos that could be the reason that the network connection in between the database and sonarqube is disrupted, resulting in a shutdown of sonarqube. But i think it has to be something else as there would be a log entry about that

1 Like
5

Thanks for the valuable inputs.

6

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.