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

AMBARI-15312 : Agent Registration request doesn't match any pattern

New Contributor

Hi All,

I am installing HDP - 2.6.5 cluster on Ambari-2.6.0. The OS platform is Cent OS-6.10. I am able to install Ambari successfully and also the agents are up & running but moving ahead the HDP installation fails to form cluster(Unable to Add hostname in cluster) with the error something to the link I pasted below :

https://issues.apache.org/jira/browse/AMBARI-15312

Also I get the error message in Hadoop server logfile : WARN [ambari-action-scheduler] ExecutionCommandWrapper:260 - 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 12

6 REPLIES 6

Super Mentor

@sameer shembavnekar

Can you pleas eattach the complete "/var/log/ambari-server/ambari-server.log" and also the Agent log from one of the problematic host "/var/log/ambari-agent/ambari-agent.log"

.

Hi @sameer shembavnekar,

can you tail on ambari-server.log and provide some more usefull logs.

the apache bug you have mentioned is unassigned so it can be an invalid issue or is not the actual root cause of the issue you are facing.

and the below exception you have mentioned might be because of some database inconsistencies,

WARN [ambari-action-scheduler] ExecutionCommandWrapper:260 - 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 12

additionally, can you see whats output of curl : http://<AMBARI_SERVER>:8080/api/v1/clusters/<CLUSTER_NAME>;

if its ok to reset the ambari-server and start the installation again,

If you want to reset the Ambari Database to remove the deleted cluster information then do the following:

  1. Take a backup of Ambari database to your backup location and reset the ambari-server using below command
pg_dump -U ambari ambari  > ./ambari_$(date +"%Y%m%d%H%M%S").sql
$ ambari-server reset

New Contributor

Hi Akhil...

Till now I have done this 10 to 15 times...also installed the cluster using different versions of HDP like 2.6.5 /2.5.3 ...but it comes at same place where it fails to register the hostname in cluster

Super Mentor

@sameer shembavnekar

Without knowing the reson of failure it is not right to just "reset" the ambari DB 10-15 times.

As mentioned earlier if you can attach the complete "/var/log/ambari-server/ambari-server.log" and also the Agent log from one of the problematic host "/var/log/ambari-agent/ambari-agent.log" then we might get the actual cause of failure.

Also please check if you have fullfilled the Prerequisite of Ambari cluster installations like?

https://docs.hortonworks.com/HDPDocuments/Ambari-2.6.2.0/bk_ambari-installation/content/prepare_the_...

1. Setting FQDN for every host? the output of following command on every host

# cat /etc/hosts
# hostname -f

2. From Ambari Server host are you able to do Passwordless ssh to the Agent hosts?

# ssh root@agent1.example.com

.

New Contributor

Hi Jay.....I followed this document...passwordless ssh is working fine also FQDN is set properly...I verified...but still I will attach the o/p once I reach home...but I am sure this all works.

New Contributor

WARN [qtp-ambari-agent-44] SecurityFilter:103 - Request https://hadoop04.localdomain:8440/ca doesn't match any pattern. 12 Aug 2018 11:56:03,772 WARN [qtp-ambari-agent-44] SecurityFilter:62 - This request is not allowed on this port: https://hadoop04.localdomain:8440/ca 12 Aug 2018 11:56:05,994 INFO [qtp-ambari-agent-44] HeartBeatHandler:385 - agentOsType = centos6 12 Aug 2018 11:56:06,003 INFO [qtp-ambari-agent-44] HostImpl:334 - Received host registration, host=[hostname=hadoop06,fqdn=hadoop06.localdomain,domain=localdomain,architecture=x86_64,processorcount=1,physicalprocessorcount=1,osname=centos,osversion=6.10,osfamily=redhat,memory=3088412,uptime_hours=0,mounts=(available=44430092,mountpoint=/,used=4423536,percent=10%,size=51475068,device=/dev/mapper/vg_hadoop04-lv_root,type=ext4)(available=394577,mountpoint=/boot,used=67475,percent=15%,size=487652,device=/dev/sda1,type=ext4)(available=47077572,mountpoint=/home,used=53800,percent=1%,size=49660652,device=/dev/mapper/vg_hadoop04-lv_home,type=ext4)] , registrationTime=1534038965994, agentVersion=2.6.2.0 12 Aug 2018 11:56:06,003 INFO [qtp-ambari-agent-44] TopologyManager:642 - TopologyManager.onHostRegistered: Entering 12 Aug 2018 11:56:06,004 INFO [qtp-ambari-agent-44] TopologyManager:696 - Host hadoop06.localdomain re-registered, will not be added to the available hosts list 12 Aug 2018 11:56:08,071 INFO [Thread-34] BSRunner:310 - Script log Mesg INFO:root:BootStrapping hosts ['hadoop04.localdomain', 'hadoop05.localdomain', 'hadoop06.localdomain'] using /usr/lib/ambari-server/lib/ambari_server cluster primary OS: redhat6 with user 'root'with ssh Port '22' sshKey File /var/run/ambari-server/bootstrap/1/sshKey password File null using tmp dir /var/run/ambari-server/bootstrap/1 ambari: hadoop04.localdomain; server_port: 8080; ambari version: 2.6.2.0; user_run_as: root INFO:root:Executing parallel bootstrap INFO:root:Finished parallel bootstrap 12 Aug 2018 11:56:08,072 INFO [pool-19-thread-1] BSHostStatusCollector:55 - Request directory /var/run/ambari-server/bootstrap/1 12 Aug 2018 11:56:08,072 INFO [pool-19-thread-1] BSHostStatusCollector:62 - HostList for polling on [hadoop04.localdomain, hadoop05.localdomain, hadoop06.localdomain] 12 Aug 2018 11:56:11,236 INFO [ambari-client-thread-32] Configuration:3226 - Ambari properties config file changed. 12 Aug 2018 11:56:11,237 INFO [ambari-client-thread-32] Configuration:3251 - Ambari properties config file changed. 12 Aug 2018 11:56:11,322 WARN [ambari-action-scheduler] ExecutionCommandWrapper:260 - 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 12 Aug 2018 11:56:11,323 WARN [ambari-action-scheduler] ExecutionCommandWrapper:260 - 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 12 Aug 2018 11:56:11,325 WARN [ambari-action-scheduler] ExecutionCommandWrapper:260 - 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 12 Aug 2018 11:56:11,609

Take a Tour of the Community
Don't have an account?
Your experience may be limited. Sign in to explore more.