IPv6 support for elastic search 5.4


(Nihar) #1

Hi All,

I am trying to install elasticsearch 5.4 on a pure IPv6 machine.

Is this supported?

I am getting "GetIpAddrTable function failed" errors while starting the service.

Any pointers on the same how to get this going?

Thanks in Advance,
Nihar


(Mark Walkom) #2

Can you post the entire error and your config file?


(Nihar) #3

Hi Mark,

I am getting following error:

C:\Elasticsearch\elasticsearch-5.4.0\bin>elasticsearch.bat
[2017-05-25T13:07:33,912][ERROR][o.e.b.ElasticsearchUncaughtExceptionHandler] [vw-vc-qa54-vm6] fatal error in thread [main], exiting
java.lang.Error: IP Helper Library GetIpAddrTable function failed
at java.net.NetworkInterface.getAll(Native Method) ~[?:1.8.0_111]
at java.net.NetworkInterface.getNetworkInterfaces(NetworkInterface.java:343) ~[?:1.8.0_111]
at sun.security.provider.SeedGenerator.addNetworkAdapterInfo(SeedGenerator.java:233) ~[?:1.8.0_111]
at sun.security.provider.SeedGenerator.access$000(SeedGenerator.java:80) ~[?:1.8.0_111]
at sun.security.provider.SeedGenerator$1.run(SeedGenerator.java:183) ~[?:1.8.0_111]
at sun.security.provider.SeedGenerator$1.run(SeedGenerator.java:168) ~[?:1.8.0_111]
at java.security.AccessController.doPrivileged(Native Method) ~[?:1.8.0_111]
at sun.security.provider.SeedGenerator.getSystemEntropy(SeedGenerator.java:168) ~[?:1.8.0_111]
at sun.security.provider.SecureRandom$SeederHolder.(SecureRandom.java:201) ~[?:1.8.0_111]
at sun.security.provider.SecureRandom.engineNextBytes(SecureRandom.java:221) ~[?:1.8.0_111]
at java.security.SecureRandom.nextBytes(SecureRandom.java:468) ~[?:1.8.0_111]
at java.security.SecureRandom.next(SecureRandom.java:491) ~[?:1.8.0_111]
at java.util.Random.nextLong(Random.java:424) ~[?:1.8.0_111]
at java.io.File$TempDirectory.generateFile(File.java:1905) ~[?:1.8.0_111]
at java.io.File.createTempFile(File.java:2010) ~[?:1.8.0_111]
at com.sun.jna.Native.extractFromResourcePath(Native.java:1059) ~[jna-4.4.0.jar:4.4.0 (b0)]
at com.sun.jna.Native.loadNativeDispatchLibraryFromClasspath(Native.java:937) ~[jna-4.4.0.jar:4.4.0 (b0)]
at com.sun.jna.Native.loadNativeDispatchLibrary(Native.java:922) ~[jna-4.4.0.jar:4.4.0 (b0)]
at com.sun.jna.Native.(Native.java:190) ~[jna-4.4.0.jar:4.4.0 (b0)]
at java.lang.Class.forName0(Native Method) ~[?:1.8.0_111]
at java.lang.Class.forName(Class.java:264) ~[?:1.8.0_111]
at org.elasticsearch.bootstrap.Natives.(Natives.java:45) ~[elasticsearch-5.4.0.jar:5.4.0]
at org.elasticsearch.bootstrap.Bootstrap.initializeNatives(Bootstrap.java:105) ~[elasticsearch-5.4.0.jar:5.4.0]
at org.elasticsearch.bootstrap.Bootstrap.setup(Bootstrap.java:204) ~[elasticsearch-5.4.0.jar:5.4.0]
at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:360) ~[elasticsearch-5.4.0.jar:5.4.0]
at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:123) ~[elasticsearch-5.4.0.jar:5.4.0]
at org.elasticsearch.bootstrap.Elasticsearch.execute(Elasticsearch.java:114) ~[elasticsearch-5.4.0.jar:5.4.0]
at org.elasticsearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:67) ~[elasticsearch-5.4.0.jar:5.4.0]
at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:122) ~[elasticsearch-5.4.0.jar:5.4.0]
at org.elasticsearch.cli.Command.main(Command.java:88) ~[elasticsearch-5.4.0.jar:5.4.0]
at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:91) ~[elasticsearch-5.4.0.jar:5.4.0]
at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:84) ~[elasticsearch-5.4.0.jar:5.4.0]


Config file


======================== Elasticsearch Configuration =========================

NOTE: Elasticsearch comes with reasonable defaults for most settings.

Before you set out to tweak and tune the configuration, make sure you

understand what are you trying to accomplish and the consequences.

The primary way of configuring a node is via this file. This template lists

the most important settings you may want to configure for a production cluster.

Please consult the documentation for further information on configuration options:

https://www.elastic.co/guide/en/elasticsearch/reference/index.html

---------------------------------- Cluster -----------------------------------

Use a descriptive name for your cluster:

cluster.name: IPv6_Cluster

------------------------------------ Node ------------------------------------

Use a descriptive name for the node:

node.name: vw-vc-qa54-vm6

Add custom attributes to the node:

#node.attr.rack: r1

----------------------------------- Paths ------------------------------------

Path to directory where to store the data (separate multiple locations by comma):

#path.data: /path/to/data

Path to log files:

#path.logs: /path/to/logs

----------------------------------- Memory -----------------------------------

Lock the memory on startup:

#bootstrap.memory_lock: true

Make sure that the heap size is set to about half the memory available

on the system and that the owner of the process is allowed to use this

limit.

Elasticsearch performs poorly when the system is swapping the memory.

---------------------------------- Network -----------------------------------

Set the bind address to a specific IP (IPv4 or IPv6):

network.host: 2001:500:100:1152:c4cf:1c4:49e0:eb47

Set a custom port for HTTP:

#http.port: 9200

For more information, consult the network module documentation.

--------------------------------- Discovery ----------------------------------

Pass an initial list of hosts to perform discovery when new node is started:

The default list of hosts is ["127.0.0.1", "[::1]"]

#discovery.zen.ping.unicast.hosts: ["host1", "host2"]

Prevent the "split brain" by configuring the majority of nodes (total number of master-eligible nodes / 2 + 1):

#discovery.zen.minimum_master_nodes: 3

For more information, consult the zen discovery module documentation.

---------------------------------- Gateway -----------------------------------

Block initial recovery after a full cluster restart until N nodes are started:

#gateway.recover_after_nodes: 3

For more information, consult the gateway module documentation.

---------------------------------- Various -----------------------------------

Require explicit names when deleting indices:

#action.destructive_requires_name: true

Thanks,
Nihar


(system) #4

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.