Since Today i get the warning:
Failed to connect to JobMonApp on port 13401
I know, that there are alredy many posts on this issue. I think, i have read most of them.
I stopped and re-started the JobMonitor several times.
I stopped and re-started Datastage several times.
I used "ipcrm" and "clearsockets".
Nothing helped.
Does anybody have any further idea, what could solve the problem?
Best regards
Manfred
Failed to connect to JobMonApp on port 13401
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 58
- Joined: Wed Apr 04, 2007 10:02 am
-
- Participant
- Posts: 58
- Joined: Wed Apr 04, 2007 10:02 am
Hello Chulett,
First "netstat -a |grep 13401" showed nothing.
After restarting Datastage again, it shows:
tcp 0 0 *.13401 *.* LISTEN
But Warning still is in the log.
Beside the message mentioned in the header, there is in the log:
Contents of phantom output file =>
DataStage Job 1204 Phantom 14406
OpenSocket() returned 16
DataStage Phantom Finished.
For restarting Datastage i have a small job, using a sleep of 60 between stop and start.
Best regards
Manfred
First "netstat -a |grep 13401" showed nothing.
After restarting Datastage again, it shows:
tcp 0 0 *.13401 *.* LISTEN
But Warning still is in the log.
Beside the message mentioned in the header, there is in the log:
Contents of phantom output file =>
DataStage Job 1204 Phantom 14406
OpenSocket() returned 16
DataStage Phantom Finished.
For restarting Datastage i have a small job, using a sleep of 60 between stop and start.
Best regards
Manfred
You really shouldn't do this on a timer, but rather after a check for open ports returns zero in that state:Manfred Hagedorn wrote:For restarting Datastage i have a small job, using a sleep of 60 between stop and start.
Code: Select all
netstat -a |grep dsrpc | wc -l
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Participant
- Posts: 58
- Joined: Wed Apr 04, 2007 10:02 am
Hello,
thanks for your replay.
1. APT_ORCHHOME: how should i set this? You really think, this parameter is related to JobMonitor?
2. netstat -a |grep dsrpc | wc -l shows: 1
So, i still don't really know, how to get the JobMonitor runing.
Just to mention again, JobMonitor was runing in the past, and i have re-started him in the past several times ... something must have changed or be different now, but what ???
As a workaround, it would help me, just to remove "Failed to connect to JobMonApp on port 13401" from the log and get a return code without warnings. But i tried to do this with the Message Handler in the Director, but this warning doesn't have a message id and i can't suppress it from log ???
Best regards
Manfred
thanks for your replay.
1. APT_ORCHHOME: how should i set this? You really think, this parameter is related to JobMonitor?
2. netstat -a |grep dsrpc | wc -l shows: 1
So, i still don't really know, how to get the JobMonitor runing.
Just to mention again, JobMonitor was runing in the past, and i have re-started him in the past several times ... something must have changed or be different now, but what ???
As a workaround, it would help me, just to remove "Failed to connect to JobMonApp on port 13401" from the log and get a return code without warnings. But i tried to do this with the Message Handler in the Director, but this warning doesn't have a message id and i can't suppress it from log ???
Best regards
Manfred