[
https://issues.apache.org/jira/browse/FLUME-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15964079#comment-15964079
]
Umesh Chaudhary commented on FLUME-1302:
----------------------------------------
[~mubarakseyed] after providing the dir path (for checkpoint and data) the only
reason to print the above message "CheckpointDir could not be created" is
permission issue. For me the message tells it all, otherwise we need to print
different message for both the preconditions mentioned in the code. Let me know
your thoughts.
> FileChannel Log error message when there is no write permission
> ---------------------------------------------------------------
>
> Key: FLUME-1302
> URL: https://issues.apache.org/jira/browse/FLUME-1302
> Project: Flume
> Issue Type: Improvement
> Components: Sinks+Sources
> Reporter: Mubarak Seyed
> Priority: Minor
>
> FileChannel Log instance tries to create files (checkpoint and data) and
> fails when specified directory for flume user (or user one that used to start
> flume agent) doesn't have write permission. It would be fine if we improve
> the error message at
> {code}
> Preconditions.checkArgument(
> checkpointDir.isDirectory() || checkpointDir.mkdirs(), "CheckpointDir
> "
> + checkpointDir + " could not be created");
> {code}
> {code}
> 2012-06-21 09:01:34,530 INFO file.FileChannel: Starting FileChannel with
> dataDir [/data7/flume/file-channel/data6]
> 2012-06-21 09:01:34,530 ERROR lifecycle.LifecycleSupervisor: Unable to start
> org.apache.flume.channel.file.FileChannel@6ca084f8 - Exception follows.
> java.lang.IllegalArgumentException: CheckpointDir
> /data7/flume/file-channel/checkpoint6 could not be created
> at
> com.google.common.base.Preconditions.checkArgument(Preconditions.java:88)
> at org.apache.flume.channel.file.Log.<init>(Log.java:84)
> at org.apache.flume.channel.file.FileChannel.start(FileChannel.java:178)
> at
> org.apache.flume.lifecycle.LifecycleSupervisor$MonitorRunnable.run(LifecycleSupervisor.java:228)
> 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)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
