[
https://issues.apache.org/jira/browse/FLUME-1246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13287155#comment-13287155
]
Hari Shreedharan commented on FLUME-1246:
-----------------------------------------
In the latest log you posted, the agent seems to have been killed before all
components were even created, so start was never called:
2012-06-01 11:30:17,098 INFO conf.FlumeConfiguration: Post-validation flume
configuration contains configuration for agents: [test]
2012-06-01 11:30:17,098 INFO properties.PropertiesFileConfigurationProvider:
Creating channels
2012-06-01 11:30:17,098 DEBUG channel.DefaultChannelFactory: Creating instance
of channel ch1 type file
2012-06-01 11:30:21,332 INFO node.FlumeNode: Flume node stopping - test
2012-06-01 11:30:21,332 INFO lifecycle.LifecycleSupervisor: Stopping lifecycle
supervisor 9
2012-06-01 11:30:21,333 INFO nodemanager.DefaultLogicalNodeManager: Node
manager stopping
2012-06-01 11:30:21,333 INFO lifecycle.LifecycleSupervisor: Stopping lifecycle
supervisor 9
2012-06-01 11:30:21,334 DEBUG nodemanager.DefaultLogicalNodeManager: Node
manager stopped
11:30:17 - channel factory log message
11:30:21 - shutdown.
I don't think all the components were created here, so the starts were never
called.
> FileChannel failing to start, also shutdown impossible without kill
> --------------------------------------------------------------------
>
> Key: FLUME-1246
> URL: https://issues.apache.org/jira/browse/FLUME-1246
> Project: Flume
> Issue Type: Bug
> Components: Channel
> Affects Versions: v1.2.0
> Environment: CentOS 5.4
> Reporter: Juhani Connolly
> Attachments: flume-hari-2012May312217PST.log, flume.log, flume.log,
> flume.log, flume.log.20120601, test_conf.conf
>
>
> Reduced to a minimal configuration for simplicity. I can recreate this on
> some machines, and not others. I wouldn't be surprised if it is some machines
> specific issue(test machines on CentOS5.4. On some it worked, others not),
> however whatever exception was thrown when attempting to get created is
> consumed and never passed onwards
> Config:
> test.channels.ch1.type = file
> test.channels.ch1.checkpointDir =
> /home/share/juhani_connolly/flume-1.2.0-incubating-SNAPSHOT/check
> test.channels.ch1.dataDirs =
> /home/share/juhani_connolly/flume-1.2.0-incubating-SNAPSHOT/filechdata
> test.sources.top.type = exec
> test.sources.top.command = /usr/bin top -b -d 1
> test.sources.top.restart = true
> test.sources.top.restartThrottle = 1000
> test.sources.top.interceptors = ts
> test.sources.top.interceptors.ts.type =
> org.apache.flume.interceptor.TimestampInterceptor$Builder
> test.sources.top.channels = ch1
> test.sinks.log.type = logger
> test.sinks.log.channel = ch1
> test.channels = ch1
> test.sources = top
> test.sinks = log
> attaching logs with general/lifecycle loglevel down to debug.
> A solution to this is probably going to be just improving error reporting.
> Another possibly more important element is that flume enters a state from
> which it cannot shutdown without kill -9. It looks like the Interrupts are
> getting swallowed up silently somewhere
--
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
