You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Alexander Lorenz-Alten (Created) (JIRA)" <ji...@apache.org> on 2012/03/03 09:59:56 UTC

[jira] [Created] (FLUME-1017) syslog classes missing

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

        

[jira] [Commented] (FLUME-1017) syslog classes missing

Posted by "Will McQueen (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/FLUME-1017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13249253#comment-13249253 ] 

Will McQueen commented on FLUME-1017:
-------------------------------------

I would have liked to see the SYSLOG_TCP and SYSLOG_UDP instead, to match the current convention of separating words with underscores like we currently do with FILE_ROLL.
                
> 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
>            Assignee: Hari Shreedharan
>            Priority: Blocker
>              Labels: sources, syslog
>             Fix For: v1.2.0
>
>         Attachments: FLUME-1017-1.patch, flume.log, web.conf
>
>
> 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

        

[jira] [Updated] (FLUME-1017) syslog classes missing

Posted by "Hari Shreedharan (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FLUME-1017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hari Shreedharan updated FLUME-1017:
------------------------------------

    Attachment: FLUME-1017-1.patch
    
> 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
>            Assignee: Hari Shreedharan
>            Priority: Blocker
>              Labels: sources, syslog
>             Fix For: v1.2.0
>
>         Attachments: FLUME-1017-1.patch, flume.log, web.conf
>
>
> 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

        

[jira] [Updated] (FLUME-1017) syslog classes missing

Posted by "Arvind Prabhakar (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FLUME-1017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Arvind Prabhakar updated FLUME-1017:
------------------------------------

    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

Patch committed. Thanks Hari!

@Rafael - let us move the discussion on syslog source dropping events to FLUME-1103 which is filed to track this problem.
                
> 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
>            Assignee: Hari Shreedharan
>            Priority: Blocker
>              Labels: sources, syslog
>             Fix For: v1.2.0
>
>         Attachments: FLUME-1017-1.patch, flume.log, web.conf
>
>
> 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

        

[jira] [Updated] (FLUME-1017) syslog classes missing

Posted by "Rafael Nunes (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FLUME-1017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rafael Nunes updated FLUME-1017:
--------------------------------

    Attachment: flume.log
                web.conf

agent's conf and log
                
> 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
>              Labels: sources, syslog
>             Fix For: v1.2.0
>
>         Attachments: flume.log, web.conf
>
>
> 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

        

[jira] [Issue Comment Edited] (FLUME-1017) syslog classes missing

Posted by "Rafael Nunes (Issue Comment Edited) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/FLUME-1017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13237913#comment-13237913 ] 

Rafael Nunes edited comment on FLUME-1017 at 3/25/12 4:27 PM:
--------------------------------------------------------------

@Arvind, hi.

I'm facing the same issue.
I took a look at the source code and find that in the package _org.apache.flume.source_ exists an _ENUM_ called _SourceType_ that doesn't have the syslogTcp type in it.

I'll try to implement this, but I'm too newbie as developer, so I thought that would be better, at least, point this out.

Here is the link to this _ENUM_ at the trunk:
https://svn.apache.org/repos/asf/incubator/flume/trunk/flume-ng-core/src/main/java/org/apache/flume/source/SourceType.java

Attached is the _conf_ used to my agent and its log.

Rgs.

                
      was (Author: datherra):
    agent's conf and log
                  
> 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
>              Labels: sources, syslog
>             Fix For: v1.2.0
>
>         Attachments: flume.log, web.conf
>
>
> 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

        

[jira] [Commented] (FLUME-1017) syslog classes missing

Posted by "jiraposter@reviews.apache.org (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/FLUME-1017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13247932#comment-13247932 ] 

jiraposter@reviews.apache.org commented on FLUME-1017:
------------------------------------------------------


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/4663/
-----------------------------------------------------------

Review request for Flume.


Summary
-------

Adding SyslogTcpSource and SyslogUDPSource to the enum.


This addresses bug FLUME-1017.
    https://issues.apache.org/jira/browse/FLUME-1017


Diffs
-----

  flume-ng-core/src/main/java/org/apache/flume/source/SourceType.java 9082470 

Diff: https://reviews.apache.org/r/4663/diff


Testing
-------

Builds fine, current unit tests are ok.


Thanks,

