Knowledge Base

cancel
Showing results for 
Search instead for 
Did you mean: 

How do I solve a "failed to resolve address" error after upgrading the Events Service to 4.3?

Symptoms

The Events Service does not start after upgrading from version 4.2 to version 4.3.

 

The following error message appears in events-service/logs/events-service-api-store.log:

1) Error injecting constructor, java.lang.IllegalArgumentException: Failed to resolve address for [10.132.1.114[9300-9400]]
at org.elasticsearch.discovery.zen.ping.unicast.UnicastZenPing.<init>(Unknown Source)
while locating org.elasticsearch.discovery.zen.ping.unicast.UnicastZenPing
while locating org.elasticsearch.discovery.zen.ping.ZenPing annotated with @org.elasticsearch.common.inject.multibindings.Element(setName=,uniqueId=19)
at _unknown_
while locating java.util.Set<org.elasticsearch.discovery.zen.ping.ZenPing>
for parameter 1 at org.elasticsearch.discovery.zen.ping.ZenPingService.<init>(Unknown Source)
while locating org.elasticsearch.discovery.zen.ping.ZenPingService
for parameter 6 at org.elasticsearch.discovery.zen.ZenDiscovery.<init>(Unknown Source)
while locating org.elasticsearch.discovery.zen.ZenDiscovery
while locating org.elasticsearch.discovery.Discovery
for parameter 3 at org.elasticsearch.node.service.NodeService.<init>(Unknown Source)
while locating org.elasticsearch.node.service.NodeService
Caused by: java.lang.IllegalArgumentException: Failed to resolve address for [10.132.1.114[9300-9400]]

 

Diagnosis

Following the steps in the Upgrade the Events Service documentation, the user moves the data directory and copies all properties in the events-service-api-store.properties file located in the events-service/conf/ directory to the new config directory.

 

The user then sees the following error after starting the Events Service:

1) Error injecting constructor, java.lang.IllegalArgumentException: Failed to resolve address for [10.132.1.114[9300-9400]]

 This is due to a change in the value of the property ad.es.node.unicast.hosts within the properties file in version 4.3.

 

Version 4.2 example:

ad.es.node.unicast.hosts=node1.example.com[9300-9400],node2.example.com[9300-9400],node3.example.com[9300-9400]

Version 4.3 example:

ad.es.node.unicast.hosts=node1.example.com:9300,node2.example.com:9300,node3.example.com:9300

 

Solution

Do not enter a range for the ad.es.node.unicast.hosts property when copying and pasting old properties into the new property file.  

 

Instead of: 

node1.example.com[9300-9400]

 

Enter: 

node1.example.com:9300

 

Version history
Revision #:
5 of 5
Last update:
‎09-14-2018 01:39 PM
Updated by:
 
Labels (1)
0 Kudos