[
https://issues.apache.org/jira/browse/JENA-789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14305010#comment-14305010
]
ASF GitHub Bot commented on JENA-789:
-------------------------------------
GitHub user stain opened a pull request:
https://github.com/apache/jena/pull/27
JENA-789: Fixes FUSEKI_USER breaking logging
Q: Are there other of the FUSEKI_* variables that needs to be passed
through?
Fixes [JENA-789](https://issues.apache.org/jira/browse/JENA-789)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/stain/jena JENA-789-fuseki-non-root
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/jena/pull/27.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #27
----
commit 00e6b1254f2684f5e8ba3818e346e15cff5844ea
Author: Stian Soiland-Reyes <[email protected]>
Date: 2015-02-04T12:18:18Z
JENA-789: Fixes FUSEKI_USER breaking logging
Are there other of the FUSEKI_* variables that needs
to be passed through?
----
> Permission and pages not found errors when fuseki is started non-root
> ---------------------------------------------------------------------
>
> Key: JENA-789
> URL: https://issues.apache.org/jira/browse/JENA-789
> Project: Apache Jena
> Issue Type: Bug
> Components: Fuseki
> Affects Versions: Fuseki 1.1.0
> Environment: OEL Linux 5
> Reporter: Nicholas Sushkin
> Attachments: jena-789.patch
>
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> Multiple issues in fuseki init script when fuseki is started as a non-root
> user (non-empty $FUSEKI_USER)
> 1. When $FUSEKI_DATA_DIR does not exist, it's created as root by the init
> script and $FUSEKI_USER cannot open the database with FileException
> com.hp.hpl.jena.tdb.base.file.FileException: Failed to open:
> <$FUSEKI_DATA_DIR>/node2id.idn (mode=rw)
>
> at
> com.hp.hpl.jena.tdb.base.file.ChannelManager.open$(ChannelManager.java:82)
>
> 2. When $FUSEKI_HOME is not the same as the home directory of $FUSEKI_USER,
> fuseki is unable to find static content, giving warnings such as
> WARN No such directory for static content: /home/fuseki/.
> WARN You may need to set the --pages or --home option to configure static
> content correctly
> WARN No pages directory - ./pages
> 3. When run as non-root, the server output is not saved in
> $FUSEKI_LOGS_STDERROUT
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
