syslog classes missing
----------------------
Key: FLUME-1017
URL: https://issues.apache.org/jira/browse/FLUME-1017
Project: Flume
Issue Type: Bug
Components: Sinks+Sources
Affects Versions: NG alpha 1
Reporter: Alexander Lorenz-Alten
Priority: Blocker
Fix For: v1.1.0
bin/flume-ng agent -n syslog-agent -f conf/flume-conf.properties.template
Warning: No configuration directory set! Use --conf <dir> to override.
12/03/03 09:57:34 INFO lifecycle.LifecycleSupervisor: Starting lifecycle
supervisor 1
12/03/03 09:57:34 INFO node.FlumeNode: Flume node starting - syslog-agent
12/03/03 09:57:34 INFO nodemanager.DefaultLogicalNodeManager: Node manager
starting
12/03/03 09:57:34 INFO lifecycle.LifecycleSupervisor: Starting lifecycle
supervisor 10
12/03/03 09:57:34 INFO properties.PropertiesFileConfigurationProvider:
Configuration provider starting
12/03/03 09:57:34 INFO properties.PropertiesFileConfigurationProvider:
Reloading configuration file:conf/flume-conf.properties.template
12/03/03 09:57:34 WARN properties.FlumeConfiguration: Agent configuration for
'exec-agent' source 'tail' has no valid channels. Removing.
12/03/03 09:57:34 WARN properties.FlumeConfiguration: Agent configuration for
'exec-agent': source 'ExecTail' does not have 'type' specified.
12/03/03 09:57:34 WARN properties.FlumeConfiguration: Agent configuration for
'exec-agent': source 'ExecTail' has some required attributes missing. Removing.
12/03/03 09:57:34 WARN properties.FlumeConfiguration: Agent configuration for
'exec-agent': source 'ExecTail' is not configured. Removing.
12/03/03 09:57:34 INFO properties.FlumeConfiguration: Post-validation flume
configuration contains configuation for agents: [foo, exec-agent, syslog-agent]
12/03/03 09:57:34 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:265)
at
org.apache.flume.conf.properties.PropertiesFileConfigurationProvider.load(PropertiesFileConfigurationProvider.java:213)
at
org.apache.flume.conf.file.AbstractFileConfigurationProvider.doLoad(AbstractFileConfigurationProvider.java:124)
at
org.apache.flume.conf.file.AbstractFileConfigurationProvider.access$300(AbstractFileConfigurationProvider.java:38)
at
org.apache.flume.conf.file.AbstractFileConfigurationProvider$FileWatcherRunnable.run(AbstractFileConfigurationProvider.java:203)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at
java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: java.lang.ClassNotFoundException: syslogTcp
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:169)
at
org.apache.flume.source.DefaultSourceFactory.create(DefaultSourceFactory.java:90)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
