px.connect.fail##### files generated

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
peep
Premium Member
Premium Member
Posts: 162
Joined: Mon Aug 20, 2012 6:52 pm

px.connect.fail##### files generated

Post by peep »

In my DataStage environment under /tmp is px.connect.fail#### files

I see them on few of my remote servers where datastage scratch disk is mounted (nfs) .

I am assuming some connection fail while accessing scratch disk and this is generating these logs..

Did any one see such files in your servers ?
if yes please shed some light .


Thanks
priyadarshikunal
Premium Member
Premium Member
Posts: 1735
Joined: Thu Mar 01, 2007 5:44 am
Location: Troy, MI

Post by priyadarshikunal »

Don't have access to check so need to ask whether you have any content in those files or they are just 0 byte files?
Priyadarshi Kunal

Genius may have its limitations, but stupidity is not thus handicapped. :wink:
peep
Premium Member
Premium Member
Posts: 162
Joined: Mon Aug 20, 2012 6:52 pm

Post by peep »

these logs have info about
hostname , ports ,dsd.run and connections established and wait state

So basically it has lot of information about the server.


After lot of research I figured when a datastage job is initiated and failed abruptly then these logs are generated.


If you have more info pls share.
priyadarshikunal
Premium Member
Premium Member
Posts: 1735
Joined: Thu Mar 01, 2007 5:44 am
Location: Troy, MI

Post by priyadarshikunal »

I think you have your answer. And even in case of abrupt failure, the job related information is saved in &PH& folder in project directory. These files only generated when there is a connector stage in your job which failed abruptly, IMO.
Priyadarshi Kunal

Genius may have its limitations, but stupidity is not thus handicapped. :wink:
peep
Premium Member
Premium Member
Posts: 162
Joined: Mon Aug 20, 2012 6:52 pm

Post by peep »

I have tried with a job having a connector stage and by killing the job in the middle of execution but could not generate these files .
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

I think the failure has to be from the database end.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
peep
Premium Member
Premium Member
Posts: 162
Joined: Mon Aug 20, 2012 6:52 pm

Post by peep »

I am seeing these files on compute nodes (server2)also ..
where my scratch disk is located . ..

And my engine is located on conductor node server 1.
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Yes, I believe they're written there when the connector detects a failure in what it's connected to.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
peep
Premium Member
Premium Member
Posts: 162
Joined: Mon Aug 20, 2012 6:52 pm

Post by peep »

is this connector failure have to do with kernel limits ?
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Almost certainly not. Problems with kernel size will usually be picked up at installation time.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Post Reply