FAQ
Hi all,

I don't know where to report this since the JIRA on cloudera seems to be a
private one.

Basically, assign a Flume instance to your host and then try and use a
filechannel with only a filename (no path).

By default, this tries and create the file in the .flume directory off the
user's home directory. For some reason, the cloudera manager sets this to
/var/run/flume-ng. The problem is, the installer doesn't seem to create
this directory.

To solve the problem, just mkdir -p /var/run/flume-ng/.flume and then chown
the whole things to flume:flume.

Restart the flume agent and everything starts working again.

Pat

Search Discussions

  • bc Wong at Nov 17, 2012 at 6:07 pm

    On Sat, Nov 17, 2012 at 9:44 AM, Patrick Ethier wrote:

    Hi all,

    I don't know where to report this since the JIRA on cloudera seems to be a
    private one.

    Basically, assign a Flume instance to your host and then try and use a
    filechannel with only a filename (no path).

    By default, this tries and create the file in the .flume directory off the
    user's home directory. For some reason, the cloudera manager sets this to
    /var/run/flume-ng. The problem is, the installer doesn't seem to create
    this directory.

    To solve the problem, just mkdir -p /var/run/flume-ng/.flume and then
    chown the whole things to flume:flume.

    Restart the flume agent and everything starts working again.
    The `flume' user's home directory is /var/run/flume-ng, which is set by the
    Flume package. So that much is standard. But I agree with your conclusion
    that CM needs to create /var/run/flume-ng, when starting the Flume service.
    Thanks for the bug report and we'll fix it in the next release.

    Cheers,
    bc
  • Vikas Singh at Nov 17, 2012 at 7:29 pm
    Hi Patrick,

    Public JIRA for CM is at: https://issues.cloudera.org/browse/CM. You can
    use that to report any issue.

    - Vikas
    On Sat, Nov 17, 2012 at 10:07 AM, bc Wong wrote:
    On Sat, Nov 17, 2012 at 9:44 AM, Patrick Ethier wrote:

    Hi all,

    I don't know where to report this since the JIRA on cloudera seems to be
    a private one.

    Basically, assign a Flume instance to your host and then try and use a
    filechannel with only a filename (no path).

    By default, this tries and create the file in the .flume directory off
    the user's home directory. For some reason, the cloudera manager sets this
    to /var/run/flume-ng. The problem is, the installer doesn't seem to create
    this directory.

    To solve the problem, just mkdir -p /var/run/flume-ng/.flume and then
    chown the whole things to flume:flume.

    Restart the flume agent and everything starts working again.
    The `flume' user's home directory is /var/run/flume-ng, which is set by
    the Flume package. So that much is standard. But I agree with your
    conclusion that CM needs to create /var/run/flume-ng, when starting the
    Flume service. Thanks for the bug report and we'll fix it in the next
    release.

    Cheers,
    bc

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupscm-users @
categorieshadoop
postedNov 17, '12 at 5:44p
activeNov 17, '12 at 7:29p
posts3
users3
websitecloudera.com
irc#hadoop

People

Translate

site design / logo © 2022 Grokbase