Mailing-List: contact chukwa-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: chukwa-user@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of eric818@gmail.com designates
 209.85.216.175 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CANZWjw6s=Ytt9KyWhc_r55rktx+hWQaGofNHykxDgdS8QS5cww@mail.gmail.com>
References: 
 <CANZWjw6ym3M5wEV17vnbtdoQr0WdyfbB2Se6eXPiNyvcdZGG1A@mail.gmail.com>
	<CADfbTpFk4mCjes3ewWCcJfwNKsUsvVC=_np5TBS4SWBT+imMEw@mail.gmail.com>
	<CANZWjw4a5MZxkfHWF3rN7XU3bfVxCsDQUjWh5dSkNiUdDS-CGQ@mail.gmail.com>
	<CADfbTpHUxRKvO=79B5tgnyb1WSDxvnvODHui3OAJMuffREeqNg@mail.gmail.com>
	<CANZWjw6s=Ytt9KyWhc_r55rktx+hWQaGofNHykxDgdS8QS5cww@mail.gmail.com>
Date: Sat, 10 Dec 2011 20:14:38 -0800
Message-ID: 
 <CADfbTpG0dNCAccMx9HfxxSuxiuxiPgAU3GPFyb-+PuqBeQ__RQ@mail.gmail.com>
Subject: Re: debug Error saving Chunk
From: Eric Yang <eric818@gmail.com>
To: chukwa-user@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

You can change the log.info line to:

log.error(ExceptionUtil.getStackTrace(e));

This should show the stack trace.
e.printStackTrace() should have been recorded in syslog section of the
mapreduce job.  Note, syslog in this case is not referring to OS
syslog subsystem but the log file that you can see when you click on
task attempts.

regards,
Eric

On Sat, Dec 10, 2011 at 7:38 PM, AD <straightflush@gmail.com> wrote:
> It looks like its happening in my collect method in my OutputCollector bu=
t
> not seeing any stack trace. =A0I put some debug logging in AbstractProces=
sor
> and its failing here
>
> =A0while (hasNext()) {
> =A0 =A0 =A0 try {
> =A0 =A0 =A0 =A0 parse(nextLine(), output, reporter);
> =A0 =A0 =A0 } catch (Throwable e) {
> =A0 =A0 =A0 =A0 log.info("Error parsing....");
> =A0 =A0 =A0 =A0 e.printStackTrace();
> =A0 =A0 =A0 =A0 saveChunkInError(e);
> =A0 =A0 =A0 }
>
> I see "Error parsing" and i can trace everything working in parse() up to
> the line output.collect() so i imagine is failing there but not seeing an=
y
> stacktrace....
>
> Is there a way to get all stderr/stdout to one logfile?
>
>
>
> On Sat, Dec 10, 2011 at 10:21 PM, Eric Yang <eric818@gmail.com> wrote:
>>
>> In Mapreduce framework, everything that uses System.out or System.err
>> are redirected automatically to syslog.
>> You shouldn't need to do anything special.
>>
>> regards,
>> Eric
>>
>> On Sat, Dec 10, 2011 at 7:07 PM, AD <straightflush@gmail.com> wrote:
>> > I have a custom processor in extraction/demux/processor/mapper do I ne=
ed
>> > to
>> > print something custom to stderr from there ?
>> >
>> >
>> > On Sat, Dec 10, 2011 at 4:32 PM, Eric Yang <eric818@gmail.com> wrote:
>> >>
>> >> Hi AD,
>> >>
>> >> The stack trace is output to stdout of the mapreduce job. =A0Hence,
>> >> check the syslog file for the mapreduce job to find the actual cause
>> >> of the problem. =A0Hope this helps.
>> >>
>> >> regards,
>> >> Eric
>> >>
>> >> On Sat, Dec 10, 2011 at 1:23 PM, AD <straightflush@gmail.com> wrote:
>> >> > i am seeing the following error :
>> >> >
>> >> > 2011-12-10 16:21:43,886 WARN btpool0-1 ChunkSaver - Unable to save =
a
>> >> > chunk:
>> >> > tags: =A0testcluster - source:lilmac.home
>> >> >
>> >> > Is there a way to turn on more debugging to find out why?
>> >
>> >
>
>