Ambari services couldn't be started

[#1]

Hi, I've upgraded ambari from 2.2 to 2.4. when ambari was started using "ambari-server start" got the error as follows, DB configs consistency check failed. Run "ambari-server start --skip-database-check" to skip. If you use this "--skip-database-check" option, do not make any changes to your cluster topology or perform a cluster upgrade until you correct the database consistency issues. See "/var/log/ambari-server/ambari-server-check-database.log" for more details on the consistency issues. Ambari database consistency check finished In /var/log/ambari-server/ambari-server-check-database.log 2016-12-20 00:33:28,188 INFO - ******************************* Check database started ******************************* 2016-12-20 00:33:47,630 INFO - Checking for configs not mapped to any cluster 2016-12-20 00:33:47,703 INFO - Checking for configs selected more than once 2016-12-20 00:33:47,762 INFO - Checking for hosts without state 2016-12-20 00:33:47,792 INFO - Checking host component states count equals host component desired states count 2016-12-20 00:33:47,826 INFO - Checking services and their configs 2016-12-20 00:34:00,127 ERROR - Required config(s): usersync-properties,ranger-site is(are) not available for service RANGER with service config version 3 in cluster atlas So instead started ambari using "ambari-server start --skip-database-check" and the it worked fine. In /var/log/ambari-server/ambari-server-check-database.log 2016-12-20 00:34:00,131 INFO - ******************************* Check database completed ******************************* 2016-12-20 00:35:26,917 INFO - Checking DB store version 2016-12-20 00:35:30,076 INFO - DB store version is compatible But if logged into the ambari page, "start services" option is in disabled mode. How to start the services..

Thanks!!

[#2 · Accepted solution]

@Sujatha Veeswar

The error that you are getting indicates that you have some DB inconsistency. Your issue looks somewhat related to : https://issues.apache.org/jira/browse/AMBARI-18822 Which should be addressed in Ambari 2.5

As a temporary remedy you can try starting the Ambari server as following:

ambari-server start --skip-database-check

DB needs to be checked for the inconsistency fix.

.