Hari


                
> 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
>            Assignee: Hari Shreedharan
>            Priority: Blocker
>              Labels: sources, syslog
>             Fix For: v1.2.0
>
>         Attachments: flume.log, web.conf
>
>
> 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

        

[jira] [Issue Comment Edited] (FLUME-1017) syslog classes missing

Posted by "Rafael Nunes (Issue Comment Edited) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/FLUME-1017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13237913#comment-13237913 ] 

Rafael Nunes edited comment on FLUME-1017 at 3/25/12 4:40 PM:
--------------------------------------------------------------

@Arvind, hi.

I'm facing the same issue.
I took a look at the source code and find that in the package _org.apache.flume.source_ exists an _ENUM_ called _SourceType_ that doesn't have the syslogTcp type in it.

I'll try to implement this, but I'm too newbie as developer, so I thought that would be better, at least, point this out.

Here is the link to this _ENUM_ at the trunk:
https://svn.apache.org/repos/asf/incubator/flume/trunk/flume-ng-core/src/main/java/org/apache/flume/source/SourceType.java

Attached is the _conf_ used by my agent and its log.

Rgs.

                
      was (Author: datherra):
    @Arvind, hi.

I'm facing the same issue.
I took a look at the source code and find that in the package _org.apache.flume.source_ exists an _ENUM_ called _SourceType_ that doesn't have the syslogTcp type in it.

I'll try to implement this, but I'm too newbie as developer, so I thought that would be better, at least, point this out.

Here is the link to this _ENUM_ at the trunk:
https://svn.apache.org/repos/asf/incubator/flume/trunk/flume-ng-core/src/main/java/org/apache/flume/source/SourceType.java

Attached is the _conf_ used to my agent and its log.

Rgs.

                  
> 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
>              Labels: sources, syslog
>             Fix For: v1.2.0
>
>         Attachments: flume.log, web.conf
>
>
> 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

        

[jira] [Assigned] (FLUME-1017) syslog classes missing

Posted by "Hari Shreedharan (Assigned) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FLUME-1017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hari Shreedharan reassigned FLUME-1017:
---------------------------------------

    Assignee: Hari Shreedharan
    
> 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
>            Assignee: Hari Shreedharan
>            Priority: Blocker
>              Labels: sources, syslog
>             Fix For: v1.2.0
>
>         Attachments: flume.log, web.conf
>
>
> 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

        

[jira] [Commented] (FLUME-1017) syslog classes missing

Posted by "jiraposter@reviews.apache.org (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/FLUME-1017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13249254#comment-13249254 ] 

jiraposter@reviews.apache.org commented on FLUME-1017:
------------------------------------------------------


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/4663/#review6772
-----------------------------------------------------------



flume-ng-core/src/main/java/org/apache/flume/source/SourceType.java
<https://reviews.apache.org/r/4663/#comment14930>

    SYSLOGTCP => SYSLOG_TCP
    (to match current convention of underscore-separated words, like with FILE_ROLL)



flume-ng-core/src/main/java/org/apache/flume/source/SourceType.java
<https://reviews.apache.org/r/4663/#comment14931>

    SYSLOGUDP => SYSLOG_UDP
    (to match current convention of underscore-separated words, like with FILE_ROLL)


- Will


On 2012-04-06 01:07:45, Hari Shreedharan wrote:
bq.  
bq.  -----------------------------------------------------------
bq.  This is an automatically generated e-mail. To reply, visit:
bq.  https://reviews.apache.org/r/4663/
bq.  -----------------------------------------------------------
bq.  
bq.  (Updated 2012-04-06 01:07:45)
bq.  
bq.  
bq.  Review request for Flume.
bq.  
bq.  
bq.  Summary
bq.  -------
bq.  
bq.  Adding SyslogTcpSource and SyslogUDPSource to the enum.
bq.  
bq.  
bq.  This addresses bug FLUME-1017.
bq.      https://issues.apache.org/jira/browse/FLUME-1017
bq.  
bq.  
bq.  Diffs
bq.  -----
bq.  
bq.    flume-ng-core/src/main/java/org/apache/flume/source/SourceType.java 9082470 
bq.  
bq.  Diff: https://reviews.apache.org/r/4663/diff
bq.  
bq.  
bq.  Testing
bq.  -------
bq.  
bq.  Builds fine, current unit tests are ok.
bq.  
bq.  
bq.  Thanks,
bq.  
bq.  Hari
bq.  
bq.


                
> 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
>            Assignee: Hari Shreedharan
>            Priority: Blocker
>              Labels: sources, syslog
>             Fix For: v1.2.0
>
>         Attachments: FLUME-1017-1.patch, flume.log, web.conf
>
>
> 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

        

