Return-Path: 
 <user-return-3431-apmail-flume-user-archive=flume.apache.org@flume.apache.org>
X-Original-To: apmail-flume-user-archive@www.apache.org
Delivered-To: apmail-flume-user-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 5C3C6E778
	for <apmail-flume-user-archive@www.apache.org>;
 Fri, 18 Jan 2013 19:14:25 +0000 (UTC)
Received: (qmail 14825 invoked by uid 500); 18 Jan 2013 19:14:25 -0000
Delivered-To: apmail-flume-user-archive@flume.apache.org
Received: (qmail 14739 invoked by uid 500); 18 Jan 2013 19:14:25 -0000
Mailing-List: contact user-help@flume.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@flume.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@flume.apache.org>
List-Post: <mailto:user@flume.apache.org>
List-Id: <user.flume.apache.org>
Reply-To: user@flume.apache.org
Delivered-To: mailing list user@flume.apache.org
Received: (qmail 14731 invoked by uid 99); 18 Jan 2013 19:14:25 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Jan 2013 19:14:25 +0000
X-ASF-Spam-Status: No, hits=1.5 required=5.0
	tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of cwoodson.dev@gmail.com
 designates 74.125.82.44 as permitted sender)
Received: from [74.125.82.44] (HELO mail-wg0-f44.google.com) (74.125.82.44)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Jan 2013 19:14:17 +0000
Received: by mail-wg0-f44.google.com with SMTP id dr12so2341265wgb.23
        for <user@flume.apache.org>; Fri, 18 Jan 2013 11:13:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:x-received:date:message-id:subject:from:to
         :content-type;
        bh=Mr1v+jRlyva6HPuxOXR3evxExGKcNM7VXqwc43+rDe8=;
        b=c8Z57cPMg7izQ2ASaEr4s7Z93uoF9ERH2sxN732b76SCqhq4EudoIel+iFnVACfJCA
         UuMHKhyVqv0y5S1YQz0FAp8wjZDZ17YIKOouTL4Nxng8ebIGKQWqrsY6HAxUoYDymM0I
         8HrIuXS76Ck9uP8YY+16Y+atfsIuPYD0EsMP6vwwux1X2DgEicU9pg84zg8feiirNszv
         x3PnNWlUdWXHDhFxkK7q870BZDx13Qn1ZSnx6CLPlOqXVcrFQaqbXSsipzAqsz7BRQ/9
         uNG1dVaB7ZpCBdvp4TBjQG/5eJdETBLwoWDnAav/PxO4Ui2KNk5kaee8+Yr7fREiS/xG
         gqyA==
MIME-Version: 1.0
X-Received: by 10.194.84.68 with SMTP id w4mr4342843wjy.51.1358536437318; Fri,
 18 Jan 2013 11:13:57 -0800 (PST)
Received: by 10.227.2.196 with HTTP; Fri, 18 Jan 2013 11:13:57 -0800 (PST)
Date: Fri, 18 Jan 2013 11:13:57 -0800
Message-ID: 
 <CAH0o75OCNZu66hYcE1OP+m8T3SwXpegTKuemFunNEUpD+xPuww@mail.gmail.com>
Subject: Log4J Appender in Flume
From: Connor Woodson <cwoodson.dev@gmail.com>
To: "user@flume.apache.org" <user@flume.apache.org>
Content-Type: multipart/alternative; boundary=047d7bb04754c2c4f904d394e9e7
X-Virus-Checked: Checked by ClamAV on apache.org

--047d7bb04754c2c4f904d394e9e7
Content-Type: text/plain; charset=ISO-8859-1

I just ran into an unfortunate configuration issue; I want to use flume's
log4j appender as part of the agent itself in order to send error logs to a
monitoring system. However, when that system is down (which it should be
able to be without causing issues), the RPCClient (even though it's in a
Failover Sink) throws an error/warning that it can't connect to the system,
and then that error gets routed recursively back into the appender and so
forth...

Is there any way to make this system work (using the log4j appender on
error messages), or if not any recommendations on how to track my error
logs?

Thanks,

- Connor

--047d7bb04754c2c4f904d394e9e7
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I just ran into an unfortunate configuration issue; I want=
 to use flume&#39;s log4j appender as part of the agent itself in order to =
send error logs to a monitoring system. However, when that system is down (=
which it should be able to be without causing issues), the RPCClient (even =
though it&#39;s in a Failover Sink) throws an error/warning that it can&#39=
;t connect to the system, and then that error gets routed recursively back =
into the appender and so forth...<div>
<br></div><div style>Is there any way to make this system work (using the l=
og4j appender on error messages), or if not any recommendations on how to t=
rack my error logs?</div><div style><br></div><div style>Thanks,</div><div =
style>
<br></div><div style>- Connor</div></div>

--047d7bb04754c2c4f904d394e9e7--