[
https://issues.apache.org/jira/browse/METRON-384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15430259#comment-15430259
]
ASF GitHub Bot commented on METRON-384:
---------------------------------------
GitHub user 2xyo opened a pull request:
https://github.com/apache/incubator-metron/pull/221
METRON-384 Allow elasticsearch to bind to loopback addresses
This PR addresses https://issues.apache.org/jira/browse/METRON-384
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/2xyo/incubator-metron patch-4
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-metron/pull/221.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #221
----
commit 91c204b8eb088d4aa52c7f06ad481eba171f1d8e
Author: 2*yo <yoh...@lepage.info>
Date: 2016-08-22T07:55:51Z
METRON-384 Allow elasticsearch to bind to loopback addresses
This PR addresses https://issues.apache.org/jira/browse/METRON-384
----
> Deployment fails at task "Wait for Elasticsearch Host to Start"
> ----------------------------------------------------------------
>
> Key: METRON-384
> URL: https://issues.apache.org/jira/browse/METRON-384
> Project: Metron
> Issue Type: Bug
> Environment: $ git rev-parse HEAD
> 225a490cf4a475e728bf9129ea3e662b543f5cc4
> Reporter: Yohann
> Labels: deployment
>
> The deployments fails at task "metron_elasticsearch_templates : Wait for
> Elasticsearch Host to Start" even if elasticsearch is up and running.
> {code}
> TASK [metron_elasticsearch_templates : Wait for Elasticsearch Host to Start]
> ***
> fatal: [node1]: FAILED! => {"changed": false, "elapsed": 300, "failed": true,
> "msg": "Timeout when waiting for node1:9200"}
> {code}
> On metron node:
> {code}
> [root@node1 ~]# lsof -P -n -iTCP -sTCP:LISTEN | grep elasticsearch
> java 12684 elasticsearch 117u IPv6 181670 0t0 TCP
> 192.168.1.13:9300 (LISTEN)
> java 12684 elasticsearch 146u IPv6 181879 0t0 TCP
> 192.168.1.13:9200 (LISTEN)
> {code}
> Elasticsearch listens on the IP address of the interface while the name
> "node1" only resolves to 127.0.0.1.
> Resolution: listen to IP address of the interface and to 127.0.0.1:
> {code}
> diff --git a/metron-deployment/roles/elasticsearch/tasks/elasticsearch.yml
> b/metron-deployment/roles/elasticsearch/tasks/elasticsearch.yml
> index b5df7b9..92ef9c5 100644
> --- a/metron-deployment/roles/elasticsearch/tasks/elasticsearch.yml
> +++ b/metron-deployment/roles/elasticsearch/tasks/elasticsearch.yml
> @@ -66,8 +66,8 @@
> state=present
> with_items:
> - { regexp: '^# *cluster\.name:', line: 'cluster.name: metron' }
> - - { regexp: '^# *network\.host:', line: 'network.host: _{{
> - elasticsearch_network_interface }}:ipv4_' }
> + - { regexp: '^# *network\.host:', line: 'network.host: ["_{{
> + elasticsearch_network_interface }}:ipv4_","_local:ipv4_"]' }
> - { regexp: '^# *discovery\.zen\.ping\.unicast\.hosts:',
> line: 'discovery.zen.ping.unicast.hosts: [ {{ es_hosts }} ]'}
> - { regexp: '^# *path\.data', line: 'path.data: {{
> elasticsearch_data_dir }}' }
> {code}
> Result:
> {code}
> [root@node1 ~]# lsof -P -n -iTCP -sTCP:LISTEN | grep elasticsearch
> java 19741 elasticsearch 117u IPv6 202309 0t0 TCP 127.0.0.1:9300
> (LISTEN)
> java 19741 elasticsearch 119u IPv6 202312 0t0 TCP
> 192.168.1.13:9300 (LISTEN)
> java 19741 elasticsearch 147u IPv6 202382 0t0 TCP 127.0.0.1:9200
> (LISTEN)
> java 19741 elasticsearch 148u IPv6 202383 0t0 TCP
> 192.168.1.13:9200 (LISTEN)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
