Did you deploy the custom cluster topology? A quick way to test is to try changing cluster1 to default in your curl request and see if it works. It sounds like knox can't find your cluster.
On Thu, Jul 2, 2015 at 2:27 PM, Aneela Saleem <[email protected]> wrote: > ${KNOX_HOME}/knox/conf/topologies has the following contents: > > admin.xml cluster1.xml README sandbox.xml > > cluster1.xml is the topology descriptor file created by me. > > cluster1.xml has following contents: > > <topology> > <gateway> > </gateway> > <service> > <role>NAMENODE</role> > <url>hdfs:// namenode-host :8020</url> > </service> > > <service> > <role>JOBTRACKER</role> > <url>rpc:// jobtracker-host :8050</url> > </service> > > <service> > <role>RESOURCEMANAGER</role> > <url>http://red3:8088/ws</url> > </service> > > <service> > <role>WEBHDFS</role> > <url>http://localhost:50070/webhdfs</url> > </service> > > <service> > <role>WEBHCAT</role> > <url>http://webcat-host :50111/templeton</url> > </service> > > <service> > <role>OOZIE</role> > <url>http://oozie-host :11000/oozie</url> > </service> > > <service> > <role>WEBHBASE</role> > <url>http://webhbase-host :60080</url> > </service> > </topology> > > > admin.xml has default contents. I did not make any changes. > > > > On Thu, Jul 2, 2015 at 11:15 PM, Steve Howard <[email protected]> > wrote: > >> To be clear, the error isn't hostname not found (that just means it >> wasn't in the DNS cache on your computer), it's that the URL can't be found >> by the knox server. >> >> Can you post the contents of your ${KNOX_HOME}/knox/conf/topologies >> directory? >> >> On Thu, Jul 2, 2015 at 1:50 PM, Aneela Saleem <[email protected]> >> wrote: >> >>> Hi, >>> >>> I'm trying to connect to HDFS through Knox gateway. I run the following >>> command: >>> >>> curl -vk >>> https://localhost:8443/gateway/cluster1/WEBHDFS/v1?op=GETHOMEDIRECTORY >>> >>> when i run this command i get the following error: >>> >>> * Hostname was NOT found in DNS cache >>> * Trying 127.0.0.1... >>> * Connected to localhost (127.0.0.1) port 8443 (#0) >>> * successfully set certificate verify locations: >>> * CAfile: none >>> CApath: /etc/ssl/certs >>> * SSLv3, TLS handshake, Client hello (1): >>> * SSLv3, TLS handshake, Server hello (2): >>> * SSLv3, TLS handshake, CERT (11): >>> * SSLv3, TLS handshake, Server key exchange (12): >>> * SSLv3, TLS handshake, Server finished (14): >>> * SSLv3, TLS handshake, Client key exchange (16): >>> * SSLv3, TLS change cipher, Client hello (1): >>> * SSLv3, TLS handshake, Finished (20): >>> * SSLv3, TLS change cipher, Client hello (1): >>> * SSLv3, TLS handshake, Finished (20): >>> * SSL connection using ECDHE-RSA-DES-CBC3-SHA >>> * Server certificate: >>> * subject: C=US; ST=Test; L=Test; O=Hadoop; OU=Test; CN=localhost >>> * start date: 2015-06-29 21:39:18 GMT >>> * expire date: 2016-06-28 21:39:18 GMT >>> * issuer: C=US; ST=Test; L=Test; O=Hadoop; OU=Test; CN=localhost >>> * SSL certificate verify result: self signed certificate (18), >>> continuing anyway. >>> > GET /gateway/cluster1/WEBHDFS/v1?op=GETHOMEDIRECTORY HTTP/1.1 >>> > User-Agent: curl/7.35.0 >>> > Host: localhost:8443 >>> > Accept: */* >>> > >>> < HTTP/1.1 404 Not Found >>> < Content-Length: 0 >>> * Server Jetty(8.1.14.v20131031) is not blacklisted >>> < Server: Jetty(8.1.14.v20131031) >>> < >>> * Connection #0 to host localhost left intact >>> >>> >>> >>> Can anyone please help me in tackling this issue? >>> >> >> >
