The attempt_XXXX_XXXX_N is in the format containing taskid, tip, jobid, that possibly can narrow down your search to get error under syslogs, and I think the logging has jobid, so a grep might help.
Cheers, /R On 2/23/10 5:22 PM, "prasenjit mukherjee" <[email protected]> wrote: Generally the stderr goes to the file <hadoop>/logs/userlog/attempt_XXXX_XXXX_N/stderr in the hadoop node running that script. But it is not practical as it requires user to go and search all the stderr files, most of them probably will be pseudo-empty ( just the headers footers, but no actual stderr output ). Any available packages/techniques to help users to fetch stderr coming out of custom DEFINE scripts in pig ? -Thanks, Prasen
