You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "Joachim Neubert (JIRA)" <ji...@apache.org> on 2018/03/22 15:22:00 UTC
[jira] [Created] (JENA-1511) Stopping systemd service for Fuseki
Joachim Neubert created JENA-1511:
-------------------------------------
Summary: 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
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.
Ping [~osma] for this one, too.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)