Ambari 2.2.2 ranger installation failed @ step 6 with "server error" message.

[#1]

I'm re-installing Ranger. I deleted the previous install using ambari-api. But, now I'm seeing this issue: @ step 6 with "server error" message and then Ambari hangs. here is another similar HCC case with no resolution: https://community.hortonworks.com/questions/2862/ambari-212-ranger-installation-failed-api-delete-a....

At the same time, if I try to upgrade the cluster to 2.4 after deleting Ranger, it is also failing. It throws mising pre-main class error for one of the Ranger jars (though ranger has been deleted completely).

As per log this statement is failing while writing ambari DB:

INSERT INTO serviceconfigmapping (config_id, service_config_id) VALUES (22, 240) was aborted

[#2]

Have you followed the steps outlined by Neeraj to cleanup DB ?

[#3]

yes, of course. But, it did not help the previous post and as well as me.

[#4]

Here is ambari-server log:

19 May 2016 14:29:37,414  INFO [qtp-ambari-client-26] StackAdvisorRunner:71 -     advisor script stderr:
19 May 2016 14:30:10,741  INFO [qtp-ambari-client-69] AmbariManagementControllerImpl:1355 - Received a updateCluster request, clusterId=2, clusterName=DEVHDPCLST, securityType=null, request={ clusterName=DEVHDPCLST, clusterId=2, provisioningState=null, securityType=null, stackVersion=HDP-2.2, desired_scv=null, hosts=[] }
19 May 2016 14:30:10,758  INFO [qtp-ambari-client-69] AmbariManagementControllerImpl:1474 - Applying configuration with tag 'version1463686209068' to cluster 'DEVHDPCLST'  for configuration type hbase-env
19 May 2016 14:30:10,880  INFO [qtp-ambari-client-69] AmbariManagementControllerImpl:1474 - Applying configuration with tag 'version1463686209070' to cluster 'DEVHDPCLST'  for configuration type hbase-site
19 May 2016 14:30:11,027  INFO [qtp-ambari-client-69] AmbariManagementControllerImpl:1474 - Applying configuration with tag 'version1463686209072' to cluster 'DEVHDPCLST'  for configuration type ranger-hbase-plugin-properties
19 May 2016 14:30:11,392 ERROR [qtp-ambari-client-69] AmbariJpaLocalTxnInterceptor:180 - [DETAILED ERROR] Rollback reason:
Local Exception Stack:
Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.6.2.v20151217-774c696): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.BatchUpdateException: Batch entry 3 INSERT INTO serviceconfigmapping (config_id, service_config_id) VALUES (22, 240) was aborted.  Call getNextException to see the cause.
Error Code: 0
Call: INSERT INTO serviceconfigmapping (config_id, service_config_id) VALUES (?, ?)
        bind => [2 parameters bound]
        at org.eclipse.persistence.exceptions.DatabaseException.sqlException(DatabaseException.java:340)
        at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.processExceptionForCommError(DatabaseAccessor.java:1620)
        at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeJDK12BatchStatement(DatabaseAccessor.java:926)
        at org.eclipse.persistence.internal.databaseaccess.ParameterizedSQLBatchWritingMechanism.executeBatch(ParameterizedSQLBatchWritingMechanism.java:179)
        at org.eclipse.persistence.internal.databaseaccess.ParameterizedSQLBatchWritingMechanism.executeBatchedStatements(ParameterizedSQLBatchWritingMechanism.java:134)
        at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.writesCompleted(DatabaseAccessor.java:1845)
        at org.eclipse.persistence.internal.sessions.AbstractSession.writesCompleted(AbstractSession.java:4300)
        at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.writesCompleted(UnitOfWorkImpl.java:5592)
        at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.acquireWriteLocks(UnitOfWorkImpl.java:1646)
        at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.commitTransactionAfterWriteChanges(UnitOfWorkImpl.java:1614)
        at org.eclipse.persistence.internal.sessions.RepeatableWriteUnitOfWork.commitRootUnitOfWork(RepeatableWriteUnitOfWork.java:285)
        at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.commitAndResume(UnitOfWorkImpl.java:1169)
        at org.eclipse.persistence.internal.jpa.transaction.EntityTransactionImpl.commit(EntityTransactionImpl.java:134)
        at org.apache.ambari.server.orm.AmbariJpaLocalTxnInterceptor.invoke(AmbariJpaLocalTxnInterceptor.java:153)
        at com.google.inject.internal.InterceptorStackCallback$InterceptedMethodInvocation.proceed(InterceptorStackCallback.java:72)
        at com.google.inject.internal.InterceptorStackCallback.intercept(InterceptorStackCallback.java:52)
        at org.apache.ambari.server.state.cluster.ClusterImpl$$EnhancerByGuice$$90de4d20.applyConfigs(<generated>)
        at org.apache.ambari.server.state.cluster.ClusterImpl.addDesiredConfig(ClusterImpl.java:2282)
        at org.apache.ambari.server.controller.AmbariManagementControllerImpl.updateCluster(AmbariManagementControllerImpl.java:1488)

[#5 · Accepted solution]

Usually these sort of problems indicate a deeper Ambari problem. Most likely if you try to add any service, it would fail. Would recommend restoring your Ambari db backup or contacting support in such scenarios.