Return-Path: 
 <user-return-4650-apmail-hadoop-mapreduce-user-archive=hadoop.apache.org@hadoop.apache.org>
X-Original-To: apmail-hadoop-mapreduce-user-archive@minotaur.apache.org
Delivered-To: apmail-hadoop-mapreduce-user-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 6D72FE48A
	for <apmail-hadoop-mapreduce-user-archive@minotaur.apache.org>;
 Mon, 28 Jan 2013 10:37:15 +0000 (UTC)
Received: (qmail 68144 invoked by uid 500); 28 Jan 2013 10:37:10 -0000
Delivered-To: apmail-hadoop-mapreduce-user-archive@hadoop.apache.org
Received: (qmail 68046 invoked by uid 500); 28 Jan 2013 10:37:10 -0000
Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@hadoop.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@hadoop.apache.org>
List-Post: <mailto:user@hadoop.apache.org>
List-Id: <user.hadoop.apache.org>
Reply-To: user@hadoop.apache.org
Delivered-To: mailing list user@hadoop.apache.org
Received: (qmail 68038 invoked by uid 99); 28 Jan 2013 10:37:10 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 Jan 2013 10:37:10 +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 (athena.apache.org: domain of iphcalvin@gmail.com
 designates 209.85.220.182 as permitted sender)
Received: from [209.85.220.182] (HELO mail-vc0-f182.google.com)
 (209.85.220.182)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 Jan 2013 10:37:03 +0000
Received: by mail-vc0-f182.google.com with SMTP id fl17so1755847vcb.13
        for <user@hadoop.apache.org>; Mon, 28 Jan 2013 02:36:43 -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=LO3oasmwJncDeQP6HlVD7GkEhu+A2bFMfbJihnFkvnI=;
        b=HQYv2v33Z3UdMuc+oJOD6UB5b7gxZYRyk8RAOMoyomou9ImXJs//INDoVYfwp9lkCW
         duJKuVwBpzifoyV5wL1Za4MnD+5G9sudIfZ/jbboCP1N7aPXAf1MKxjzggYU/gbyupWq
         1nRPkGxKzOG3PQXtkSZPxeq7DByHbgKF01bRlaio/dXiZT2u21lJzz/7EBV+3Kl1Qh73
         KtSIfEW2ZLCStUS5Ha6TUBSmkGFhHlvR/b1Iq5RpRF6leIAazJUH71K45UO6lfxvDK5j
         /cevrrqf7UT7/X7V+HP0AFNvWBCUzpuW2SBhflx5rrFkLC/q8s5hUn0cQtX2RW1obNas
         ReLQ==
MIME-Version: 1.0
X-Received: by 10.52.72.129 with SMTP id d1mr12680886vdv.109.1359369403137;
 Mon, 28 Jan 2013 02:36:43 -0800 (PST)
Received: by 10.220.123.131 with HTTP; Mon, 28 Jan 2013 02:36:43 -0800 (PST)
Date: Mon, 28 Jan 2013 02:36:43 -0800
Message-ID: 
 <CADSD3vi8yT3MQ763fSUG7cgAJrS72KkeNhkSjx9cN3wbNsc7fQ@mail.gmail.com>
Subject: warnings from log4j -- where to look to resolve?
From: Calvin <iphcalvin@gmail.com>
To: user@hadoop.apache.org
Content-Type: multipart/alternative; boundary=20cf3071c70a647f6104d456dadf
X-Virus-Checked: Checked by ClamAV on apache.org

--20cf3071c70a647f6104d456dadf
Content-Type: text/plain; charset=UTF-8

Hi,

Each time I run a job, I get thousands of these warnings. I've looked at
conf/log4j.properties and nothing out of the ordinary (a diff with the
default log4j.properties shows no lines of consequence changed).

Has anyone else come across this problem? Where else would I look to find
potentially conflicting settings for log4j?

Thanks.

---

attempt_201301161411_0244_m_000054_0: log4j:WARN Not allowed to write to a
closed appender.
attempt_201301161411_0244_m_000054_0: log4j:WARN Not allowed to write to a
closed appender.
attempt_201301161411_0244_m_000054_0: log4j:WARN Not allowed to write to a
closed appender.

--20cf3071c70a647f6104d456dadf
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div style>Hi,</div><div style><br></div><div style>Each t=
ime I run a job, I get thousands of these warnings. I&#39;ve looked at conf=
/log4j.properties and nothing out of the ordinary (a diff with the default =
log4j.properties shows no lines of consequence changed).</div>
<div style><br></div><div style>Has anyone else come across this problem? W=
here else would I look to find potentially conflicting settings for log4j?<=
/div><div style><br></div><div style>Thanks.</div><div style><br></div>
<div style>---</div><div><br></div><div>attempt_201301161411_0244_m_000054_=
0: log4j:WARN Not allowed to write to a closed appender.</div><div>attempt_=
201301161411_0244_m_000054_0: log4j:WARN Not allowed to write to a closed a=
ppender.</div>
<div>attempt_201301161411_0244_m_000054_0: log4j:WARN Not allowed to write =
to a closed appender.</div></div>

--20cf3071c70a647f6104d456dadf--