Can you point me how to fix this thing? Or if there is a workaround? Getting this to work would be really helpful.
On Thu, Jan 19, 2012 at 8:59 PM, Eric Yang <[email protected]> wrote: > Chukwa's own TaskLogAppender code seems to be using default > initialization parameters for contacting Chukwa Agent. The code may > need some update for it to work right. The subAppend function between > ChukwaDailyRollingFileAppender and TaskLogAppender should look very > similar. Unfortunately, it isn't at the current state. I think a > patch is required to get Chukwa's TaskLogAppender to work. > > regards, > Eric > > On Jan 19, 2012, at 6:49 PM, Abhijit Dhar <[email protected]> > wrote: > > > I tried different loglevels too. But, I checked, and found that > > TaskLogAppender does not even register itself with the chuka agent as an > > adapter. I tried using ChukwaDailyRollingFileAppender with the below > config, > > and it works flawlessly - > > > > > log4j.appender.TLA=org.apache.hadoop.chukwa.inputtools.log4j.ChukwaDailyRollingFileAppender > > log4j.appender.TLA.File=logs/jcrawler.log > > log4j.appender.TLA.recordType=CrawlerLog > > log4j.appender.TLA.chukwaClientHostname=localhost > > log4j.appender.TLA.chukwaClientPortNum=9093 > > log4j.appender.TLA.DatePattern=.yyyy-MM-dd > > log4j.appender.TLA.layout=org.apache.log4j.PatternLayout > > log4j.appender.TLA.layout.ConversionPattern=%d{ISO8601} %p [%t] > > [%c{5}.%M()]:: %m%n > > > > But, with ChukwaDailyRollingFileAppender, it does not create the task log > > attempt directories(which I need too) > > > > -- > > View this message in context: > http://apache-chukwa.679492.n3.nabble.com/hadoop-s-attempt-directory-logs-tp3665088p3674393.html > > Sent from the Chukwa - Users mailing list archive at Nabble.com. > -- Абижит Дар
