The first work-around is to uncomment the code in isLog4JConfigured (ApplicationSetup), but a better solution would be to rely on a Terrier specific logger repository, i.e. followinghttp://articles.qos.ch/sc.html

Craig Macdonald
added a comment - 05/Jun/12 1:45 PM Thanks Benjami.
isLog4JConfigured() never worked as intended. Its interesting that it does something for you.
So that I can try to reproduce your issue, which Hadoop version/distribution are you using?
Craig

I looked into this. The key point is log4j will (wrongly) configure itself from the Hadoop jar files. The solution is to ensure that bin/anyclass.sh informs log4j if a terrier-log.xml file exists in the TERRIER_ETC directory. The isLog4jConfigured() in ApplicationSetup works as expected. Patch attached.

Craig Macdonald
added a comment - 18/Jul/13 7:13 PM I looked into this. The key point is log4j will (wrongly) configure itself from the Hadoop jar files. The solution is to ensure that bin/anyclass.sh informs log4j if a terrier-log.xml file exists in the TERRIER_ETC directory. The isLog4jConfigured() in ApplicationSetup works as expected. Patch attached.