Support Questions
Find answers, ask questions, and share your expertise
Check out our newest addition to the community, the Cloudera Innovation Accelerator group hub.

Can't install Apache NiFi on a HDP cluster with Ambari

Hey there,

I'm trying to install Apache NiFi on a HDP 2.6 cluster with Ambari. For that I followed the documentation at Now that I want to instal NiFi I get the error that "Skipping stack-select on NIFI because it does not exist in the stack-select package structure"

Here are the log files for the installation: output-1056.txt errors-1056.txt

I really don't know what to do right now, so I would appreciate any help.

Best regards,



Super Collaborator

It looks like it created the directory structure for the service.

2017-12-07 16:43:16,148 - Installing package nifi_3_0_* ('/usr/bin/yum -d 0 -e 0 -y install 'nifi_3_0_*'')
2017-12-07 16:44:58,917 - Directory['/usr/hdf/current/nifi'] {'owner': 'nifi', 'group': 'nifi', 'create_parents': True, 'recursive_ownership': True}
2017-12-07 16:44:58,918 - Creating directory Directory['/usr/hdf/current/nifi'] since it doesn't exist.
2017-12-07 16:44:58,918 - Following the link /usr/hdf/current/nifi to /usr/hdf/ to create the directory
2017-12-07 16:44:58,919 - Changing owner for /usr/hdf/ from 0 to nifi
2017-12-07 16:44:58,919 - Changing group for /usr/hdf/ from 0 to nifi
2017-12-07 16:44:58,921 - Directory['/var/run/nifi'] {'owner': 'nifi', 'create_parents': True, 'group': 'nifi', 'recursive_ownership': True}
2017-12-07 16:44:58,921 - Directory['/var/log/nifi'] {'owner': 'nifi', 'create_parents': True, 'group': 'nifi', 'recursive_ownership': True}
2017-12-07 16:44:58,922 - Directory['/var/lib/nifi'] {'owner': 'nifi', 'create_parents': True, 'group': 'nifi', 'recursive_ownership': True}
2017-12-07 16:44:58,922 - Directory['/var/lib/nifi/database_repository'] {'owner': 'nifi', 'create_parents': True, 'group': 'nifi', 'recursive_ownership': True}
2017-12-07 16:44:58,923 - Directory['/var/lib/nifi/flowfile_repository'] {'owner': 'nifi', 'create_parents': True, 'group': 'nifi', 'recursive_ownership': True}
2017-12-07 16:44:58,923 - Directory['/var/lib/nifi/provenance_repository'] {'owner': 'nifi', 'create_parents': True, 'group': 'nifi', 'recursive_ownership': True}
2017-12-07 16:44:58,924 - Directory['/usr/hdf/current/nifi/conf'] {'owner': 'nifi', 'create_parents': True, 'group': 'nifi', 'recursive_ownership': True}
2017-12-07 16:44:58,924 - Creating directory Directory['/usr/hdf/current/nifi/conf'] since it doesn't exist.
2017-12-07 16:44:58,924 - Changing owner for /usr/hdf/current/nifi/conf from 0 to nifi
2017-12-07 16:44:58,924 - Changing group for /usr/hdf/current/nifi/conf from 0 to nifi

It looks like you are using a custom local repository? Have you tried using the Hortonworks ones?

Using the public repositories is sadly no possibility in my environment. But I also used the local ones on my HDP cluster without any problems, so I really don't think that the problem lies there.

Super Collaborator

@Markus Wilhelm Well, the error does not say the installation of NiFi failed. Maybe the service won't show up in Ambari, but are you able to start NiFi on the server you installed it to?

I checked again and it seems NiFi is installed and works. This still leaves the problem that it doesn't show up in Ambari though. Any suggestions what I could do to add it in Ambari?

Super Collaborator

@Markus Wilhelm, Since NiFi is installed on the machine itself, you might be able to post the service to the Ambari database

Something like this

POST ambari-server:8080/clusters/:clusterName/services/NIFI

Super Collaborator

@Markus Wilhelm, That API call tells the Ambari server that it has a service, but yes, now you'll need to add the nifi component.

Some combination of these requests should be able to show / add that...

I think the Nifi component name is NIFI_MASTER,

Somehow I can't answer your last post. I managed to add the NiFi service to the Ambari web view, but how do I configure it to actually use it with the web view? Currently I can't start / stop the service or configure it, probably because Ambari doesn't know on which machine in the cluster it runs?