Created 09-11-2016 08:16 AM
I am adding extra aws nodes using cloudera manager hosted on VM locally. However, scm server hostname is pointing to my broadband instead of the hostname where cloudera magager is running and giving error as shown in image below:
Below are entries of /etc/resolv.conf:
# Generated by NetworkManager
search cloudera
nameserver 192.168.0.1
Created 09-19-2016 09:54 PM
Hello,
I am pretty sure that the $SSH_CLIENT environment variable governs the IP address and then the following call is used to arrive at a FQDN for Cloudera Manager:
Then, "host -t PTR <IP>" is run to get the FQDN
For instance, in my testbed:
#echo $SSH_CLIENT
10.17.102.53 65520 22
#host -t PTR 10.17.102.53
53.102.17.10.in-addr.arpa domain name pointer host-10-17-102-53.coe.cloudera.com.
The last value is chosen as the Cloudera Manager hostname.
I'm not sure if this helps you out, but if you can't figure this out, I recommend adding the host manually:
Created 02-15-2017 03:34 PM
The CM server listens (for the agents) on port 7182 so you need to add that to your security group in AWS:
Created 04-26-2020 09:09 PM
Thanks so much, have same problem and was solved by adding 7182 to EC2 security group.