From 1b267c475c45ac8e468cf5e8a793b8a36d32fd5f Mon Sep 17 00:00:00 2001
From: Jonathan Rosser <jonathan.rosser@rd.bbc.co.uk>
Date: Wed, 5 Sep 2018 10:45:23 +0000
Subject: [PATCH] Ensure logstash listens on ipv4 address
Upgrading the ELK stack to 6.4.0 leaves logstash only listening on
an ipv6 address and thereby unable to receive existing beats inputs.
This change makes the jvm prefer binding to ipv4 addresses.
Change-Id: I04a0fdbcb253a0a6a3bcc3759eb0b9d0f1962621
---
.../roles/elastic_dependencies/templates/jvm.options.j2 | 3 +++
1 file changed, 3 insertions(+)
diff --git a/elk_metrics_6x/roles/elastic_dependencies/templates/jvm.options.j2 b/elk_metrics_6x/roles/elastic_dependencies/templates/jvm.options.j2
index c0130f32..e4e4e921 100644
--- a/elk_metrics_6x/roles/elastic_dependencies/templates/jvm.options.j2
+++ b/elk_metrics_6x/roles/elastic_dependencies/templates/jvm.options.j2
@@ -83,5 +83,8 @@
# ensure the directory exists
#-Xloggc:${LS_GC_LOG_FILE}
+#listen on IPv4 addresses
+-Djava.net.preferIPv4Stack=true
+
# Disable log4j because its not supported by elastic
-Dlog4j2.disable.jmx=true