Support Questions
Find answers, ask questions, and share your expertise

How to resolv " Unable to lookup the cluster by ID" and "Received registration request from host with non compatible agent version" ?

How to resolv " Unable to lookup the cluster by ID" and "Received registration request from host with non compatible agent version" ?

Hi ! I m trying to add isilon to hortonworks, but it fails, the Ambari UI shows 0 issues, but the ambari-server log shows this errors

Thank you

N.B hdfs-hdp.pfe.test.com is the name of my host that failed.

p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 10.0px Monaco; color: #f5f5f5; background-color: #000000} span.s1 {font-variant-ligatures: no-common-ligatures}

2017 12:24:34,566 WARN [qtp-ambari-agent-37] HeartBeatHandler:411 - Received registration request from host with non compatible agent version, hostname=hdfs-hdp.pfe.test.com, agentVersion=1.7.0, serverVersion=2.5.0.3

19 avr. 2017 12:24:38,831 WARN [qtp-ambari-agent-37] HeartBeatHandler:411 - Received registration request from host with non compatible agent version, hostname=hdfs-hdp.pfe.test.com, agentVersion=1.7.0, serverVersion=2.5.0.3

19 avr. 2017 12:25:40,688 WARN [qtp-ambari-agent-37] HeartBeatHandler:411 - Received registration request from host with non compatible agent version, hostname=hdfs-hdp.pfe.test.com, agentVersion=1.7.0, serverVersion=2.5.0.3

19 avr. 2017 12:25:44,978 WARN [qtp-ambari-agent-38] HeartBeatHandler:411 - Received registration request from host with non compatible agent version, hostname=hdfs-hdp.pfe.test.com, agentVersion=1.7.0, serverVersion=2.5.0.3

19 avr. 2017 12:26:46,064 WARN [qtp-ambari-agent-38] HeartBeatHandler:411 - Received registration request from host with non compatible agent version, hostname=hdfs-hdp.pfe.test.com, agentVersion=1.7.0, serverVersion=2.5.0.3

19 avr. 2017 12:26:50,347 WARN [qtp-ambari-agent-38] HeartBeatHandler:411 - Received registration request from host with non compatible agent version, hostname=hdfs-hdp.pfe.test.com, agentVersion=1.7.0, serverVersion=2.5.0.3

19 avr. 2017 12:27:51,465 WARN [qtp-ambari-agent-35] HeartBeatHandler:411 - Received registration request from host with non compatible agent version, hostname=hdfs-hdp.pfe.test.com, agentVersion=1.7.0, serverVersion=2.5.0.3

19 avr. 2017 12:27:55,737 WARN [qtp-ambari-agent-36] HeartBeatHandler:411 - Received registration request from host with non compatible agent version, hostname=hdfs-hdp.pfe.test.com, agentVersion=1.7.0, serverVersion=2.5.0.3

19 avr. 2017 12:28:56,853 WARN [qtp-ambari-agent-38] HeartBeatHandler:411 - Received registration request from host with non compatible agent version, hostname=hdfs-hdp.pfe.test.com, agentVersion=1.7.0, serverVersion=2.5.0.3

19 avr. 2017 12:29:01,115 WARN [qtp-ambari-agent-36] HeartBeatHandler:411 - Received registration request from host with non compatible agent version, hostname=hdfs-hdp.pfe.test.com, agentVersion=1.7.0, serverVersion=2.5.0.3

19 avr. 2017 12:29:17,516 INFO [pool-18-thread-1] MetricsServiceImpl:64 - Checking for metrics sink initialization

19 avr. 2017 12:29:17,516 INFO [pool-18-thread-1] MetricsServiceImpl:78 - ********* Configuring Metric Sink **********

19 avr. 2017 12:29:17,516 INFO [pool-18-thread-1] AmbariMetricSinkImpl:92 - No clusters configured.

19 avr. 2017 12:30:02,249 WARN [qtp-ambari-agent-36] HeartBeatHandler:411 - Received registration request from host with non compatible agent version, hostname=hdfs-hdp.pfe.test.com, agentVersion=1.7.0, serverVersion=2.5.0.3

19 avr. 2017 12:30:06,500 WARN [qtp-ambari-agent-36] HeartBeatHandler:411 - Received registration request from host with non compatible agent version, hostname=hdfs-hdp.pfe.test.com, agentVersion=1.7.0, serverVersion=2.5.0.3

19 avr. 2017 12:31:07,632 WARN [qtp-ambari-agent-37] HeartBeatHandler:411 - Received registration request from host with non compatible agent version, hostname=hdfs-hdp.pfe.test.com, agentVersion=1.7.0, serverVersion=2.5.0.3

19 avr. 2017 12:31:11,877 WARN [qtp-ambari-agent-38] HeartBeatHandler:411 - Received registration request from host with non compatible agent version, hostname=hdfs-hdp.pfe.test.com, agentVersion=1.7.0, serverVersion=2.5.0.3

