Unable to start ORCHESTRATE network connection on node

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
pavuluri
Participant
Posts: 4
Joined: Sat Dec 15, 2007 4:24 am

Unable to start ORCHESTRATE network connection on node

Post by pavuluri »

Unable to start ORCHESTRATE network connection on node .

anyone faced same kind of issue?
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

:!: 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".
-craig

"You can never have too many knives" -- Logan Nine Fingers
pavuluri
Participant
Posts: 4
Joined: Sat Dec 15, 2007 4:24 am

Unable to start ORCHESTRATE network connection on node

Post by pavuluri »

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.
pavuluri
PaulVL
Premium Member
Premium Member
Posts: 1315
Joined: Fri Dec 17, 2010 4:36 pm

Post by PaulVL »

Is this a first time running a job with that user id on that system?
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Or with this config file, perhaps?
-craig

"You can never have too many knives" -- Logan Nine Fingers
attu
Participant
Posts: 225
Joined: Sat Oct 23, 2004 8:45 pm
Location: Texas

Post by attu »

Can you run the job with a single node config file?
clmhwybe
Premium Member
Premium Member
Posts: 8
Joined: Mon Jun 18, 2012 1:43 pm

Re: Unable to start ORCHESTRATE network connection on node

Post by clmhwybe »

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.
Post Reply