- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Float this Question for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Apache NiFi: Processor configuration url issue
- Labels:
-
Apache NiFi
Created on ‎12-20-2019 12:28 PM - edited ‎12-20-2019 12:54 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi
I've installed Apache NiFi through Apache Ambari on my HDP: Stack and Versions->Stack->Install... All configuration while installation I left to defaults. Installation was successful, however I was not able to access "http://sandbox-hdp.hortonworks.com:9090/nifi" out of box. So I added:
server {
listen 9090;
server_name sandbox-hdp.hortonworks.com;
location / {
proxy_pass http://sandbox-hdp:9090;
}
}
to my "HDP_3.0.1_docker-deploy-scripts_18120587fc7fb\sandbox\proxy\conf.d\http-hdp.conf" file and it started working properly. However now I have a problem when trying to change process configuration: when I click on Configure in process drop-down, I'm redirected to page with text "Please ensure the application is running and check the logs for any errors." In network I can see failed request to "http://sandbox-hdp:9090/nifi-api/processors/23ae900c-016f-1000-ffff-ffff8d289282". Any ideas how it can be fixed?
Thanks
Created ‎12-30-2019 07:30 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I found solution to my problem:
Change is required to "HDP_3.0.1_docker-deploy-scripts_18120587fc7fb\assets\generate-proxy-deploy-script.sh" file. I moved:
[9090]=9090
[9091]=9091
from section:
tcpPortsHDF=(
[2202]=22
[2182]=2181
[4557]=4557
....
)
to section:
tcpPortsHDP=(
[12049]=2049
[2201]=22
[2222]=22
[1100]=1100
....
[9090]=9090
[9091]=9091
...
)
Then I ran again "HDP_3.0.1_docker-deploy-scripts_18120587fc7fb\docker-deploy-hdp30.sh". Now it works.
Created ‎12-24-2019 03:15 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Please check carefully the documentation you are following. I don't think you are expected to change the deployment configuration, perhaps you need to add something on your local machine. (e.g. in /etc/hosts)
- Dennis Jaheruddin
If this answer helped, please mark it as 'solved' and/or if it is valuable for future readers please apply 'kudos'.
Created ‎12-26-2019 07:03 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It's part of my "c:\Windows\System32\drivers\etc\hosts" file. I followed "https://www.cloudera.com/tutorials/learning-the-ropes-of-the-hdp-sandbox.html#admin-password-reset" documentation:
127.0.0.1 localhost sandbox-hdp.hortonworks.com sandbox-hdf.hortonworks.com
# Added by Docker Desktop
10.224.206.135 host.docker.internal
10.224.206.135 gateway.docker.internal
# To allow the same kube context to work on the host and the container:
127.0.0.1 kubernetes.docker.internal
# End of section
Created ‎12-30-2019 07:30 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I found solution to my problem:
Change is required to "HDP_3.0.1_docker-deploy-scripts_18120587fc7fb\assets\generate-proxy-deploy-script.sh" file. I moved:
[9090]=9090
[9091]=9091
from section:
tcpPortsHDF=(
[2202]=22
[2182]=2181
[4557]=4557
....
)
to section:
tcpPortsHDP=(
[12049]=2049
[2201]=22
[2222]=22
[1100]=1100
....
[9090]=9090
[9091]=9091
...
)
Then I ran again "HDP_3.0.1_docker-deploy-scripts_18120587fc7fb\docker-deploy-hdp30.sh". Now it works.
