Problem background and phenomenon
Install the Flume client and set the avro sink to communicate with the server. It is found that the Flume server cannot
be connected.
Cause Analysis
1. The server configuration is incorrect, and the listening port fails to start. For example, the server avro source is configured
with the wrong IP or the port that has already been occupied. View the Flume server running log:
2016-08-31 09:28,092 | ERROR | [lifecycleSupervisor-1-9] | Unable to start EventDrivenSourceRunner: { source:Avro source
avro_source: { bindAddress: 189.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 09:28,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/huawei/Bigdata/FusionInsight/FusionInsight-Flume-1.6.0/flume/conf/flume_sChat.jks
3. The client and server communicate abnormally.
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
Step 1 Set to the correct IP, it must be the IP of the local machine. If the port is occupied, reconfigure an idle port.
Step 2 Configure the correct certification path.
Step 3 Contact your network administrator to restore the network.
