ChrisSamo632 commented on PR #6658: URL: https://github.com/apache/nifi/pull/6658#issuecomment-1426492811
The `integration-tests` (with update `verifySniffer` logic) just revealed that the Elasticsearch instance's `network.publish_address` **must** be one of the `network.bind_address`(es) for the Sniffer to work - this wasn't the case by default for the TestContainer running Elasticsearch, so it could be an issue like that - again, I've added a note to the `Sniffer` property and the `integration-tests` now set `network.bind_address` to [site](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-network.html#network-interface-values), which allows them to pass on both Elasticsearch 7.x and 8.x (no TLS but with Auth enabled) Going back to the earlier Docker question - is it that you're running Elasticsearch as a Docker container but NiFi "natively" on your machine, connecting to Elasticsearch using `localhost` and then the Elasticsearch instance is reporting back the Docker-internal address of `172.17.0.3`? What do you see under the `http` section of the response from a call to your Elasticsearch's `GET /_nodes/http` API? With an Elasticsearch Docker container running, I get: ```json "http": { "bound_address": [ "0.0.0.0:9200" ], "publish_address": "172.20.0.2:9200", "max_content_length_in_bytes": 104857600 } ``` which isn't contactable from my browser/terminal - so I suspect this is indeed what's going on for you, i.e. your Elasticsearch instance is reporting back its "internal" IP as its `publish_address` and you'd need to re-configure the instance's `network.publish_address` (or run NiFi within the Docker network **or** use the `host` network for your Elasticsearch container) so that the correct combination of `publish_address` and host network routing can be used -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
