[ https://issues.apache.org/jira/browse/JENA-1511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16416973#comment-16416973 ]
Osma Suominen commented on JENA-1511: ------------------------------------- After some investigation I found that it's normal for Java processes to exit with status 143 when they are killed by SIGTERM. See e.g. https://stegard.net/2016/08/gracefully-killing-a-java-process-managed-by-systemd/ So I think adding the {{SuccessExitStatus=143}} directive makes sense. I don't know why it wasn't necessary on my Ubuntu systems and don't have time to investigate now. But adding it shouldn't do any harm. > 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)