Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

Unable to start Ambari-sever

Unable to start Ambari-sever

Contributor

Hi!

Unable to start ambari-server

[root@bi-nifi1 dmp]# cat /var/log/ambari-server/ambari-server.out
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=128m; support was removed in 8.0
Database consistency check result: DB_CHECK_WARNING
An unexpected error occured during starting Ambari Server.
org.apache.ambari.server.ServiceNotFoundException: Service not found, clusterName=hdf_kg, serviceName=AMBARI_INFRA
        at org.apache.ambari.server.state.cluster.ClusterImpl.getService(ClusterImpl.java:864)
        at org.apache.ambari.server.api.services.AmbariMetaInfo.reconcileAlertDefinitions(AmbariMetaInfo.java:1240)
        at org.apache.ambari.server.controller.AmbariServer.run(AmbariServer.java:532)
        at org.apache.ambari.server.controller.AmbariServer.main(AmbariServer.java:1067)

Log at /var/log/ambari-server/ambari-server-check-database.log says:

2018-12-18 16:32:33,076  INFO - Checking DB store version
2018-12-18 16:32:33,643  INFO - DB store version is compatible
2018-12-18 16:32:41,042  INFO - ******************************* Check database started *******************************
2018-12-18 16:32:41,042  INFO - Ensuring that the schema set for Postgres is correct
2018-12-18 16:32:41,048  INFO - Checking for configs that are not mapped to any service
2018-12-18 16:32:41,150  INFO - Checking for configs selected more than once
2018-12-18 16:32:41,152  INFO - Checking for hosts without state
2018-12-18 16:32:41,152  INFO - Checking host component states count equals host component desired states count
2018-12-18 16:32:41,153  INFO - Checking services and their configs
2018-12-18 16:32:41,153  INFO - Getting ambari metainfo instance
2018-12-18 16:32:41,153  INFO - Executing query 'GET_SERVICES_WITHOUT_CONFIGS'
2018-12-18 16:32:41,154  INFO - Executing query 'GET_SERVICE_CONFIG_WITHOUT_MAPPING'
2018-12-18 16:32:41,155  INFO - Getting stack info from database
2018-12-18 16:32:41,155  INFO - Executing query 'GET_SERVICES_WITH_CONFIGS'
2018-12-18 16:32:41,160  INFO - Comparing service configs from stack with configs that we got from db
2018-12-18 16:32:41,160  INFO - Getting services from metainfo
2018-12-18 16:32:41,160  INFO - Processing HDF-3.0 / RANGER
2018-12-18 16:32:41,160  INFO - Processing HDF-3.0 / AMBARI_METRICS
2018-12-18 16:32:41,160  INFO - Processing HDF-3.0 / AMBARI_INFRA
2018-12-18 16:32:41,160  WARN - Service AMBARI_INFRA is not available for stack HDF-3.0 in cluster hdf_kg
2018-12-18 16:32:41,160  INFO - Processing HDF-3.0 / LOGSEARCH
2018-12-18 16:32:41,160  INFO - Processing HDF-3.0 / KAFKA
2018-12-18 16:32:41,160  INFO - Processing HDF-3.0 / NIFI
2018-12-18 16:32:41,160  INFO - Processing HDF-3.0 / ZOOKEEPER
2018-12-18 16:32:41,160  INFO - Comparing required service configs from stack with mapped service configs from db
2018-12-18 16:32:41,160  WARN - Required config(s): atlas-tagsync-ssl is(are) not available for service RANGER with service config version 23 in cluster hdf_kg
2018-12-18 16:32:41,161  INFO - Getting services which has mapped configs which are not selected in clusterconfig
2018-12-18 16:32:41,164  INFO - Checking Topology tables
2018-12-18 16:32:41,166  INFO - Checking for tables with large physical size
2018-12-18 16:32:41,167  INFO - The database table host_role_command is currently 3.641 MB and is within normal limits (3000.000)
2018-12-18 16:32:41,167  INFO - The database table execution_command is currently 2.109 MB and is within normal limits (3000.000)
2018-12-18 16:32:41,168  INFO - The database table stage is currently 0.477 MB and is within normal limits (3000.000)
2018-12-18 16:32:41,168  INFO - The database table request is currently 0.297 MB and is within normal limits (3000.000)
2018-12-18 16:32:41,168  INFO - The database table alert_history is currently 4.758 MB and is within normal limits (3000.000)
2018-12-18 16:32:41,168  INFO - Checking config group host mappings
2018-12-18 16:32:41,169  INFO - ******************************* Check database completed *******************************

