- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Float this Question for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Provenance repository NoSuchFileException: /usr/hdf/current/nifi/conf/sensitive.key
- Labels:
-
Apache NiFi
-
Cloudera DataFlow (CDF)
Created ‎10-23-2017 01:00 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have a HDF cluster, 1 ambari server and 3 Nifi nodes. Some days ago, the cluster shutted down automatically. Reviewing the logs, find this error Provenance Repository Rollover Thread-1, NoSuchFileException: /usr/hdf/current/nifi/conf/sensitive.key. After reviewing in the 3 nodes, can't find the file. We stopped the service, restarted, not work. Restarted one by one, node 1 fine, node 2 fine, node 3 fine, shut down node 1, after a while node 2 too. We found some answers in forum and applied the propose solution, worked for a day, today the service is down again. Any clues?
Regards
Created ‎10-23-2017 01:49 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You are running into https://issues.apache.org/jira/browse/NIFI-4187
There currently is no HDF release that includes this fix. What is happening is something is causing the NIFi process to die. The NiFi bootstrap detects that the NiFi process has hung or died and tries to restart it where it runs in to the above BUG. I would search you NiFi logs for perhaps some OOM error that may have have caused the NiFi process to die.
Created ‎10-23-2017 01:49 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You are running into https://issues.apache.org/jira/browse/NIFI-4187
There currently is no HDF release that includes this fix. What is happening is something is causing the NIFi process to die. The NiFi bootstrap detects that the NiFi process has hung or died and tries to restart it where it runs in to the above BUG. I would search you NiFi logs for perhaps some OOM error that may have have caused the NiFi process to die.