[jira] [Commented] (FLUME-1017) syslog classes missing

Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/FLUME-1017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13247963#comment-13247963 ] 

Hudson commented on FLUME-1017:
-------------------------------

Integrated in flume-trunk #160 (See [https://builds.apache.org/job/flume-trunk/160/])
    FLUME-1017. Syslog Source does not have a short name.

(Hari Shreedharan via Arvind Prabhakar) (Revision 1310149)

     Result = SUCCESS
arvind : http://svn.apache.org/viewvc/?view=rev&rev=1310149
Files : 
* /incubator/flume/trunk/flume-ng-core/src/main/java/org/apache/flume/source/SourceType.java

                
> 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
>            Assignee: Hari Shreedharan
>            Priority: Blocker
>              Labels: sources, syslog
>             Fix For: v1.2.0
>
>         Attachments: FLUME-1017-1.patch, flume.log, web.conf
>
>
> 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

        

[jira] [Commented] (FLUME-1017) syslog classes missing

Posted by "jiraposter@reviews.apache.org (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/FLUME-1017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13247933#comment-13247933 ] 

jiraposter@reviews.apache.org commented on FLUME-1017:
------------------------------------------------------


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/4663/#review6724
-----------------------------------------------------------

Ship it!


+1

Please attach the patch to the Jira.

- Arvind


On 2012-04-06 01:07:45, Hari Shreedharan wrote:
bq.  
bq.  -----------------------------------------------------------
bq.  This is an automatically generated e-mail. To reply, visit:
bq.  https://reviews.apache.org/r/4663/
bq.  -----------------------------------------------------------
bq.  
bq.  (Updated 2012-04-06 01:07:45)
bq.  
bq.  
bq.  Review request for Flume.
bq.  
bq.  
bq.  Summary
bq.  -------
bq.  
bq.  Adding SyslogTcpSource and SyslogUDPSource to the enum.
bq.  
bq.  
bq.  This addresses bug FLUME-1017.
bq.      https://issues.apache.org/jira/browse/FLUME-1017
bq.  
bq.  
bq.  Diffs
bq.  -----
bq.  
bq.    flume-ng-core/src/main/java/org/apache/flume/source/SourceType.java 9082470 
bq.  
bq.  Diff: https://reviews.apache.org/r/4663/diff
bq.  
bq.  
bq.  Testing
bq.  -------
bq.  
bq.  Builds fine, current unit tests are ok.
bq.  
bq.  
bq.  Thanks,
bq.  
bq.  Hari
bq.  
bq.


                
> 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
>            Assignee: Hari Shreedharan
>            Priority: Blocker
>              Labels: sources, syslog
>             Fix For: v1.2.0
>
>         Attachments: flume.log, web.conf
>
>
> 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

        

[jira] [Commented] (FLUME-1017) syslog classes missing

Posted by "Arvind Prabhakar (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/FLUME-1017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13246547#comment-13246547 ] 

Arvind Prabhakar commented on FLUME-1017:
-----------------------------------------

Thanks for the details on this Rafael. We are working towards testing and fixing the Syslog source and will have an update available soon. Among the things that this update will address are the issues with SyslogUtils implementation  along with concurrent connection handling details.
                
> 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
>              Labels: sources, syslog
>             Fix For: v1.2.0
>
>         Attachments: flume.log, web.conf
>
>
> 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

        

[jira] [Commented] (FLUME-1017) syslog classes missing

Posted by "Arvind Prabhakar (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/FLUME-1017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13236018#comment-13236018 ] 

Arvind Prabhakar commented on FLUME-1017:
-----------------------------------------

@Alex - do you still see this happening on the trunk? If so, please provide a sample configuration that will reproduce this.
                
> 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
>              Labels: sources, syslog
>             Fix For: v1.2.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

        

