Good day! We actively use software configuration management (SCM, for example saltstack, ansible, puppet/etc), and we decide add new host to cluster Cloudera hadoop through this system. Our steps: 1. Add repo   cat /etc/apt/sources.list.d/cloudera-manager.list deb https://archive.cloudera.com/cm5/debian/jessie/amd64/cm/ jessie-cm5.13.0 contri     2. Install soft (cloudera-manager-daemons, cloudera-manager-agent)   3. Edit /etc/cloudera-scm-agent/config.ini   [General] # Hostname of the CM server. server_host=main.test.com 4. Start agent     After that we see that new host in cluster. Also I use this doc - https://www.cloudera.com/documentation/enterprise/5-13-x/topics/cm_mc_adding_hosts.html for checking our steps in SCM. But we run into some trouble   A. http://community.cloudera.com/t5/Cloudera-Manager-Installation/Bad-The-hostname-and-canonical-name-for-this-host-are-not/m-p/86905#M16122?eid=1&aid=1  - there I wrote some description about our error   B. CDH version didn't show in web interface: It is None   A and B issues aren't terrible, we can live with them   C. (blocking problem) We cann't add our recently host to any Service in Cloudera - any. Some Service - Instances - Add Role Instance - Select Hosts - in appeared list didn't show our new hosts (we add in this manner two hosts).   After all we remove this hosts from  cluster and added by hand through  web GUI and all OK.   During installation in web GUI I saw this: Installing selected parcels - this step we didn't do through our SCM. Parcles in good and bad hosts: bad_host# ls -lh /opt/cloudera/parcels total 0 good_host#ls -lh /opt/cloudera/parcels total 48K drwxr-xr-x 8 root root 4,0K окт 10 2016 ACCUMULO-1.7.2-5.5.0.ACCUMULO5.5.0.p0.8 lrwxrwxrwx 1 root root 14 фев 27 13:01 Anaconda -> Anaconda-4.0.0 drwxr-xr-x 18 root root 4,0K мар 29 2016 Anaconda-4.0.0 lrwxrwxrwx 1 root root 28 фев 27 13:01 CDH -> CDH-5.13.0-1.cdh5.13.0.p0.29 drwxr-xr-x 9 root root 4,0K окт 4 2017 CDH-5.13.0-1.cdh5.13.0.p0.29 lrwxrwxrwx 1 root root 20 фев 27 12:58 CDSW -> CDSW-1.4.0.p1.431664 drwxrwxr-x 3 root root 4,0K июн 20 2018 CDSW-1.4.0.p1.431664 lrwxrwxrwx 1 root root 16 фев 27 13:01 FLINK -> FLINK-1.7.1-p1.2 drwxrwxr-x 4 root root 4,0K янв 14 17:14 FLINK-1.7.1-p1.1 drwxrwxr-x 4 root root 4,0K янв 14 17:14 FLINK-1.7.1-p1.2 lrwxrwxrwx 1 root root 30 фев 27 13:01 FSEXPLORER -> FSEXPLORER-0.0.2-SNAPSHOT-p1.0 drwxrwxr-x 3 root root 4,0K фев 26 17:20 FSEXPLORER-0.0.2-SNAPSHOT-p1.0 lrwxrwxrwx 1 root root 34 фев 27 13:01 GPLEXTRAS -> GPLEXTRAS-5.13.0-1.cdh5.13.0.p0.29 drwxr-xr-x 4 root root 4,0K окт 4 2017 GPLEXTRAS-5.13.0-1.cdh5.13.0.p0.29 lrwxrwxrwx 1 root root 25 фев 27 13:01 KAFKA -> KAFKA-3.0.0-1.3.0.0.p0.40 drwxr-xr-x 6 root root 4,0K мар 24 2017 KAFKA-2.1.1-1.2.1.1.p0.18 drwxr-xr-x 6 root root 4,0K окт 5 2017 KAFKA-3.0.0-1.3.0.0.p0.40 lrwxrwxrwx 1 root root 44 фев 27 12:58 SPARK2 -> SPARK2-2.3.0.cloudera2-1.cdh5.13.3.p0.316101 drwxr-xr-x 6 root root 4,0K апр 11 2018 SPARK2-2.3.0.cloudera2-1.cdh5.13.3.p0.316101 drwxr-xr-x 6 root root 4,0K окт 2 11:02 SPARK2-2.3.0.cloudera4-1.cdh5.13.3.p0.611179 Is there any way in GUI or something else download and install this parcels on "bad" host? (deploy parcels to host?) I found this item in GUI: But I don't found any configuration how do this. Any idea? May be we cann't add host to any service for some other cause? In web GUI hosts show "OK" (we saw metrics about memory, interface, disk, etc), only warning that Parcels directory is empty   ... View more

Good evening. This message I receive after add two new hosts to the hadoop cluser. Tehnical info: Nodes - Debian GNU/Linux 8.9 (jessie) cloudera-manager-agent 5.13.0-1.cm5130.p0.55~jessie-cm5 amd64 cloudera-manager-daemons 5.13.0-1.cm5130.p0.55~jessie-cm5 all Earlier we add nodes using web interface. But this 2 nodes was added by hand: 1. Add repo cloudera 2. Install packages from repo 3. Configure /etc/cloudera-scm-agent/config.ini: server_host=hadoop-server.test.com After start clouder agents, I saw tho strangeness In cloudera web interface: 1. All Hosts - my new host - CDH Version is None 2. Error from topic: "The hostname and canonical name for this host are not consistent when checked from a Java process." I dont know is connected to each other this issues or not.   I try resolve second issue: python -c 'import socket; print socket.getfqdn(), socket.gethostbyname(socket.getfqdn())' regensburg.test.com 1.1.1.1 This command use from /etc/cloudera-scm-agent/config.ini file. Response is valid - A indicate to this IP and PTR indicate to domain name. But, from internet space I found this command and it return other response: java -classpath /usr/share/cmf/lib/agent-5.*.jar com.cloudera.cmon.agent.DnsTest {"status": "0", "ip": "1.1.1.1", "hostname": "regensburg", "canonicalname": "regensburg.test.com", "localhostDuration": "4", "canonicalnameDuration": "1" } Ok, hostname is short. root@regensburg ~ # hostname regensburg root@regensburg ~ # hostname -f regensburg.test.com In /etc/hosts we had some records: 1.1.1.1 regensburg.test.com regensburg Why arise this error? In other nodes we didn't receive this error, some info from working node: root@berlin ~ # python -c "import socket; print socket.getfqdn(); print socket.gethostbyname(socket.getfqdn())" berlin.test.com 2.2.2.2 java -classpath /usr/share/cmf/lib/agent-5.*.jar com.cloudera.cmon.agent.DnsTest {"status": "0", "ip": "2.2.2.2", "hostname": "berlin.test.com", "canonicalname": "berlin.test.com", "localhostDuration": "4", "canonicalnameDuration": "0" } root@berlin ~ # hostname berlin root@berlin ~ # hostname -f berlin.test.com root@berlin ~ # cat /etc/hosts | grep berli 2.2.2.2 berlin.test.com berlin root@berlin ~ # dpkg -l | grep clouder ii  cloudera-manager-agent                5.13.0-1.cm5130.p0.55~jessie-cm5   amd64        The Cloudera Manager Agent ii  cloudera-manager-daemons              5.13.0-1.cm5130.p0.55~jessie-cm5   all          Provides daemons for monitoring Hadoop and related tools.   From com.cloudera.cmon.agent.DnsTest  on all other nodes we receive FQDN hostname, but on this new - short hostname.   ... View more