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
Job run issue
Moderators: chulett, rschirm, roy
Re: Job run issue
Did you investigate this?kumar11 wrote:This likely indicates a network problem.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
Re: Job run issue
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
node_etl03: Fatal Error: Unable to start ORCHESTRATE process on node etl03 (mdcdetlndw01a): APT_PMPlayer::APT_PMPlayer: fork() failed, Not enough space
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.
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.