Not a customer? Click the 'Start a free trial' link to begin a 30-day SaaS trial of our product and to join our community.
Existing Cisco AppDynamics customers should click the 'Sign In' button to authenticate to access the community
on 08-31-2017 10:32 AM
While starting the Events Service as a standalone process, the following error can be seen in the log files:
1) Error injecting method, MasterNotDiscoveredException[null]
at com.appdynamics.analytics.processor.elasticsearch.index.IndexManagementModule.createMetaDataIndices(IndexManagementModule.java:199)
while locating com.appdynamics.analytics.processor.elasticsearch.index.IndexManagementModule
1 error
at com.google.inject.internal.Errors.throwProvisionExceptionIfErrorsExist(Errors.java:482)
at com.google.inject.internal.MembersInjectorImpl.injectMembers(MembersInjectorImpl.java:67)
at com.google.inject.internal.InjectorImpl.injectMembers(InjectorImpl.java:984)
at com.appdynamics.common.framework.Loaders.internalPrepareAndPreStart(Loaders.java:182)
at com.appdynamics.common.framework.Loaders.loadAndInitializeModules(Loaders.java:128)
at com.appdynamics.common.framework.AbstractApp.run(AbstractApp.java:318)
at com.appdynamics.common.framework.AbstractApp.run(AbstractApp.java:63)
at io.dropwizard.cli.EnvironmentCommand.run(EnvironmentCommand.java:40)
at io.dropwizard.cli.ConfiguredCommand.run(ConfiguredCommand.java:77)
at io.dropwizard.cli.Cli.run(Cli.java:70)
at io.dropwizard.Application.run(Application.java:80)
at com.appdynamics.common.framework.AbstractApp.callRunServer(AbstractApp.java:270)
at com.appdynamics.common.framework.AbstractApp.runUsingFile(AbstractApp.java:264)
at com.appdynamics.common.framework.AbstractApp.runUsingTemplate(AbstractApp.java:251)
at com.appdynamics.common.framework.AbstractApp.runUsingTemplate(AbstractApp.java:171)
at com.appdynamics.analytics.processor.AnalyticsService.main(AnalyticsService.java:71)
Caused by: MasterNotDiscoveredException[null]
at org.elasticsearch.action.support.master.TransportMasterNodeAction$AsyncSingleAction$5.onTimeout(TransportMasterNodeAction.java:234)
at org.elasticsearch.cluster.ClusterStateObserver$ObserverClusterStateListener.onTimeout(ClusterStateObserver.java:236)
at org.elasticsearch.cluster.service.InternalClusterService$NotifyTimeout.run(InternalClusterService.java:804)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:748)
One of the possible causes for this issue can be during Events Service cluster deployment when the master node is not reachable due to configuration issues in the events-service-api-store.properties
file.
To resolve this issue, the user must provide the "Fully Qualified Hostname" or IP address as a value for the property in the events-service-api-store.properties
file:
property ad.es.node.network.publish.host
Then save the file and restart the Events Service cluster.
Thank you! Your submission has been received!
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form