[
https://issues.apache.org/jira/browse/FLUME-537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashish Paliwal resolved FLUME-537.
----------------------------------
Resolution: Won't Fix
Fix Version/s: v0.9.5
Won't fix. 0.X branch not maintained anymore
> Error message for "exec load" could be more clear
> -------------------------------------------------
>
> Key: FLUME-537
> URL: https://issues.apache.org/jira/browse/FLUME-537
> Project: Flume
> Issue Type: Improvement
> Components: Master
> Affects Versions: v0.9.3
> Environment: Ubuntu 10.04 LTS on EC2
> Reporter: Disabled imported user
> Priority: Trivial
> Fix For: v0.9.5
>
>
> We upgraded from 0.9.1 to 0.9.3 and our "exec load" failed:
> {noformat}
> ubuntu@domU-12-31-39-04-54-CE:~$ flume shell -c localhost -e "exec load"
> 2011-02-23 23:25:17,006 [main] INFO conf.FlumeConfiguration: Loading
> configurations from /etc/flume/conf
> Using default admin port: 35873
> Using default report port: 45678
> Connecting to Flume master localhost:35873:45678...
> 2011-02-23 23:25:17,168 [main] INFO util.AdminRPCThrift: Connected to master
> at localhost:35873
> [id: 16] Execing command : load
> Command failed
> null
> {noformat}
> It looks like LoadConfigCommand changed to require a file versus assuming
> current.flume as the default.
> This line looks to be the culprit - perhaps missing an error message if the
> assertion fails?
> {noformat}
> Preconditions.checkArgument(argv.length == 0);
> {noformat}
> Sharethrough loves Flume! :)
> Rob
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
