You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Roshan Naik (JIRA)" <ji...@apache.org> on 2012/11/28 20:25:58 UTC
[jira] [Created] (FLUME-1743) Multiport syslog tcp source does not
load (v1.3 rc5)
Roshan Naik created FLUME-1743:
----------------------------------
Summary: 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
Fix For: v1.3.0
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 = multiport_syslogtcp
# 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
Re: [jira] [Updated] (FLUME-1743) Multiport syslog tcp source
does not load (v1.3 rc5)
Posted by Brock Noland <br...@cloudera.com>.
Yes that is what it looks like to me, but it's not hurting anything asis.
--
Brock Noland
Sent with Sparrow (http://www.sparrowmailapp.com/?sig)
On Thursday, November 29, 2012 at 6:23 PM, Roshan Naik wrote:
> you mean the corresponding classes need to be created ?
>
>
> On Thu, Nov 29, 2012 at 3:54 PM, Brock Noland <br...@cloudera.com> wrote:
>
> > I actually don't think any of the classes exist an as such only basic
> > configuration checking is done. That is, the reference to the
> > non-existant class is not a problem but should be resolved in the long
> > run. I think this is the JIRA to resolve it:
> >
> > https://issues.apache.org/jira/browse/FLUME-1051
> >
> > Brock
> >
> > On Thu, Nov 29, 2012 at 5:45 PM, Roshan Naik <ro...@hortonworks.com>
> > wrote:
> > > I see that some of the enum values in SourceConfigurationType refer to
> >
> > non
> > > existent class names.
> > > Like for instance ...
> > >
> >
> > MULTIPORT_SYSLOGTCP("org.apache.flume.source.MultiportSyslogTCPSourceConfiguration")
> > >
> > > and
> > >
> > > EXEC("org.apache.flume.conf.source.ExecSourceConfiguration")
> > >
> > >
> > > It appears to me that they should be set to null like in the case of ...
> > >
> > > SEQ(null)
> > >
> > > If so i can go ahead and file a jira.
> >
> >
> >
> > --
> > Apache MRUnit - Unit testing MapReduce -
> > http://incubator.apache.org/mrunit/
> >
>
>
>
Re: [jira] [Updated] (FLUME-1743) Multiport syslog tcp source does
not load (v1.3 rc5)
Posted by Roshan Naik <ro...@hortonworks.com>.
you mean the corresponding classes need to be created ?
On Thu, Nov 29, 2012 at 3:54 PM, Brock Noland <br...@cloudera.com> wrote:
> I actually don't think any of the classes exist an as such only basic
> configuration checking is done. That is, the reference to the
> non-existant class is not a problem but should be resolved in the long
> run. I think this is the JIRA to resolve it:
>
> https://issues.apache.org/jira/browse/FLUME-1051
>
> Brock
>
> On Thu, Nov 29, 2012 at 5:45 PM, Roshan Naik <ro...@hortonworks.com>
> wrote:
> > I see that some of the enum values in SourceConfigurationType refer to
> non
> > existent class names.
> > Like for instance ...
> >
> >
> MULTIPORT_SYSLOGTCP("org.apache.flume.source.MultiportSyslogTCPSourceConfiguration")
> >
> > and
> >
> > EXEC("org.apache.flume.conf.source.ExecSourceConfiguration")
> >
> >
> > It appears to me that they should be set to null like in the case of ...
> >
> > SEQ(null)
> >
> > If so i can go ahead and file a jira.
>
>
>
> --
> Apache MRUnit - Unit testing MapReduce -
> http://incubator.apache.org/mrunit/
>
Re: [jira] [Updated] (FLUME-1743) Multiport syslog tcp source does
not load (v1.3 rc5)
Posted by Brock Noland <br...@cloudera.com>.
I actually don't think any of the classes exist an as such only basic
configuration checking is done. That is, the reference to the
non-existant class is not a problem but should be resolved in the long
run. I think this is the JIRA to resolve it:
https://issues.apache.org/jira/browse/FLUME-1051
Brock
On Thu, Nov 29, 2012 at 5:45 PM, Roshan Naik <ro...@hortonworks.com> wrote:
> I see that some of the enum values in SourceConfigurationType refer to non
> existent class names.
> Like for instance ...
>
> MULTIPORT_SYSLOGTCP("org.apache.flume.source.MultiportSyslogTCPSourceConfiguration")
>
> and
>
> EXEC("org.apache.flume.conf.source.ExecSourceConfiguration")
>
>
> It appears to me that they should be set to null like in the case of ...
>
> SEQ(null)
>
> If so i can go ahead and file a jira.
--
Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/
Re: [jira] [Updated] (FLUME-1743) Multiport syslog tcp source does
not load (v1.3 rc5)
Posted by Roshan Naik <ro...@hortonworks.com>.
I see that some of the enum values in SourceConfigurationType refer to non
existent class names.
Like for instance ...
MULTIPORT_SYSLOGTCP("org.apache.flume.source.MultiportSyslogTCPSourceConfiguration")
and
EXEC("org.apache.flume.conf.source.ExecSourceConfiguration")
It appears to me that they should be set to null like in the case of ...
SEQ(null)
If so i can go ahead and file a jira.
[jira] [Updated] (FLUME-1743) Multiport syslog tcp source does not
load (v1.3 rc5)
Posted by "Will McQueen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Will McQueen updated FLUME-1743:
--------------------------------
Priority: Blocker (was: Major)
> 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
[jira] [Updated] (FLUME-1743) Multiport syslog tcp source does not
load (v1.3 rc5)
Posted by "Roshan Naik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Roshan Naik updated FLUME-1743:
-------------------------------
Description:
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 = multiport_syslogtcp
## 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}} }
was:
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 = multiport_syslogtcp
# 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}} }
> 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
> Fix For: v1.3.0
>
>
> 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 = multiport_syslogtcp
> ## 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
[jira] [Updated] (FLUME-1743) Multiport syslog tcp source does not
load (v1.3 rc5)
Posted by "Hari Shreedharan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hari Shreedharan updated FLUME-1743:
------------------------------------
Attachment: FLUME-1743.patch
[~roshan_naik]: Does the source work with the FQCN?
Can someone verify that this patch is working if the short name is specified?
> 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
> 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
[jira] [Commented] (FLUME-1743) Multiport syslog tcp source does
not load (v1.3 rc5)
Posted by "Brock Noland (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13506542#comment-13506542 ]
Brock Noland commented on FLUME-1743:
-------------------------------------
You'll get that error if the tar.gz file is not found. Typically if you just run test without doing package or install.
> 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
[jira] [Commented] (FLUME-1743) Multiport syslog tcp source does
not load (v1.3 rc5)
Posted by "Hari Shreedharan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13505827#comment-13505827 ]
Hari Shreedharan commented on FLUME-1743:
-----------------------------------------
It happens with both the short and FQCN? Short name, I think is because the class is not added 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
> Fix For: v1.3.0
>
>
> 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
[jira] [Commented] (FLUME-1743) Multiport syslog tcp source does
not load (v1.3 rc5)
Posted by "Roshan Naik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13506093#comment-13506093 ]
Roshan Naik commented on FLUME-1743:
------------------------------------
I am trying out a patch after adding it to 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
> 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
[jira] [Commented] (FLUME-1743) Multiport syslog tcp source does
not load (v1.3 rc5)
Posted by "Roshan Naik (JIRA)" <ji...@apache.org>.
[ 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 <br...@apache.org>
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
[jira] [Commented] (FLUME-1743) Multiport syslog tcp source does
not load (v1.3 rc5)
Posted by "Will McQueen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13505922#comment-13505922 ]
Will McQueen commented on FLUME-1743:
-------------------------------------
Hi Hari,
Without the patch, both trunk and flume-1.3.0 fail to configure the source when either the FQCN or the short name is used. With the patch, both trunk and flume-1.3.0 branches successfully configure the source.
In this case, I would consider this issue a blocker for 1.3.0 release since it prevents the multiport syslog tcp source from working.
> 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
> 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
[jira] [Updated] (FLUME-1743) Multiport syslog tcp source does not
load (v1.3 rc5)
Posted by "Roshan Naik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Roshan Naik updated FLUME-1743:
-------------------------------
Description:
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}} }
was:
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 = multiport_syslogtcp
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}} }
> 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
> Fix For: v1.3.0
>
>
> 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
[jira] [Updated] (FLUME-1743) Multiport syslog tcp source does not
load (v1.3 rc5)
Posted by "Brock Noland (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brock Noland updated FLUME-1743:
--------------------------------
Assignee: Hari Shreedharan
> 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
[jira] [Updated] (FLUME-1743) Multiport syslog tcp source does not
load (v1.3 rc5)
Posted by "Roshan Naik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Roshan Naik updated FLUME-1743:
-------------------------------
Description:
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 = multiport_syslogtcp
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}} }
was:
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 = multiport_syslogtcp
## 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}} }
> 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
> Fix For: v1.3.0
>
>
> 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 = multiport_syslogtcp
> 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
[jira] [Commented] (FLUME-1743) Multiport syslog tcp source does
not load (v1.3 rc5)
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ 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