Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Threaded View
MapReduce >> mail # user >> warnings from log4j -- where to look to resolve?


Copy link to this message
-
Re: warnings from log4j -- where to look to resolve?
Hi,

Does your code instantiate and work with a self logger object? If so,
is it a log4j instance or a commons logging one?

On Mon, Jan 28, 2013 at 4:06 PM, Calvin <[EMAIL PROTECTED]> wrote:
> 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.

--
Harsh J
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB