@Michael Bronson I tried like this and it worked: # /usr/hdp/current/kafka-broker/bin/zookeeper-shell.sh localhost:2181 get / Connecting to localhost:2181 WATCHER:: WatchedEvent state:SyncConnected type:None path:null cZxid = 0x0 ctime = Thu Jan 01 00:00:00 UTC 1970 mZxid = 0x0 mtime = Thu Jan 01 00:00:00 UTC 1970 pZxid = 0x80009e5f1 cversion = 37 dataVersion = 0 aclVersion = 0 ephemeralOwner = 0x0 dataLength = 0 numChildren = 19 . ... View more

@Marcelo Natalio Saied The problem seems to be because of the following error (other errors seems it's side effect) resource_management.core.exceptions.ExecutionFailed: Execution of 'usermod -G hdfs -g hadoop hdfs' returned 6. usermod: user 'hdfs' does not exist in /etc/passwd Cause: The above error indicates that you might be running the Ambari Agent as "Non Root" user and the privileges are not setup correctly for this user. As this user does not have some privileges like creating/modifying user "hdfs" thats why it is failing to run the "usermod" / "useradd" command. So please check the following: 1. Are you running ambari agent as Non Root user? # grep 'run_as_user' /etc/ambari-agent/conf/ambari-agent.ini 2. If running ambari agent as non root uset then please make sure that you have customized the "/etc/sudoers" file as described in https://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.6.4/bk_security/content/_sudoer_configuration.html 3. Have you configured the "su" commands and corresponding Hadoop service accounts as mentioned in https://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.6.4/bk_security/content/_customizable_users.html And the Sudoer's default : https://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.6.4/bk_security/content/_sudo_defaults.html # Ambari Customizable Users ambari ALL=(ALL) NOPASSWD:SETENV: /bin/su hdfs *,/bin/su ambari-qa *,/bin/su ranger *,/bin/su zookeeper *,/bin/su knox *,/bin/su falcon *,/bin/su ams *, /bin/su flume *,/bin/su hbase *,/bin/su spark *,/bin/su accumulo *,/bin/su hive *,/bin/su hcat *,/bin/su kafka *,/bin/su mapred *,/bin/su oozie *,/bin/su sqoop *,/bin/su storm *,/bin/su tez *,/bin/su atlas *,/bin/su yarn *,/bin/su kms *,/bin/su activity_analyzer *,/bin/su livy *,/bin/su zeppelin *,/bin/su infra-solr *,/bin/su logsearch *<br> 4. The Most important thing is the following Doc which shows what all commands agent needs access: https://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.6.4/bk_security/content/_commands.html . ... View more

@rachana sri Your log shows that it is trying to connect the localhost:2181 zookeeper. issuing: !connect jdbc:phoenix:localhost:2181:/hbase none none org.apache.phoenix.jdbc.PhoenixDriver Connecting to jdbc:phoenix:localhost:2181:/hbase Are you sure that you have a Zookeeper pro cess running on "localhost:2181" address? Please check if port 2181 is opened and listening to correct address? Also please check the port 16020 as we see 16020 failed on local exception # netstat -tnlpa | grep 2181 # netstat -tnlpa | grep 16020 Please try specifying the hostname. Like if you have the zookeeper running on a remote host (like test1.example.com) then please try specifying the Hostname. # ./sqlline.py test1.example.com:2181/hbase . Also as we repeatedly see "No route to host" please let us know if you are using correct hostnames/FQDN "hostname -f" ? java.io.IOException: Call to / :16020 failed on local exception: java.net.NoRouteToHostException: No route to host Mon May Are you using correct hostname for your services and Do you have the Firewall Turned Off and able to access the services using their Hostname & ports like using telnet? # hostname -f # telnet $HOSTNAME $PORT . . ... View more

@Christian Lunesa Looks like some other process is using port 8670 which is used by Agents hence agent is not able toi startup. Please find which process is using the port 8670 and then kill it then try the start Agent again. Ambari Agent uses this port 8670 as Ping Port So that port should be free before we attempt to start the agent. # netstat -tnlpa | grep 8670<br> # kill -9 $PID_from_above_command # ambari-agent start . OR you will need to change the "ping_port" of ambari agent in the following file: # grep '8670' /etc/ambari-agent/conf/ambari-agent.ini ping_port=8670 . ... View more

@Manisha Pande If this answers your query/issue then please mark this HCC thread as answered by clicking on "Accept" link on the correct answer, That way it will help other HCC users to quickly find the answers. ... View more

@Manisha Pande If this answers your query/issue then please mark this HCC thread as answered by clicking on "Accept" link on the correct answer, That way it will help other HCC users to quickly find the answers. ... View more

@Prakash Punj Additionally, it also looks like that you have added the following property in your "/etc/ambari-server/conf/ambari.properties" security.server.two_way_ssl = true This property determines whether two-way SSL should be used between Ambari Server and Ambari Agents so that the agents must also use SSL. (Default value is "false") So is there any specific reason that you have truned two way ssl on between ambari server and agent? Can you please tun it off and then restart ambari server as well as ambari agent once to see if it communicates well? ... View more