Unable to start ORCHESTRATE network connection on node .
anyone faced same kind of issue?
Unable to start ORCHESTRATE network connection on node
Moderators: chulett, rschirm, roy
You need to start your own posts rather than continue to jump on the end of unrelated topics. What version and O/S is this? I'm going to guess but you need to supply that information.
Post the complete, unedited error message. Do an exact search of the forums here for it, the answer to your question is "yes".
Post the complete, unedited error message. Do an exact search of the forums here for it, the answer to your question is "yes".
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
Unable to start ORCHESTRATE network connection on node
Craig,
Sorry for that. I'm getting below error.
OS is linux and DataStage 9.1
Lkp_Ref_Pointer_id_01,1: Configured timeout of 600 seconds reached for accepting player connections for pid 10,354,852. Pending fifo count: 0. Pending shared memory count: 0. This is most likely due to the failure of an upstream operator.
Lkp_Ref_Pointer_id_01,1: Fatal Error: Unable to start ORCHESTRATE network connection on node
APT_PMConnectionSetup::acceptConnection: unable to accept connection
node_: Player 11 terminated unexpectedly.
main_program: APT_PMsectionLeader player 11 - Unexpected exit status 1.
Sorry for that. I'm getting below error.
OS is linux and DataStage 9.1
Lkp_Ref_Pointer_id_01,1: Configured timeout of 600 seconds reached for accepting player connections for pid 10,354,852. Pending fifo count: 0. Pending shared memory count: 0. This is most likely due to the failure of an upstream operator.
Lkp_Ref_Pointer_id_01,1: Fatal Error: Unable to start ORCHESTRATE network connection on node
APT_PMConnectionSetup::acceptConnection: unable to accept connection
node_: Player 11 terminated unexpectedly.
main_program: APT_PMsectionLeader player 11 - Unexpected exit status 1.
pavuluri
Re: Unable to start ORCHESTRATE network connection on node
The issue here is your job forking out many processes which delays the start of the the process and it gets termineted after waiting like 600 seconds.
you got options as below.
- brakdown the job and run them sequentially to fork out less processes.
- run the jobs on single node and ramp down the concurrent jobs when the high yields jobs are executing.
-- change time out parm on the admin to higher value.
you got options as below.
- brakdown the job and run them sequentially to fork out less processes.
- run the jobs on single node and ramp down the concurrent jobs when the high yields jobs are executing.
-- change time out parm on the admin to higher value.