question Re: REASON: Ambari Server java process has stopped. in Support Questions

REASON: Ambari Server java process has stopped.

AarifAkhter — Thu, 13 Feb 2020 22:29:15 GMT

Waiting for server start...............ERROR: Exiting with exit code -1. REASON: Ambari Server java process has stopped. Please check the logs for more information.

Re: REASON: Ambari Server java process has stopped.

jsensharma — Thu, 13 Feb 2020 22:04:52 GMT

@AarifAkhter

As the failure message says :

Please check the logs for more information.

So in order to find out the cause of failure we will need to look at ambari server logs for more detailed messages.

Hence please share the following files for initial investigation..

/var/log/ambari-server/ambari-server.log /var/log/ambari-server/ambari-server.out

Re: REASON: Ambari Server java process has stopped.

AarifAkhter — Thu, 13 Feb 2020 22:15:36 GMT

@jsensharma

Exception in thread "main" com.google.inject.CreationException: Guice creation errors:

1) Error injecting constructor, java.lang.RuntimeException: Error while creating database accessor
at org.apache.ambari.server.orm.DBAccessorImpl.<init>(DBAccessorImpl.java:87)
at org.apache.ambari.server.orm.DBAccessorImpl.class(DBAccessorImpl.java:75)
while locating org.apache.ambari.server.orm.DBAccessorImpl
while locating org.apache.ambari.server.orm.DBAccessor
for field at org.apache.ambari.server.orm.dao.DaoUtils.dbAccessor(DaoUtils.java:36)
at org.apache.ambari.server.orm.dao.DaoUtils.class(DaoUtils.java:36)
while locating org.apache.ambari.server.orm.dao.DaoUtils
for field at org.apache.ambari.server.orm.dao.UserDAO.daoUtils(UserDAO.java:45)
at org.apache.ambari.server.orm.dao.UserDAO.class(UserDAO.java:45)
while locating org.apache.ambari.server.orm.dao.UserDAO
for field at org.apache.ambari.server.controller.internal.ActiveWidgetLayoutResourceProvider.userDAO(ActiveWidgetLayoutResourceProvider.java:61)
Caused by: java.lang.RuntimeException: Error while creating database accessor
at org.apache.ambari.server.orm.DBAccessorImpl.<init>(DBAccessorImpl.java:120)
at org.apache.ambari.server.orm.DBAccessorImpl$$FastClassByGuice$$86dbc63e.newInstance(<generated>)
at com.google.inject.internal.cglib.reflect.$FastConstructor.newInstance(FastConstructor.java:40)
at com.google.inject.internal.DefaultConstructionProxyFactory$1.newInstance(DefaultConstructionProxyFactory.java:60)
at com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:85)
at com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:254)
at com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46)
at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1031)
at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40)
at com.google.inject.Scopes$1$1.get(Scopes.java:65)
at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:40)
at com.google.inject.internal.FactoryProxy.get(FactoryProxy.java:54)
at com.google.inject.internal.SingleFieldInjector.inject(SingleFieldInjector.java:53)
at com.google.inject.internal.MembersInjectorImpl.injectMembers(MembersInjectorImpl.java:110)
at com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:94)
at com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:254)
at com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46)
at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1031)
at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40)
at com.google.inject.Scopes$1$1.get(Scopes.java:65)
at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:40)
at com.google.inject.internal.SingleFieldInjector.inject(SingleFieldInjector.java:53)
at com.google.inject.internal.MembersInjectorImpl.injectMembers(MembersInjectorImpl.java:110)
at com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:94)
at com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:254)
at com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46)

Re: REASON: Ambari Server java process has stopped.

AarifAkhter — Thu, 13 Feb 2020 22:18:40 GMT

Re: REASON: Ambari Server java process has stopped.

jsensharma — Thu, 13 Feb 2020 22:23:18 GMT

@AarifAkhter

We see the error is cause by some DB access/connect

Caused by: java.lang.RuntimeException: Error while creating database accessor at org.apache.ambari.server.orm.DBAccessorImpl.<init>(DBAccessorImpl.java:120)

So few queries:

1. Is this a newly setup ambari server?

2. Do you see the DataBase is running fine and the DB host/port is accessible ?

3. Are you using Embedded Postgres Database?

4. When was last time ambari server running fine? Any recent chances made to ambari server config/host ?

I am suspecting that there should be some more detailed log like some more "Caused By" section in your ambari-server.log which is not copied fully in your last update.

So can you please recheck your ambari log and let us know what was the first error and if you can share the Full stack trace. some times there are more than on "Caused By" section in a single stack trace.