19 avr. 2017 12:31:34,576 WARN [ambari-action-scheduler] ExecutionCommandWrapper:185 - Unable to lookup the cluster by ID; assuming that there is no cluster and therefore no configs for this execution command: Cluster not found, clusterName=clusterID=-1

19 avr. 2017 12:31:35,585 WARN [ambari-action-scheduler] ExecutionCommandWrapper:185 - Unable to lookup the cluster by ID; assuming that there is no cluster and therefore no configs for this execution command: Cluster not found, clusterName=clusterID=-1

19 avr. 2017 12:31:36,593 WARN [ambari-action-scheduler] ExecutionCommandWrapper:185 - Unable to lookup the cluster by ID; assuming that there is no cluster and therefore no configs for this execution command: Cluster not found, clusterName=clusterID=-1

19 avr. 2017 12:31:37,599 WARN [ambari-action-scheduler] ExecutionCommandWrapper:185 - Unable to lookup the cluster by ID; assuming that there is no cluster and therefore no configs for this execution command: Cluster not found, clusterName=clusterID=-1

19 avr. 2017 12:31:38,602 WARN [ambari-action-scheduler] ExecutionCommandWrapper:185 - Unable to lookup the cluster by ID; assuming that there is no cluster and therefore no configs for this execution command: Cluster not found, clusterName=clusterID=-1

19 avr. 2017 12:31:39,608 WARN [ambari-action-scheduler] ExecutionCommandWrapper:185 - Unable to lookup the cluster by ID; assuming that there is no cluster and therefore no configs for this execution command: Cluster not found, clusterName=clusterID=-1

19 avr. 2017 12:31:40,612 WARN [ambari-action-scheduler] ExecutionCommandWrapper:185 - Unable to lookup the cluster by ID; assuming that there is no cluster and therefore no configs for this execution command: Cluster not found, clusterName=clusterID=-1

19 avr. 2017 12:31:41,310 INFO [qtp-ambari-agent-35] HeartBeatHandler:332 - HeartBeatHandler.sendCommands: sending ExecutionCommand for host hdp-master.pfe.test.com, role check_host, roleCommand ACTIONEXECUTE, and command ID 142-0, task ID 170

4 REPLIES 4

Re: How to resolv " Unable to lookup the cluster by ID" and "Received registration request from host with non compatible agent version" ?

Contributor

@tita titouf

Check the HDFS logs on OneFS. They're in /var/log/hdfs.log. You should see an error related to the communication with Ambari Server.

The problem is clear to me, though. You're trying to use the latest version of Ambari, but there is not yet a version of OneFS that provides compatibility with it. See the chart here, https://community.emc.com/docs/DOC-37101 . There is no 2.5.x yet on that chart.

Please escalate with Isilon support if you are not able to start over with a lower version of Ambari and HDP. The next releases of OneFS will have support for Ambari 2.5, but you may be able to get access to it sooner.

Re: How to resolv " Unable to lookup the cluster by ID" and "Received registration request from host with non compatible agent version" ?

Super Mentor

@tita titouf

The mentioned WARN messages are coming because looks like you have Ambari Server version 2.5 installed at your end on your cluster few Ambari Agents are still older version (1.7) Hence Ambari is showing the mentioned WARN message during Agent registration.

Received registration request from host with non compatible agent version, hostname=hdfs-hdp.pfe.test.com, agentVersion=1.7.0, serverVersion=2.5.0.3

So in order to resolve this issue you will need to check the cluster hosts to findout if they have the correct Ambari Agent binaries installed there? For that we will need to check the following command outputs to see if the agents version and the repo are correct? Run the following command on the cluster nodes to find out the problematic Agent (Like Host:

hdfs-hdp.pfe.test.com)

# rpm -qa | grep ambari
# echo "Make sure that the above command returns same ambari binary versions for server & agents"
# cat /etc/yum.repos.d/ambari.repo

Please see the code: https://github.com/apache/ambari/blob/release-2.5.0/ambari-server/src/main/java/org/apache/ambari/se...

.

It can also happen if in your network some host (like : hdfs-hdp.pfe.test.com) is running with Ambari Agent version 1.7 and by mistake it has "/etc/ambari-agent/conf/ambari-agent.ini" file entry pointing to your AmbariServer 2.5.

.

Re: How to resolv " Unable to lookup the cluster by ID" and "Received registration request from host with non compatible agent version" ?

Contributor

@Jay SenSharma

Notice that Tita says she is using Isilon.

Isilon OneFS always initially says that it is 1.7, waits for Ambari Server to report its version, and then conforms to the Ambari version if it is whitelisted in OneFS.

Ambari 2.5.x is not whitelisted on any OneFS version yet.

Tita needs to wait for a version of OneFS with Ambari 2.5 whitelisted, needs to use a lower version of Ambari, or needs to contact Isilon support to request sooner access in OneFS.

Re: How to resolv " Unable to lookup the cluster by ID" and "Received registration request from host with non compatible agent version" ?

Super Mentor

@Rob Ketcherside

Thank you for explaining the "isilon' part, Now i see that the query is more specific to Isilon base environment. Your update is perfect in the right direction. +1