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.
Fatal error
Moderators: chulett, rschirm, roy
Re: Fatal error
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!
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.
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.
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.
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>