Player terminated unexpectedly

Gopalraja · Post by **Gopalraja** » Thu May 14, 2009 5:59 am

Hi,

My job got aborted due to player terminated the job.

The exact word from the director log is below...

"node_node2: Player 3 terminated unexpectedly."

May I know the reason for this ...

I'm expecting favorable solution from your side...

Thanks in Advance...
Aswice

*Title made more descriptive - Content Editor*

nagarjuna · Post by **nagarjuna** » Thu May 14, 2009 6:37 am

Any other fatal message or warning message ??

ray.wurlod · Post by **ray.wurlod** » Thu May 14, 2009 4:47 pm

It was unexpected.

How can you therefore expect to know? Some intermittent glitch in communication between processes, maybe.

ray.wurlod · Post by **ray.wurlod** » Thu May 14, 2009 4:49 pm

I'm talking on the telephone. Suddenly there is silence on the device.

May I know the reason for this ...

I'm expecting favorable solution from your side...

IBM Analytics Champion 2009 - 2020 · Post by **asorrell** » Thu May 14, 2009 8:58 pm

There are numerous (but rare) reasons for this to occur, including (but not limited to):
- System issues
- Encountering a file or process limit on the system (ulimit, etc.)
- Poor code generating an unhandled situation causing aborted process
- Corrupted job

Truthfully, the few times I've encountered this, the only way to find out for sure is to get a core dump and have IBM run a trace on the dump to see where it was in the job when it failed. Usually that will give you a clue as to what it was trying to do when it failed.

Sometimes you can also get lucky and you'll get a usable error message in the project's &PH& sub-directory for the job that holds the output of the "phantom" (background) tasks as they run.