Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

cannot add HDP sandbox service pool to HDF sandbox streaming analytics manager due to 404 error

cannot add HDP sandbox service pool to HDF sandbox streaming analytics manager due to 404 error

New Contributor

I have successfully gone through the HDF Trucking IoT tutorial, and am attempting to do the "Real-Time Event Processing In NiFi, SAM, Schema Registry and SuperSet" tutorial, and am not able to add the HDP sandbox cluster to the SAM service pools. When I auto-add http://sandbox-hdp.hortonworks.com:8080/api/v1/clusters/Sandbox it prompts me for credentials, and throws up a 404 not found error, but the spinner keeps working. If I refresh the page it shows the cluster, but says "No service". The HDP Ambari instance, and all it's services are running (at least the ones I need, some are maintenance mode from start, had to take Druid off maintenance mode and start). Also, when I hit http://sandbox-hdp.hortonworks.com:8080/api/v1/clusters/Sandbox in my browser I can see a bunch of JSON describing the cluster, so it appears to be working fine. I have already enabled native CDA, and the proxy and HDF containers are all running fine:

# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES eb80d2f492b4 hortonworks/sandbox-proxy:1.0 "nginx -g 'daemon of…" 19 minutes ago Up 19 minutes 0.0.0.0:1080->1080/tcp, 0.0.0.0:1100->1100/tcp, 0.0.0.0:1111->1111/tcp, 0.0.0.0:1988->1988/tcp, 0.0.0.0:2100->2100/tcp, 0.0.0.0:2181-2182->2181-2182/tcp, 0.0.0.0:2201-2202->2201-2202/tcp, 0.0.0.0:2222->2222/tcp, 0.0.0.0:3000->3000/tcp, 0.0.0.0:4040->4040/tcp, 0.0.0.0:4200->4200/tcp, 0.0.0.0:4242->4242/tcp, 0.0.0.0:4557->4557/tcp, 0.0.0.0:5007->5007/tcp, 0.0.0.0:5011->5011/tcp, 0.0.0.0:6001->6001/tcp, 0.0.0.0:6003->6003/tcp, 0.0.0.0:6008->6008/tcp, 0.0.0.0:6080->6080/tcp, 0.0.0.0:6188->6188/tcp, 0.0.0.0:6627->6627/tcp, 0.0.0.0:6667->6667/tcp, 0.0.0.0:7777->7777/tcp, 0.0.0.0:7788->7788/tcp, 0.0.0.0:8000->8000/tcp, 0.0.0.0:8005->8005/tcp, 0.0.0.0:8020->8020/tcp, 0.0.0.0:8032->8032/tcp, 0.0.0.0:8040->8040/tcp, 0.0.0.0:8042->8042/tcp, 0.0.0.0:8080-8082->8080-8082/tcp, 0.0.0.0:8086->8086/tcp, 0.0.0.0:8088->8088/tcp, 0.0.0.0:8090-8091->8090-8091/tcp, 0.0.0.0:8188->8188/tcp, 0.0.0.0:8443->8443/tcp, 0.0.0.0:8744->8744/tcp, 0.0.0.0:8765->8765/tcp, 0.0.0.0:8886->8886/tcp, 0.0.0.0:8888-8889->8888-8889/tcp, 0.0.0.0:8983->8983/tcp, 0.0.0.0:8993->8993/tcp, 0.0.0.0:9000->9000/tcp, 0.0.0.0:9088-9091->9088-9091/tcp, 0.0.0.0:9995-9996->9995-9996/tcp, 0.0.0.0:10000-10001->10000-10001/tcp, 0.0.0.0:10015-10016->10015-10016/tcp, 0.0.0.0:10500->10500/tcp, 0.0.0.0:10502->10502/tcp, 0.0.0.0:11000->11000/tcp, 0.0.0.0:12049->12049/tcp, 0.0.0.0:12200->12200/tcp, 0.0.0.0:15000->15000/tcp, 0.0.0.0:15002->15002/tcp, 0.0.0.0:15500->15500/tcp, 0.0.0.0:16000->16000/tcp, 0.0.0.0:16010->16010/tcp, 0.0.0.0:16020->16020/tcp, 0.0.0.0:16030->16030/tcp, 0.0.0.0:18080-18081->18080-18081/tcp, 0.0.0.0:19888->19888/tcp, 0.0.0.0:21000->21000/tcp, 0.0.0.0:33553->33553/tcp, 0.0.0.0:39419->39419/tcp, 0.0.0.0:42111->42111/tcp, 0.0.0.0:50070->50070/tcp, 0.0.0.0:50075->50075/tcp, 0.0.0.0:50079->50079/tcp, 0.0.0.0:50095->50095/tcp, 0.0.0.0:50111->50111/tcp, 0.0.0.0:60000->60000/tcp, 0.0.0.0:60080->60080/tcp, 0.0.0.0:61080->61080/tcp, 80/tcp, 0.0.0.0:61888->61888/tcp sandbox-proxy 68217bb995b6 hortonworks/sandbox-hdp:2.6.5 "/usr/sbin/init" 12 hours ago Up 11 hours 22/tcp, 4200/tcp, 8080/tcp sandbox-hdp a3d7d72be13e hortonworks/sandbox-hdf:3.1.1 "/usr/sbin/init" 13 hours ago Up 11 hours 22/tcp, 4200/tcp, 8080/tcp sandbox-hdf

I am running Ubuntu 16.06 in AWS with docker 18.06.1-ce.

Any ideas?...I haven't even found a way to view the SAM logs to try to diagnose problems.