[
https://issues.apache.org/jira/browse/NIFI-3353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Villard resolved NIFI-3353.
----------------------------------
Resolution: Feedback Received
Apache NiFi 1.x is no longer maintained and no new release is planned on the
1.x release line. Marking as resolved as part of a cleanup operation. Please
open a new one with an updated description if this is still relevant for NiFi
2.x.
> nifi-bootstrap.log not written to if using non-standard conf.dir
> ----------------------------------------------------------------
>
> Key: NIFI-3353
> URL: https://issues.apache.org/jira/browse/NIFI-3353
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.1.1
> Reporter: Joe Gresock
> Priority: Minor
>
> To reproduce this, replace "./conf" with "/opt/nifi/data/conf" (or some other
> directory that's not in the nifi installation dir) in bootstrap.conf, and
> specify the same absolute path in the nifi.properties file as well, for all
> properties that use the ./conf directory. Move all conf files to the
> /opt/nifi/data/conf directory.
> In order to get this configuration to start up, you also apparently need
> $NIFI_HOME/conf/bootstrap.conf to be a symbolic link to the actual location
> of that file (in /opt/nifi/data/conf, in this case). E.g.:
> {code}
> $ ls -al $NIFI_HOME/conf
> lrwxrwxrwx. 1 root root 19 Jan 12 13:27 bootstrap.conf ->
> /opt/nifi/data/conf/bootstrap.conf
> {code}
> Starting up nifi shows that the nifi-bootstrap.log is created but not written
> to, although all other log files are successfully written to.
> I was able to work around this by simply linking the entire $NIFI_HOME/conf
> directory to /opt/nifi/data/conf:
> {code}
> $ ls -al $NIFI_HOME
> drwxr-xr-x. 2 nifi nifi 4096 Dec 23 10:58 bin
> lrwxrwxrwx. 1 root root 19 Jan 12 13:27 conf -> /opt/nifi/data/conf
> ...
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
