Knowledge Base

Showing results for 
Search instead for 
Did you mean: 

How to resolve Events Service not coming up

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]
  while locating

1 error
 at com.appdynamics.common.framework.Loaders.internalPrepareAndPreStart(
 at com.appdynamics.common.framework.Loaders.loadAndInitializeModules(
 at com.appdynamics.common.framework.AbstractApp.callRunServer(
 at com.appdynamics.common.framework.AbstractApp.runUsingFile(
 at com.appdynamics.common.framework.AbstractApp.runUsingTemplate(
 at com.appdynamics.common.framework.AbstractApp.runUsingTemplate(
Caused by: MasterNotDiscoveredException[null]
 at org.elasticsearch.cluster.ClusterStateObserver$ObserverClusterStateListener.onTimeout(
 at org.elasticsearch.cluster.service.InternalClusterService$
 at java.util.concurrent.ThreadPoolExecutor.runWorker(
 at java.util.concurrent.ThreadPoolExecutor$


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 file.


To resolve this issue, the user must provide the "Fully Qualified Hostname" or IP address as a value for the property in the file:




Then save the file and restart the Events Service cluster.

Version history
Revision #:
2 of 2
Last update:
‎08-31-2017 10:32 AM
Updated by:
Labels (1)

Found this article helpful? Click the Thumbs Up button.
Have an additional comment? Post it below.
0 Kudos