A Flume Client Cannot Connect to the Server

Symptom

A user installs a Flume client and sets an Avro sink to communicate with the server. However, the Flume server cannot be connected.

Cause Analysis

1. The server is incorrectly configured and the monitoring port fails to be started. For example, an incorrect IP address or an occupied port is configured for the Avro source of the server.
   View Flume run logs.

   2016-08-31 17:28:42,092 | ERROR | [lifecycleSupervisor-1-9] |  Unable to start EventDrivenSourceRunner: { source:Avro source avro_source: { bindAddress: 10.120.205.7, port: 21154 } } - Exception follows.  | org.apache.flume.lifecycle.LifecycleSupervisor$MonitorRunnable.run(LifecycleSupervisor.java:253)
   java.lang.RuntimeException: org.jboss.netty.channel.ChannelException: Failed to bind to: /192.168.205.7:21154

2. If encrypted transmission is used, the certificate or password is incorrect.

   2016-08-31 17:15:59,593 | ERROR | [conf-file-poller-0] |  Source avro_source has been removed due to an error during configuration  | org.apache.flume.node.AbstractConfigurationProvider.loadSources(AbstractConfigurationProvider.java:388)
   org.apache.flume.FlumeException: Avro source configured with invalid keystore: /opt/Bigdata/MRS_XXX/install/FusionInsight-Flume-1.9.0/flume/conf/flume_sChat.jks

3. The network connection between the client and the server is abnormal.

   PING 192.168.85.55 (10.120.85.55) 56(84) bytes of data.
   From 192.168.85.50 icmp_seq=1 Destination Host Unreachable
   From 192.168.85.50 icmp_seq=2 Destination Host Unreachable
   From 192.168.85.50 icmp_seq=3 Destination Host Unreachable
   From 192.168.85.50 icmp_seq=4 Destination Host Unreachable

Solution

1. Set a correct IP address (an IP address of the local host). If the port has been occupied, configure another free port.
2. Configure a correct certificate path.
3. Contact the network administrator to restore the network.