Fatal error

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
reddy12
Participant
Posts: 99
Joined: Tue Aug 08, 2006 9:34 pm

Fatal error

Post by reddy12 »

Hi

I am getting the following fatal error.If any one know about htis please let me know

1)
node_node1: Fatal Error: Unable to start ORCHESTRATE process on node node1 (blubluds007): APT_PMPlayer::APT_PMPlayer: fork() failed, Resource temporarily unavailable
2) main_program: The Section Leader on node node1 has terminated unexpectedly.
3)main_program: Fatal Error: 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 node1

Thanks.
ds_is_fun
Premium Member
Premium Member
Posts: 194
Joined: Fri Jan 07, 2005 12:00 pm

Re: Fatal error

Post by ds_is_fun »

The problem seems to be pertaining to only one node/multiple CPUs.
I suggest to re-start the engine and try re-running the job. This should re-set all your config files.
Let us know!
reddy12 wrote:Hi

I am getting the following fatal error.If any one know about htis please let me know

1)
node_node1: Fatal Error: Unable to start ORCHESTRATE process on node node1 (blubluds007): APT_PMPlayer::APT_PMPlayer: fork() failed, Resource temporarily unavailable
2) main_program: The Section Leader on node node1 has terminated unexpectedly.
3)main_program: Fatal Error: 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 node1

Thanks.
Those who throw objects at crocodiles should be asked to retreive 'em.
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

ds_is_fun - Now you have intrigued me, how does restarting DataStage reset which 'config files'?

It just happens that the failure occurs on some node, then causes all the other processes to stop. If a fork() call cannot complete it is usually caused by some form of system overload - be it memory or disk or CPU.
Post Reply