Home | About | Sematext search-lucene.com search-hadoop.com
 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?
Vinod Kumar Vavilapalli 2013-01-29, 02:13

Try passing -Dlog4j.debug via mapred.child.java.opts. That will clearly show you the problem as part of logs itself.

Are these errors appearing in stdout/stderr or syslog?

+Vinod Kumar Vavilapalli
Hortonworks Inc.
http://hortonworks.com/

On Jan 28, 2013, at 2:36 AM, Calvin 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.