[
https://issues.apache.org/jira/browse/NIFI-717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14597918#comment-14597918
]
Mark Payne commented on NIFI-717:
---------------------------------
The issue appears to be due to the fact that when you run nifi, the NiFi
process is started with the working directory as the $NIFI_HOME directory. But
when you run it, the bootstrap's working directory is wherever you launch the
process from. So the value of "./logs" as the log directory can be problematic.
I don't see any way to configure it to use a path relative to the logback.xml
file that it reads the config from, though.
> nifi-bootstrap.log written to directory relative to current working directory
> -----------------------------------------------------------------------------
>
> Key: NIFI-717
> URL: https://issues.apache.org/jira/browse/NIFI-717
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Matt Gilman
> Priority: Minor
> Fix For: 0.2.0
>
>
> It appears that nifi-bootstrap.log is written to a directory that is relative
> to the current working directory. If NiFi is launched from outside $NIFI_HOME
> the logs end up outside of $NIFI_HOME. It is confusing since its configured
> to be written to logs/ just like nifi-app.log and nifi-user.log but it is
> written to logs/ in a different location.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
