@zblanco actually no...wasn't aware of it until you pointed it out ... View more

@Mukesh Kumar just had a chance to look at your logs. Seems like when Ambari attempted to download the zip, there was a problem and the zip is corrupted. You can double check your sandbox has internet access (eg. by pinging hortonworks.com) and run below command to remove the incomplete download. Then follow the steps here to remove the failed install in Ambari and repeat the install steps here rm -f /tmp/nifi-*zip ... View more

@Peter Kim great! Please mark the answer as accepted to close the issue...so it doesn't show up on our list of open questions ... View more

@Peter Kim Based on the log and lsof output, it seems zeppelin server is up and running. If its not opening in the browser, you may need to disable firewalls. Can you ensure you can ping the host running zeppelin from your local host? Also try to telnet into port 9995 from your local host. ... View more

@Peter Kim could you check in the zeppelin logs (under /var/log/zeppelin*) if any other errors appeared this time? In the earlier log it was complaining about the screenshots subdir. If you already removed it and tried restarting Zeppelin and it still did not come up, there probably another problem as well. There was another recent fix that went in which maybe causing the problem now: https://github.com/hortonworks-gallery/zeppelin-notebooks/pull/19/commits/027f4ad29f71289121949eedd0c88f3a96439f64 ... View more

@Timothy Spann Ok finally got a chance to try this out. Couple of things: 1. You can remove failed installs easily in Ambari 2.4 via the UI by clicking on Nifi > Service Actions > Delete 2. Nifi is not causing the popup about HDFS/YARN configs. If you try to add ANY service it will give you the same warnings. Why? Because on sandbox they have setup their own configs to get the VM to perform on single node env, and Ambari is warning about those. I think it should be safe to ignore those. 3. Installing Nifi via Ambari was failing because of some Ambari API changes in 2.4. So any service definition written prior to 2.4 will probably fail without making some updates. I have now updated the code on the github now so should work on both Ambari 2.4, as well as earlier versions as well. So to try it out, once you have imported the 2.5 sandbox, just run the below commands and proceed with the install as usual (via 'Add service' wizard): VERSION=`hdp-select status hadoop-client | sed 's/hadoop-client - \([0-9]\.[0-9]\).*/\1/'` rm -rf /var/lib/ambari-server/resources/stacks/HDP/$VERSION/services/NIFI sudo git clone https://github.com/abajwa-hw/ambari-nifi-service.git /var/lib/ambari-server/resources/stacks/HDP/$VERSION/services/NIFI service ambari restart Once installed, you can access Nifi UI on port 9090 (there is already a port forwarding rule on the VM). Also note that by default you will not see any metrics for Nifi (because Ambari Metrics is down) Screenshots @rmolina fyi...when you build your next sandbox, you should get the updated Nifi service definition automatically. So with future 2.5 sandboxes, the above manual workaround will no longer be required ... View more

+@rmolina @Timothy Spann: What error does it fail with? Sandbox team had included the demo Nifi service definition (https://github.com/abajwa-hw/ambari-nifi-service) on 2.4 sandbox to make it easy to install Nifi for the tutorials In 2.4 the service definition was under below: /var/lib/ambari-server/resources/stacks/HDP/2.4/services/NIFI/ Can you check if NIFI dir is present under both /var/lib/ambari-server/resources/stacks/HDP/2.4/services/ and /var/lib/ambari-server/resources/stacks/HDP/2.5/services directories? If so, remove the 2.4 version and restart ambari-server before installing ... View more