Created 01-09-2018 08:48 PM
I Followed these steps :
First i took a server(Cent OS 6) from Google Cloud in Asia South reagion. and Executed these commands :
Done! Cloudera manager installed Successfully.
But when I am trying to access http://my_public_ip:7180/ then getting timed out error.
Also i waited for almost an hour after installing cloudera(for startup settings). but again same response.
Created on 01-10-2018 07:37 PM - edited 01-10-2018 07:38 PM
Hello Gaurav,
Please share the output of curl on http://my_public_ip:7180 from cm host itself.
And tcpdump from the source host.
Created 03-28-2018 02:50 AM
Created 03-28-2018 07:35 AM
Created 03-28-2018 11:37 AM
I changed the inbound rules to allow port 7180
still no luck.
Created 03-28-2018 12:39 PM
If your browser cannot connect to ip-172-31-44-224.us-west-2.compute.internal:7180, then make sure that curl can connect You tested with curl, but used "localhost" so the test was not as close a comparison as one would like.
Make sure that the ip-172-31-44-224.us-west-2.compute.internal hostname can be resolved to a proper IP address and that your host has a route to that IP address.
WireShark is a great tool decoding packets sent over the wire and can give you perspective about where the problem may be occurring
I'm not saying that it isn't firewalls or otherwise, but it would be good to clarify what is stopping the client from reaching the server host/port
Created 03-28-2018 12:58 PM
i tried replacing the localhost with the machine name and still works
[ec2-user@ip-172-31-44-224 ~]$ curl -i http://ip-172-31-44-224.us-west-2.compute.internal:7180
HTTP/1.1 200 OK
Expires: Thu, 01-Jan-1970 00:00:00 GMT
Set-Cookie: CLOUDERA_MANAGER_SESSIONID=1h54xzygxge381p2g16fyh0wbh;Path=/;HttpOnly
Content-Type: text/html; charset=utf-8
Last-Modified: Wed, 07 Feb 2018 17:44:18 GMT
Content-Length: 63
Accept-Ranges: bytes
Cache-Control: max-age=3600,public
Server: Jetty(6.1.26.cloudera.4)
<head><meta http-equiv="refresh" content="0;url=/cmf/"></head>
[ec2-user@ip-172-31-44-224 ~]$ curl -i -u 'admin:admin' http://ip-172-31-44-224.us-west-2.compute.internal:7180/api/v1/tools/echo
HTTP/1.1 200 OK
Expires: Thu, 01-Jan-1970 00:00:00 GMT
Set-Cookie: CLOUDERA_MANAGER_SESSIONID=1t1pb4wgxqsl61ix0fwo3c0xs5;Path=/;HttpOnly
Content-Type: application/json
Date: Wed, 28 Mar 2018 19:57:30 GMT
Transfer-Encoding: chunked
Server: Jetty(6.1.26.cloudera.4)
{
"message" : "Hello, World!"
}[ec2-user@ip-172-31-44-224 ~]$
Created 03-28-2018 05:20 PM
So it does sound like the host is not accessible from your browser's network.
Packet sniffing is a good way to help determine what is going on.
EC2 support might know more. This is an issue about network and packets and the cloud config, so talking to those who run it may help.
Created 03-28-2018 05:24 PM
Created 03-28-2018 05:28 PM
No worries at all... we are just glad you got it working. Nothing more frustrating then being stuck like you were!