ORCHESTRATE ERROR
Moderators: chulett, rschirm, roy
ORCHESTRATE ERROR
Hi Everyone,
I moved all my jobs from DEV to QA and i moved the DSParams from DV to QA and made proper settings for the Parameters on the QA Admin too.
i get this fatal Error when i run this job from the director.
node_node1: Fatal Error: Unable to start ORCHESTRATE process on node node1 (hctunx33): APT_PMPlayer::APT_PMPlayer: fork() failed, Resource temporarily unavailable
main_program: The Section Leader on node node1 has terminated unexpectedly.
node_node8: Fatal Error: Unable to start ORCHESTRATE process on node node8 (hctunx33): APT_PMPlayer::APT_PMPlayer: fork() failed, Resource temporarily unavailable
main_program: The Section Leader on node node8 has terminated unexpectedly.
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
I have 8 nodes on my QA box and i specified the MAximum as 8 nodes and the minimum as 2 nodes. but still i dont understand why i am fetting the ORCHESTRATE error. the last fatal log says that there is a network problem. can anyone hint me on this error so that i can contact my admin.
thanks
sudharma
I moved all my jobs from DEV to QA and i moved the DSParams from DV to QA and made proper settings for the Parameters on the QA Admin too.
i get this fatal Error when i run this job from the director.
node_node1: Fatal Error: Unable to start ORCHESTRATE process on node node1 (hctunx33): APT_PMPlayer::APT_PMPlayer: fork() failed, Resource temporarily unavailable
main_program: The Section Leader on node node1 has terminated unexpectedly.
node_node8: Fatal Error: Unable to start ORCHESTRATE process on node node8 (hctunx33): APT_PMPlayer::APT_PMPlayer: fork() failed, Resource temporarily unavailable
main_program: The Section Leader on node node8 has terminated unexpectedly.
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
I have 8 nodes on my QA box and i specified the MAximum as 8 nodes and the minimum as 2 nodes. but still i dont understand why i am fetting the ORCHESTRATE error. the last fatal log says that there is a network problem. can anyone hint me on this error so that i can contact my admin.
thanks
sudharma
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
It's a UNIX kernel parameter. It's not called MAXUPROC on all variants of UNIX - you need to determine what the kernel parameter that sets your "maximum number of processes per user" is. Then you need to learn how superuser goes about changing it in that UNIX (which may require a re-boot of the UNIX machine).
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
[quote="sudharma"]Hi Guru,
i got this fixed . the MAXUPROC (Maximun Process per user ) was 128 in the QA Environment. Dev and Prod had 500. so we had to set this to 500 on QA and the issue is resolved now.
Hi all,
can anybody share that Kernel command with us for resetting MAXUPROC (Maximun Process per user ).
I am working on solaris :
-----------------------
Machine hardware: sun4us
OS version: 5.8
i got this fixed . the MAXUPROC (Maximun Process per user ) was 128 in the QA Environment. Dev and Prod had 500. so we had to set this to 500 on QA and the issue is resolved now.
Hi all,
can anybody share that Kernel command with us for resetting MAXUPROC (Maximun Process per user ).
I am working on solaris :
-----------------------
Machine hardware: sun4us
OS version: 5.8
Aquilis