DSXchange

main_program: Unable to start ORCHESTRATE job: APT_PMwaitForPlayersToStart failed while waiting for players to confirm startup. This likely indicates a network problem.
Status from APT_PMpoll is 0; node name is etl01

kumar11 wrote:This likely indicates a network problem.

Did you investigate this?

have gone through the dsxchange search and found it as a network issue and reran the job and got the below error:
node_etl03: Fatal Error: Unable to start ORCHESTRATE process on node etl03 (mdcdetlndw01a): APT_PMPlayer::APT_PMPlayer: fork() failed, Not enough space

look at your TMPDIR path and your scratch disk paths too.

make sure you have enough room.

the TMPDIR path is set to /dsScrath
and there is enough space in the directory.

but, at the time of execution...

Does the job fail 100% of the time?

When you run the job. start looking at the space consumption on that mount.

df -g /dsScrath

look at your % creep up. I bet it will max out at some point.

Your APT file might be set up with multiple spill over scratch mounts but TMPDIR does not relocate the same when when full. He will fail with fork errors and broken pipes, and Not Enough space.

Thanks Paul!!. was able to resolve the issue.

For future searchers, you resolved this by doing what exactly?

from the Admin console set the environment variable /TMPDIR to the /dsScratch path and the job ran fine after the settings.