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*
Player terminated unexpectedly
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
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.
- 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.