[ 
https://issues.apache.org/jira/browse/FLUME-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13507000#comment-13507000
 ] 

Hudson commented on FLUME-1743:
-------------------------------

Integrated in flume-trunk #333 (See 
[https://builds.apache.org/job/flume-trunk/333/])
    FLUME-1743: Multiport syslog tcp source does not load (v1.3 rc5) (Revision 
ff75006dcea040f0013c77ed3823d1e5246014bf)

     Result = UNSTABLE
brock : 
http://git-wip-us.apache.org/repos/asf/flume/repo?p=flume.git&a=commit&h=ff75006dcea040f0013c77ed3823d1e5246014bf
Files : 
* 
flume-ng-configuration/src/main/java/org/apache/flume/conf/source/SourceConfiguration.java

                
> 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
>            Assignee: Hari Shreedharan
>            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

Reply via email to