[jira] [Updated] (FLUME-1017) syslog classes missing

Posted by "Hari Shreedharan (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FLUME-1017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hari Shreedharan updated FLUME-1017:
------------------------------------

    Status: Patch Available  (was: Open)
    
> 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
>            Assignee: Hari Shreedharan
>            Priority: Blocker
>              Labels: sources, syslog
>             Fix For: v1.2.0
>
>         Attachments: FLUME-1017-1.patch, flume.log, web.conf
>
>
> 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

        

[jira] [Commented] (FLUME-1017) syslog classes missing

Posted by "Rafael Nunes (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/FLUME-1017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13246524#comment-13246524 ] 

Rafael Nunes commented on FLUME-1017:
-------------------------------------

Hi. Here are some points that I had to deal while trying to use a Syslog Source:

1. When specifying the source's type, use the full class name, as mentioned in the [Getting Started|https://cwiki.apache.org/confluence/display/FLUME/Getting+Started] wiki page of Flume-NG. ie:

{code:title=web.conf|borderStyle=solid}
# Define a memory channel called ch1 on web agent
web.channels.ch1.type = memory

# Define an SyslogTCP source called accesslog on web agent and
# tell it to bind to 0.0.0.0:10514. Connect it to channel ch1.
web.sources.accesslog.type = org.apache.flume.source.SyslogTcpSource
web.sources.accesslog.host = 0.0.0.0
web.sources.accesslog.port = 10514
web.sources.accesslog.channels = ch1

# Define a logger sink that simply logs all events it receives
# and connect it to the other end of the same channel.
web.sinks.log-sink1.type = logger
web.sinks.log-sink1.channel = ch1

# Finally, now that we've defined all of our components, tell
# web which ones we want to activate.
web.sources = accesslog
web.sinks = log-sink1
web.channels = ch1
{code} 

2. When using a RSYSLOG 4.6.3 (as in Fedora 14) to redirect remote messages to Flume's Syslog Source, either TCP or UDP works great;

3. When using a SYSLOG 1.4.1 (as in RedHat 5.2), there are some issues:
a) SYSLOG 1.4.1 supports only UDP;
b) SYSLOG 1.4.1 only tries to connect on remote's host UDP port 514, so your SyslogUPDSource have to have this port configured (or use any sort of port redirection/translation).
c) The SyslogUtils.extractEvent method behaves different when used against RSYSLOG UPD and SYSLOG UDP. In the excerpt of the SyslogUtils class bellow, I try to explain what I saw until here:

{code:title=SyslogUtils.java|borderStyle=solid}
  public static Event extractEvent(ChannelBuffer in) 
        throws IOException {

  //omitted code

    try {
      while (!doneReading) {

        // The line bellow generate a IndexOutOfBoundsException when using 
        // RSYSLOG, forcing the try/catch block execute the statement under
        // the catch and then "return e". But when using against SYSLOG 1.4.1
        // the Exception doesn't happen and the try block executes the 
        // "return null" line.
        b = in.readByte();
        switch (m) {
        case START:
          if (b == '<') {
            m = Mode.PRIO;
          } else {
            m = Mode.ERR;
          }
          break;
        case PRIO:
          if (b == '>') {
            m = Mode.DATA;
          } else {
            char ch = (char) b;
            if (Character.isDigit(ch)) {
              prio.append(ch); // stay in PRIO mode
            } else {
              m = Mode.ERR;
            }
          }
          break;
        case DATA:
          // TCP syslog entries are separated by '\n'
          if (b == '\n') {
            e = buildEvent(prio, baos);
            doneReading = true;
          }
          baos.write(b);
          break;
        case ERR:
          if (b == '<') {
            // check if its start of new event
            m = Mode.PRIO;
          }
          // otherwise stay in Mode.ERR;
          break;
        }
      }
      return null;
    } catch (IndexOutOfBoundsException eF) {
        e = buildEvent(prio, baos);
    }
    return e;
  }
{code} 

Well, after removing the "return null" from the try block, I was able to get my SyslogUDP Sources working with my RSYSLOG and SYSLOG servers.

Any comments?

Thanks for the good work on this project.
                
> 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
>              Labels: sources, syslog
>             Fix For: v1.2.0
>
>         Attachments: flume.log, web.conf
>
>
> 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