[
https://issues.apache.org/jira/browse/FLUME-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13506173#comment-13506173
]
Roshan Naik commented on FLUME-1743:
------------------------------------
The patch works but i see a different error which does not seem related but
here it is. i thought this was fixed.
testInOut(org.apache.flume.test.agent.TestFileChannel): Failed to locate
tar-ball distribution. Please specify explicitly via system property:
flume.dist.tarball
testInOut(org.apache.flume.test.agent.TestFileChannel): Failed to locate
tar-ball distribution. Please specify explicitly via system property:
flume.dist.tarball
testRpcClient(org.apache.flume.test.agent.TestRpcClient): Failed to locate
tar-ball distribution. Please specify explicitly via system property:
flume.dist.tarball
testRpcClient(org.apache.flume.test.agent.TestRpcClient): Failed to locate
tar-ball distribution. Please specify explicitly via system property:
flume.dist.tarball
testFailure(org.apache.flume.test.agent.TestRpcClientCommunicationFailure):
Failed to locate tar-ball distribution. Please specify explicitly via system
property: flume.dist.tarball
Latest:
commit 54330dcc62aa91d8c4d27dbf7135d9972ac7af84
Author: Brock Noland <[email protected]>
Date: Wed Nov 21 09:57:24 2012 -0600
FLUME-1730: HDFSEventSink testCloseOnIdle appears to be racy
(Brock Noland via Brock Noland
> Multiport syslog tcp source does not load (v1.3 rc5)
> ----------------------------------------------------
>
> Key: FLUME-1743
> URL: https://issues.apache.org/jira/browse/FLUME-1743
> Project: Flume
> Issue Type: Bug
> Components: Sinks+Sources
> Affects Versions: v1.3.0
> Reporter: Roshan Naik
> Priority: Blocker
> Fix For: v1.3.0
>
> Attachments: FLUME-1743.patch
>
>
> Multiport syslog tcp source problem ..
> Here is the config I am using...
> agent1.channels = memoryChannel
> agent1.channels.memoryChannel.type = memory
> agent1.sources = src0
> agent1.sources.src0.type = org.apache.flume.source.MultiportSyslogTCPSource
> agent1.sources.src0.channels = memoryChannel
> agent1.sources.src0.host = localhost
> agent1.sources.src0.ports = 10001 10002 10003
> agent1.sources.src0.portHeader = port
> agent1.sinks = fileRoll
> agent1.sinks.fileRoll.type = file_roll
> agent1.sinks.fileRoll.channel = memoryChannel
> agent1.sinks.fileRoll.sink.directory = output
> agent1.sinks.fileRoll.sink.rollInterval = -1
> Here is the error...
> 2/11/27 19:46:24 INFO conf.FlumeConfiguration: Processing:fileRoll
> 12/11/27 19:46:24 INFO conf.FlumeConfiguration: Processing:fileRoll
> 12/11/27 19:46:24 INFO conf.FlumeConfiguration: Processing:fileRoll
> 12/11/27 19:46:24 INFO conf.FlumeConfiguration: Processing:fileRoll
> 12/11/27 19:46:24 INFO conf.FlumeConfiguration: Added sinks: fileRoll Agent:
> agent1
> *12/11/27 19:46:24 WARN conf.FlumeConfiguration: Removed src0 due to Could
> not create configuration!*
> 12/11/27 19:46:24 INFO conf.FlumeConfiguration: Post-validation flume
> configuration contains configuration for agents: [agent1]
> 12/11/27 19:46:24 INFO properties.PropertiesFileConfigurationProvider:
> Creating channels
> 12/11/27 19:46:24 INFO properties.PropertiesFileConfigurationProvider:
> created channel memoryChannel
> 12/11/27 19:46:24 INFO sink.DefaultSinkFactory: Creating instance of sink:
> fileRoll, type: file_roll
> 12/11/27 19:46:24 INFO nodemanager.DefaultLogicalNodeManager: Starting new
> configuration:{ sourceRunners:{} sinkRunners:{fileRoll=SinkRunner: {
> policy:org.apache.flume.sink.DefaultSinkProcessor@44a613f8 counterGroup:{
> name:null counters:{} } }}
> channels:{memoryChannel=org.apache.flume.channel.MemoryChannel{name:
> memoryChannel}} }
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
