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 14:02:00 UTC

[jira] [Created] (JENA-1510) Add logging to systemd unit file for Fuseki

Joachim Neubert created JENA-1510:
-------------------------------------

             Summary: Add logging to systemd unit file for Fuseki
                 Key: JENA-1510
                 URL: https://issues.apache.org/jira/browse/JENA-1510
             Project: Apache Jena
          Issue Type: Brainstorming
          Components: Fuseki
            Reporter: Joachim Neubert


Currently, the fuseki.service logs to journalctl, which is the systemd default mechanism, and not to any fuseki-specific log file. Since I want to have (and probably keep) such files, I've followed a [solution on stackoverflow|https://stackoverflow.com/questions/37585758/how-to-redirect-output-of-systemd-service-to-a-file] and added 

{code}
StandardOutput=syslog
StandardError=syslog
SyslogIdentifier=fuseki
{code}

which logs to rsyslog. A /etc/rsyslog.d/fuseki.conf file then defines the actual log location:

{code}
if $programname == 'fuseki' then /var/log/fuseki/stderrout.log
if $programname == 'fuseki' then stop
{code}

which worked nicely. I suppose it could be useful for others, too. What do you think?

Ping [~osma] who created the systemd unit file (JENA-1501).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)