Briefly, this error occurs when Elasticsearch is bound to an external network interface, triggering the enforcement of bootstrap checks. These checks are safety measures to prevent potential issues in a production environment. To resolve this, either bind Elasticsearch to a ‘localhost’ or ‘127.0.0.1’ for development purposes, or ensure your system passes all bootstrap checks for production use. This could involve adjusting system settings like increasing file descriptor count, disabling swapping, or configuring virtual memory.
This guide will help you check for common problems that cause the log ” bound or publishing to a non-loopback or non-link-local address; enforcing bootstrap checks ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: bootstrap checks.
Log Context
Log “bound or publishing to a non-loopback or non-link-local address; enforcing bootstrap checks” classname is BootstrapCheck.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
final Logger logger) throws NodeValidationException {
final List errors = new ArrayList();
final List ignoredErrors = new ArrayList();
if (enforceLimits) {
logger.info("bound or publishing to a non-loopback or non-link-local address; enforcing bootstrap checks");
}
for (final Check check : checks) {
if (check.check()) {
if (!enforceLimits && !check.alwaysEnforce()) {
