Github user alopresto commented on the issue:
https://github.com/apache/nifi/pull/1247
There is an issue in `master` where the `nifi-app.log` is spammed with the
following lines:
```
2016-11-18 17:39:14,053 ERROR [Cleanup Archive for default]
o.a.n.c.repository.FileSystemRepository Failed to cleanup archive for container
default due to java.nio.file.NoSuchFileException:
/Users/alopresto/Workspace/nifi/nifi-assembly/target/nifi-1.1.0-SNAPSHOT-bin/nifi-1.1.0-SNAPSHOT/content_repository
2016-11-18 17:39:15,055 ERROR [Cleanup Archive for default]
o.a.n.c.repository.FileSystemRepository Failed to cleanup archive for container
default due to java.nio.file.NoSuchFileException:
/Users/alopresto/Workspace/nifi/nifi-assembly/target/nifi-1.1.0-SNAPSHOT-bin/nifi-1.1.0-SNAPSHOT/content_repository
```
Running an unsecured instance has this message but still loads the app
fine, but with keystores configured, the application fails to start.
```
hw12203:...space/nifi/nifi-assembly/target/nifi-1.1.0-SNAPSHOT-bin/nifi-1.1.0-SNAPSHOT
(pr1247) alopresto
ð 404s @ 17:39:21 $ ./bin/nifi.sh status
Java home: /Users/alopresto/.jenv/versions/1.8
NiFi home:
/Users/alopresto/Workspace/nifi/nifi-assembly/target/nifi-1.1.0-SNAPSHOT-bin/nifi-1.1.0-SNAPSHOT
Bootstrap Config File:
/Users/alopresto/Workspace/nifi/nifi-assembly/target/nifi-1.1.0-SNAPSHOT-bin/nifi-1.1.0-SNAPSHOT/conf/bootstrap.conf
2016-11-18 17:40:05,146 INFO [main] org.apache.nifi.bootstrap.Command
Apache NiFi is not running
hw12203:...space/nifi/nifi-assembly/target/nifi-1.1.0-SNAPSHOT-bin/nifi-1.1.0-SNAPSHOT
(pr1247) alopresto
ð 47s @ 17:40:08 $
```
At this point I can't verify the restricted processor changes because it
requires a secured instance with multiple user accounts. The bug needs to be
fixed in `master` first. I have filed
[NIFI-3069](https://issues.apache.org/jira/browse/NIFI-3069) to document and
address this.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
