flume报错客户机无法正常启动

最新推荐文章于 2024-06-17 14:24:53 发布

原创最新推荐文章于 2024-06-17 14:24:53 发布 · 833 阅读

0 ·

CC 4.0 BY-SA版权

文章标签：

#flume

Flume 专栏收录该内容

3 篇文章

订阅专栏

博客详细记录了在启动Flume时遇到的`FlumeException`，指出由于配置错误导致服务器socket无法正常设置。问题根源在于`avro-logger.txt`文件存在两处错误：文件名应更改为`avro-logger.conf`，以及配置文件中的源和接收端口设置不正确。修复这两处错误后，Flume成功启动并恢复正常运行。

Exception follows.
org.apache.flume.FlumeException: Failed to set up server socket
at org.apache.flume.source.AvroSource.start(AvroSource.java:248)
at org.apache.flume.source.EventDrivenSourceRunner.start(EventDrivenSourceRunner.java:44)
at org.apache.flume.lifecycle.LifecycleSupervisor $M o n i t o r R u n n a b l e . r u n (L i f e c y c l e S u p e r v i s o r . j a v a : 249) a t j a v a . u t i l . c o n c u r r e n t . E x e c u t o r s$ RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access $301 (S c h e d u l e d T h r e a d P o o l E x e c u t o r . j a v a : 180) a t j a v a . u t i l . c o n c u r r e n t . S c h e d u l e d T h r e a d P o o l E x e c u t o r$ ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor $W o r k e r . r u n (T h r e a d P o o l E x e c u t o r . j a v a : 624) a t j a v a . l a n g . T h r e a d . r u n (T h r e a d . j a v a : 748) C a u s e d b y : o r g . j b o s s . n e t t y . c h a n n e l . C h a n n e l E x c e p t i o n : F a i l e d t o b i n d t o : b i g d a t a 03 / 192.168.52.223 : 52020 a t o r g . j b o s s . n e t t y . b o o t s t r a p . S e r v e r B o o t s t r a p . b i n d (S e r v e r B o o t s t r a p . j a v a : 272) a t o r g . a p a c h e . a v r o . i p c . N e t t y S e r v e r . < i n i t > (N e t t y S e r v e r . j a v a : 106) a t o r g . a p a c h e . f l u m e . s o u r c e . A v r o S o u r c e . s t a r t (A v r o S o u r c e . j a v a : 243) . . . 9 m o r e C a u s e d b y : j a v a . n e t . B i n d E x c e p t i o n : C a n n o t a s s i g n r e q u e s t e d a d d r e s s a t s u n . n i o . c h . N e t . b i n d 0 (N a t i v e M e t h o d) a t s u n . n i o . c h . N e t . b i n d (N e t . j a v a : 433) a t s u n . n i o . c h . N e t . b i n d (N e t . j a v a : 425) a t s u n . n i o . c h . S e r v e r S o c k e t C h a n n e l I m p l . b i n d (S e r v e r S o c k e t C h a n n e l I m p l . j a v a : 223) a t s u n . n i o . c h . S e r v e r S o c k e t A d a p t o r . b i n d (S e r v e r S o c k e t A d a p t o r . j a v a : 74) a t o r g . j b o s s . n e t t y . c h a n n e l . s o c k e t . n i o . N i o S e r v e r B o s s$ RegisterTask.run(NioServerBoss.java:193)
at org.jboss.netty.channel.socket.nio.AbstractNioSelector.processTaskQueue(AbstractNioSelector.java:372)
at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:296)
at org.jboss.netty.channel.socket.nio.NioServerBoss.run(NioServerBoss.java:42)
at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
at org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)

今天反复一台客户机报错,检查之后,发现是
avro-logger.txt有2处错误:
1.avro-logger.txt 修改为:avro-logger.conf;
2.配置错误,按照以下配置更新后
a1.sources = r1
a1.sinks = k1
a1.channels = c1

a1.sources.r1.type = avro
a1.sources.r1.channels = c1
a1.sources.r1.bind = bigdata03
a1.sources.r1.port = 52020

a1.sinks.k1.type = logger
a1.channels.c1.type = memory
a1.channels.c1.capacity = 1000
a1.channels.c1.transactionCapacity = 100
a1.sources.r1.channels = c1
a1.sinks.k1.channel = c1

果然又恢复了正常