Briefly, this error occurs when the Elasticsearch readiness service is successfully started and running on a specific port. This is not an error message, but rather an informational message indicating that the service is functioning as expected. If you’re seeing this message frequently or in an unexpected context, you may want to check your system’s logging settings or investigate whether the service is being restarted frequently. If you’re having trouble connecting to the service, ensure that any firewalls or network settings are correctly configured to allow traffic on the specified port.
This guide will help you check for common problems that cause the log ” readiness service up and running on {} ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: .
Log Context
Log “readiness service up and running on {}” classname is ReadinessService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
} finally {
listenerThreadLatch.countDown();
}
}; "elasticsearch[readiness-service]").start();
logger.info("readiness service up and running on {}"; boundAddress().publishAddress());
}
@Override
protected void doStop() {
this.active = false;
