[
https://issues.apache.org/jira/browse/JENA-1020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne resolved JENA-1020.
---------------------------------
Resolution: Fixed
Assignee: Andy Seaborne
Fix Version/s: Fuseki 2.3.1
> /etc/init.d/fuseki looks in wrong location for .pid when responding to
> 'service fuseki status'
> ----------------------------------------------------------------------------------------------
>
> Key: JENA-1020
> URL: https://issues.apache.org/jira/browse/JENA-1020
> Project: Apache Jena
> Issue Type: Bug
> Components: Fuseki
> Affects Versions: Fuseki 2.3.0
> Environment: Ubuntu
> Reporter: Chris
> Assignee: Andy Seaborne
> Priority: Trivial
> Labels: easyfix, easytest, patch
> Fix For: Fuseki 2.3.1
>
> Original Estimate: 10m
> Remaining Estimate: 10m
>
> I see in /etc/init.d/fuseki (just 'fuseki' in the tarball)'s comment block
> that the pid file is placed in $FUSEKI_RUN. The script correctly puts the
> pidfile in $FUSEKI_RUN.
> Way down in the run() function - in the 'status' block of the case statement
> the script looks for the pidfile in in /var/run, /usr/var/run, $FUSEKI_HOME
> and /tmp. I suspect $FUSEKI_HOME is meant to be $FUSEKI_RUN (Also,
> $FUSEKI_PID may provide a shortcut in place of findFile, as it's previously
> defined as $FUSEKI_RUN/fuseki.pid).
> Having $FUSEKI_RUN set to something other that $FUSEKI_HOME causes calls to
> 'service fuseki status' to return ' * Fuseki is not running', even though
> fuseki can be accessed via its web interface, shutdown via the CLI, or seen
> in the the process space via the PID in its pidfile.
> The suggested modification ($FUSEKI_HOME -> FUSEKI_RUN) worked on my
> installation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