We tried manually start the AMBARI_INFRA using the following command given by @scharan, service seems to be started, but it didn't help

su - infra-solr -c '/usr/lib/ambari-infra-solr/bin/solr start -cloud -noprompt -s /opt/ambari_infra_solr/data'
ambari=# select * from ambari.hostcomponentstate where service_name = 'AMBARI_INFRA';
 id  | cluster_id |  component_name   | version | current_state | host_id | service_name | upgrade_state | security_state 
-----+------------+-------------------+---------+---------------+---------+--------------+---------------+----------------
 105 |          2 | INFRA_SOLR_CLIENT | UNKNOWN | INSTALLED     |     101 | AMBARI_INFRA | NONE          | UNKNOWN
   4 |          2 | INFRA_SOLR        | UNKNOWN | STARTED       |      51 | AMBARI_INFRA | NONE          | UNKNOWN
 104 |          2 | INFRA_SOLR_CLIENT | UNKNOWN | INSTALLED     |     103 | AMBARI_INFRA | NONE          | UNKNOWN
 106 |          2 | INFRA_SOLR_CLIENT | UNKNOWN | INSTALLED     |     102 | AMBARI_INFRA | NONE          | UNKNOWN
  20 |          2 | INFRA_SOLR_CLIENT | UNKNOWN | INSTALLED     |      51 | AMBARI_INFRA | NONE          | UNKNOWN
  21 |          2 | INFRA_SOLR_CLIENT | UNKNOWN | INSTALLED     |       4 | AMBARI_INFRA | NONE          | UNKNOWN
  24 |          2 | INFRA_SOLR_CLIENT | UNKNOWN | INSTALLED     |       1 | AMBARI_INFRA | NONE          | UNKNOWN
(7 rows)
Cluster is not in the cloud, maybe we shouldn't have to stated -cloud option in this command or 
ambari=# select * from ambari.servicecomponentdesiredstate where service_name = 'AMBARI_INFRA';
 id |  component_name   | cluster_id | desired_state | service_name | recovery_enabled | desired_repo_version_id | repo_state 
----+-------------------+------------+---------------+--------------+------------------+-------------------------+------------
  4 | INFRA_SOLR_CLIENT |          2 | INSTALLED     | AMBARI_INFRA |                0 |                      51 | CURRENT
  3 | INFRA_SOLR        |          2 | STARTED       | AMBARI_INFRA |                1 |                      51 | CURRENT
(2 rows)

Should we start INFRA_SOLR_CLIENTs also? If yes how can they be started manually?

Could you please give any suggestion?

with my best regards

Gulshan

1 REPLY 1

Re: Unable to start Ambari-sever

Hi @Gulshan Agivetova ,

I am not sure if you have successfully recovered this ambari startup issue, if you haven't Can you tell me whats you current ambari version.

As per exception :

org.apache.ambari.server.ServiceNotFoundException:Servicenot found, clusterName=hdf_kg, serviceName=AMBARI_INFRA        at org.apache.ambari.server.state.cluster.ClusterImpl.getService(ClusterImpl.java:864)        at org.apache.ambari.server.api.services.AmbariMetaInfo.reconcileAlertDefinitions(AmbariMetaInfo.java:1240)

It states me you have Tried to upgrade to ambari-2.7.x version (Ambari in HDF) and forgot to upgrade mpack

This is the order in which you need to upgrade

1)upgrade ambari-server packages

2) upgrade mpack

3) run ambari-server upgrade command

refer to : https://docs.hortonworks.com/HDPDocuments/HDF3/HDF-3.2.0/ambari-managed-hdf-upgrade/content/hdf-upgr...

Also refer to this article :https://community.hortonworks.com/articles/230871/hdf-ambari-upgrade-to-270-failing-with-exception.html

Hope this helps you. Please accept answer if it did.