On Wed, Jun 6, 2012 at 5:13 PM, Mike Percy <[email protected]> wrote:
> Hi Mohit, > That change is on trunk. > > However what you can do is instead specify the whole class name instead of > using the "syslogtcp" alias, i.e. > > syslog-agent.sources.Syslog.type = > org.apache.flume.source.SyslogTcpSource > > The main drawback is that you will be missing some bug fixes improvements > that were done since 1.1.0. > > Thanks. I am on 1.2.0. Do you think I should upgrade or I'll be ok? > Mike > > On Wednesday, June 6, 2012 at 5:01 PM, Mohit Anchlia wrote: > > Looks like related to https://issues.apache.org/jira/browse/FLUME-1017 > > Are there any jars available or do I need to rebuild? > On Wed, Jun 6, 2012 at 4:49 PM, Mohit Anchlia <[email protected]>wrote: > > I am trying out example from this site > http://mapredit.blogspot.de/2012/03/flumeng-evolution.html > > > When I run the node I get. Am I doing something wrong? > > 12/06/06 16:50:05 ERROR properties.PropertiesFileConfigurationProvider: > Failed to load configuration data. Exception follows. > > org.apache.flume.FlumeException: Unable to load source type: syslogtcp, > class: syslogtcp > > at > org.apache.flume.source.DefaultSourceFactory.create(DefaultSourceFactory.java:92) > > at > org.apache.flume.conf.properties.PropertiesFileConfigurationProvider.loadSources(PropertiesFileConfigurationProvider.java:267) > > > >
