Getting "lumberjack All host unavailable, sleeping" error when Logstash-to-Logstash communication is configured

Elastic Stack Logstash
1

Logstash Version: 6.4.1

Use case: Logstash-to-Logstash Communication

Upstream hostname : node-1 (IP 172.30.64.98)
Downstream hostname : node-2 (IP 172.30.64.115)

In /etc/hosts both hostname is already mentioned and both hosts is accessible by each other.

Execution Steps:

  1. Generate a trusted SSL certificate under /usr/share/logstash/bin in Upstream host
    # openssl req -x509 -batch -nodes -newkey rsa:2048 -keyout lumberjack.key -out lumberjack.cert -subj /CN=node1

  2. Copy the SSL certificate and key to the downstream Logstash machine
    # scp /usr/share/logstash/bin/lumberjack.* root@node2:/usr/share/logstash/bin

  3. Start the downstream logstash instance
    # cd /usr/share/logstash/bin
    # ./logstash -e 'input { beats { codec => json port => 5000 ssl => true ssl_certificate => "lumberjack.cert" ssl_key => "lumberjack.key"} }'

  4. Start the upstream logstash instance
    # cd /usr/share/logstash/bin
    # ./logstash -e 'input { generator { count => 5 } } output { lumberjack { codec => json hosts => "mydownstreamhost" ssl_certificate => "lumberjack.cert" port => 5000 } }'

During the Starting of upstream logstance instance I am getting below error
[ERROR] 2019-05-07 12:16:49.471 [[main]-pipeline-manager] lumberjack - All hosts unavailable, sleeping {:hosts=>["172.30.64.115"], :e=>#<Errno::EHOSTUNREACH: No route to host - SocketChannel.connect>, :

Is there any specific solution regarding this issue?

1 Like
2

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