<div dir="ltr"><div dir="ltr">On Wed, Jun 12, 2019 at 7:57 PM Hire, Shannon [US] (MS) <<a href="mailto:Shannon.Hire@ngc.com">Shannon.Hire@ngc.com</a>> wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div lang="EN-US">
<div class="gmail-m_-4913605907034622546WordSection1">
<p class="MsoNormal">Hi,<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">I’m not sure if this is the right place to ask for help, but my system log directed me here.</p></div></div></blockquote><div><br></div><div>It varies... The `journalctl -x` output is a bit misleading, in that the message was *shown by* systemd, but quite often has nothing to do with the actual reason the service crashed.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div lang="EN-US"><div class="gmail-m_-4913605907034622546WordSection1"><p class="MsoNormal">
<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">So I currently have SonarQube set up on a Linux CentOS VM. Yesterday I was able to start up SonarQube just fine, but today I am having issues and am unsure why.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Here is the status output:<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">● sonar.service - SonarQube<u></u><u></u></p>
<p class="MsoNormal"> Loaded: loaded (/etc/systemd/system/sonar.service; enabled; vendor preset: disabled)<u></u><u></u></p>
<p class="MsoNormal"> Active: failed (Result: start-limit) since Wed 2019-06-12 11:12:49 CDT; 3min 21s ago<u></u><u></u></p>
<p class="MsoNormal"> Process: 25886 ExecStart=/opt/sonarqube/bin/linux-x86-64/sonar.sh --debug start (code=exited, status=1/FAILURE)<u></u><u></u></p>
<p class="MsoNormal">Main PID: 22198 (code=exited, status=0/SUCCESS)<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Jun 12 11:12:49 <a href="http://wx-bld07.ms.northgrum.com" target="_blank">wx-bld07.ms.northgrum.com</a> systemd[1]: Failed to start SonarQube.<u></u><u></u></p>
<p class="MsoNormal">Jun 12 11:12:49 <a href="http://wx-bld07.ms.northgrum.com" target="_blank">wx-bld07.ms.northgrum.com</a> systemd[1]: Unit sonar.service entered failed state.<u></u><u></u></p>
<p class="MsoNormal">Jun 12 11:12:49 <a href="http://wx-bld07.ms.northgrum.com" target="_blank">wx-bld07.ms.northgrum.com</a> systemd[1]: sonar.service failed.<u></u><u></u></p>
<p class="MsoNormal">Jun 12 11:12:49 <a href="http://wx-bld07.ms.northgrum.com" target="_blank">wx-bld07.ms.northgrum.com</a> systemd[1]: start request repeated too quickly for sonar.service<u></u><u></u></p>
<p class="MsoNormal">Jun 12 11:12:49 <a href="http://wx-bld07.ms.northgrum.com" target="_blank">wx-bld07.ms.northgrum.com</a> systemd[1]: Failed to start SonarQube.<u></u><u></u></p>
<p class="MsoNormal">Jun 12 11:12:49 <a href="http://wx-bld07.ms.northgrum.com" target="_blank">wx-bld07.ms.northgrum.com</a> systemd[1]: Unit sonar.service entered failed state.<u></u><u></u></p>
<p class="MsoNormal">Jun 12 11:12:49 <a href="http://wx-bld07.ms.northgrum.com" target="_blank">wx-bld07.ms.northgrum.com</a> systemd[1]: sonar.service failed.</p></div></div></blockquote><div><br></div><div>Does the service write its logs anywhere else (e.g. directly to /var/log)?</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div lang="EN-US"><div class="gmail-m_-4913605907034622546WordSection1">
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">[Service]<u></u><u></u></p>
<p class="MsoNormal">Type=forking<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">ExecStart=/opt/sonarqube/bin/linux-x86-64/sonar.sh --debug start</p></div></div></blockquote><div><br></div><div>Does the script use `su`, `setsid`, `start-stop-daemon`, etc? Can you start the daemon without using sonar.sh at all? What does the --debug option mean for this script?</div><div><br></div><div>With Type=forking, when the initial ExecStart process (i.e. the shellscript) exits, the service is "started" and whatever child process is left over gets marked as the service's main process. If *that* process then exits, that counts as the whole service stopping. So in other words, the initial process should have as few layers of forking/backgrounding/daemonization as possible.</div><div><br></div></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr">Mantas Mikulėnas</div></div></div>