[JENA-1020] /etc/init.d/fuseki looks in wrong location for .pid when responding to 'service fuseki status'

• Type: Bug
• Status: Closed
• Priority: Trivial
• Resolution: Fixed
• Affects Version/s: Fuseki 2.3.0
• Fix Version/s: Fuseki 2.3.1
• Component/s: Fuseki
• Labels: easyfix easytest patch

Environment

Ubuntu

• Flags: Patch
• Assignee: Andy Seaborne
• Reporter: Chris
• Created: 02/Sep/15 08:58
• Updated: 12/Dec/15 17:46
• Resolved: 22/Sep/15 12:12

Description

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.