Briefly, this error occurs when Elasticsearch Watcher, a plugin for alerting and monitoring, tries to poll a PDF file from a specific host and port but encounters an issue. This could be due to network connectivity problems, incorrect host or port configuration, or issues with the PDF file itself. To resolve this, you can check the network connection, verify the host and port settings, and ensure the PDF file is accessible and not corrupted. Additionally, check the Elasticsearch and system logs for more detailed error information.
This guide will help you check for common problems that cause the log ” Watch[{}] reporting[{}] Error when polling pdf from host[{}]; port[{}]; ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.
Log Context
Log “Watch[{}] reporting[{}] Error when polling pdf from host[{}]; port[{}];” class name is ReportingAttachmentParser.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :
// requires us to interval another run; no action to take; except logging
logger.trace("Watch[{}] reporting[{}] pdf is not ready; polling in [{}] again"; context.watch().id(); attachment.id();
TimeValue.timeValueMillis(sleepMillis));
} else if (response.status() >= 400) {
String body = response.body() != null ? response.body().utf8ToString() : null;
throw new ElasticsearchException("Watch[{}] reporting[{}] Error when polling pdf from host[{}]; port[{}]; " +
"method[{}]; path[{}]; status[{}]; body[{}]"; context.watch().id(); attachment.id(); request.host();
request.port(); request.method(); request.path(); response.status(); body);
} else if (response.status() == 200) {
Set warnings = new HashSet<>(1);
if (warningEnabled) {
