Support Questions

Find answers, ask questions, and share your expertise
Announcements
Celebrating as our community reaches 100,000 members! Thank you!

Ambari Cannot register host with not supported os type

avatar
Expert Contributor

My hosts won't register but I am using Ubuntu 14.

Agent log:

ERROR 2016-07-27 22:02:59,618 Controller.py:117 - Cannot register host with not supported os type, hostname=x.y.z, serverOsType=ubuntu14, agentOsType=ubuntu14

Server log:

22:03:10,454 ERROR [qtp1057908342-26] ActionDBAccessorImpl:241 - Host x.y.z doesn't exist in database

Any help is much appreciated

1 ACCEPTED SOLUTION

avatar

@ed day

Please check link:-

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

this was the bug i ambari 1.7.0.

The usual work flow when ambari-server is creating the agents is as follow: Ambari-server host provisions by ssh all ambari-agents Every ambari-agent needs to callback to https://ambari.test.com:8440 and register itself in the server. All agents are registered and now you can install "stuff" in them through ambari.

If you configuring multinode cluster then the problem was the agents in different nodes couldn't execute the callback cause they couldn't reach ambari-server url in that port.

Maybe this isssue is related to ports 8440 and 8441 in the ambari-server host. Please open this port and try once again or use ambari version 2.0.0 or later.

Hope it helps!

View solution in original post

6 REPLIES 6

avatar
Cloudera Employee

Hi @ed day

1 - What are the Ambari and HDP stack versions here?

2 - Is this a new cluster? If not, what OS are existing hosts running?

3 - What is your complete Ubuntu version number?

avatar
Expert Contributor

Thanks!!

1. Ambari 1.7.0 HDP 2.2.

2. New cluster.

3. Ubuntu 14.04.4 LTS.

avatar
Cloudera Employee

@ed day the issue is most likely that Ubuntu 14 is not a supported OS with Ambari 1.7 and HDP 2.2.

Only Ubuntu 12 is supported for Ambari 1.7. You will need to go with Ambari 2.1 or higher to have Ubuntu 14 support.

avatar

@ed day

Please check link:-

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

this was the bug i ambari 1.7.0.

The usual work flow when ambari-server is creating the agents is as follow: Ambari-server host provisions by ssh all ambari-agents Every ambari-agent needs to callback to https://ambari.test.com:8440 and register itself in the server. All agents are registered and now you can install "stuff" in them through ambari.

If you configuring multinode cluster then the problem was the agents in different nodes couldn't execute the callback cause they couldn't reach ambari-server url in that port.

Maybe this isssue is related to ports 8440 and 8441 in the ambari-server host. Please open this port and try once again or use ambari version 2.0.0 or later.

Hope it helps!

avatar
Expert Contributor

Thanks Ashnee! I will try that later today using Amabari 2.2.0 from here: https://cwiki.apache.org/confluence/display/AMBARI/Install+Ambari+2.2.0+from+Public+Repositories

avatar

if this is the answer of your question, then lets close this.