[
https://issues.apache.org/jira/browse/JENA-1511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16416977#comment-16416977
]
ASF subversion and git services commented on JENA-1511:
-------------------------------------------------------
Commit ab9c843905e350fad2e5d932ef1c8ccb868cae12 in jena's branch
refs/heads/master from [~osma]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=ab9c843 ]
JENA-1511: consider 143 (killed by SIGTERM) a succesful exit status for the
fuseki service
> 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)
