Curl Response from Cloudera Manager Host. [root@ip-172-31-24-21 etc]# curl -u admin:admin http://ec2-18-144-47-252.us-west-1.compute.amazonaws.com:7180 -v * About to connect() to ec2-18-144-47-252.us-west-1.compute.amazonaws.com port 7180 (#0) * Trying 172.31.24.21... * Connected to ec2-18-144-47-252.us-west-1.compute.amazonaws.com (172.31.24.21) port 7180 (#0) * Server auth using Basic with user 'admin' > GET / HTTP/1.1 > Authorization: Basic YWRtaW46YWRtaW4= > User-Agent: curl/7.29.0 > Host: ec2-18-144-47-252.us-west-1.compute.amazonaws.com:7180 > Accept: */* > < HTTP/1.1 200 OK < Date: Tue, 22 Oct 2019 21:55:52 GMT < Set-Cookie: CLOUDERA_MANAGER_SESSIONID=node0124m6i5b2ijzlyafpyc8wm6u724.node0;Path=/;HttpOnly < Expires: Thu, 01 Jan 1970 00:00:00 GMT < Last-Modified: Fri, 19 Jul 2019 06:26:10 GMT < Content-Type: text/html;charset=utf-8 < Accept-Ranges: bytes < Cache-Control: max-age=3600,public < X-XSS-Protection: 1; mode=block < X-Frame-Options: SAMEORIGIN < X-Content-Type-Options: nosniff < Content-Length: 63 < <head><meta http-equiv="refresh" content="0;url=/cmf/"></head> * Connection #0 to host ec2-18-144-47-252.us-west-1.compute.amazonaws.com left intact Curl Response from some other machine. * Rebuilt URL to: http://ec2-18-144-47-252.us-west-1.compute.amazonaws.com:7180/ * Trying 18.144.47.252... * TCP_NODELAY set * Connection failed * connect to 18.144.47.252 port 7180 failed: Operation timed out * Failed to connect to ec2-18-144-47-252.us-west-1.compute.amazonaws.com port 7180: Operation timed out * Closing connection 0 curl: (7) Failed to connect to ec2-18-144-47-252.us-west-1.compute.amazonaws.com port 7180: Operation timed out I have all the necessary ports open on the CM Host machine for HTTP/HTTPS and also the 7180 port.
... View more
