[
https://issues.apache.org/jira/browse/JENA-1511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16409852#comment-16409852
]
Osma Suominen commented on JENA-1511:
-------------------------------------
I don't have the same problem on Ubuntu 16.04.
After running {{service fuseki stop}} I see this:
{noformat}
Mar 22 18:37:48 tester-os-kktest systemd[1]: Stopping LSB: Start Jena Fuseki at
boot time...
Mar 22 18:37:48 tester-os-kktest fuseki[2290]: * Stopping Fuseki:
Mar 22 18:37:49 tester-os-kktest fuseki[2290]: ...done.
Mar 22 18:37:49 tester-os-kktest systemd[1]: Stopped LSB: Start Jena Fuseki at
boot time.
{noformat}
And a subsequent {{service fuseki start}} gives me this:
{noformat}
Mar 22 18:38:00 tester-os-kktest systemd[1]: Starting LSB: Start Jena Fuseki at
boot time...
Mar 22 18:38:01 tester-os-kktest fuseki[2348]: * Starting Fuseki
Mar 22 18:38:03 tester-os-kktest fuseki[2348]: ...done.
Mar 22 18:38:03 tester-os-kktest fuseki[2348]: * STARTED Fuseki Thu Mar 22
18:38:03 EET 2018
Mar 22 18:38:03 tester-os-kktest fuseki[2348]: * PID=2363
{noformat}
With your {{/bin/kill}} recipe, does Fuseki shut down cleanly? My understanding
is that systemd does not wait for the daemon to shut down after the ExecStop
command, but will kill it forcefully it is still running after the defined
command has exited.
> Stopping systemd service for Fuseki
> -----------------------------------
>
> Key: JENA-1511
> URL: https://issues.apache.org/jira/browse/JENA-1511
> Project: Apache Jena
> Issue Type: Improvement
> Components: Fuseki
> Reporter: Joachim Neubert
> Priority: Minor
>
> Currently, the systemd service creates errors on exit:
> {code:java}
> Mar 22 16:08:32 ite-srv26 systemd[1]: Stopping Fuseki...
> Mar 22 16:08:33 ite-srv26 systemd[1]: fuseki.service: main process exited,
> code=exited, status=143/n/a
> Mar 22 16:08:33 ite-srv26 systemd[1]: Stopped Fuseki.
> Mar 22 16:08:33 ite-srv26 systemd[1]: Unit fuseki.service entered failed
> state.
> Mar 22 16:08:33 ite-srv26 systemd[1]: fuseki.service failed.
> {code}
> I found that adding the lines
> {code:java}
> ExecStop=/bin/kill $MAINPID
> SuccessExitStatus=143
> {code}
> to the unit file reduces that to
> {code:java}
> Mar 22 16:11:23 ite-srv26 systemd[1]: Stopping Fuseki...
> Mar 22 16:11:23 ite-srv26 systemd[1]: Stopped Fuseki.
> {code}
> I'm not sure however that sending SIGTERM is the correct/best way to stop the
> service, and if the exit code 143 wants to tell us something.
> Ping [~osma] for this one, too.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
