Hi
When i tried connecting to DS Server i get the following error
Failed to connect to host: <ip address >, project: <xyz>(The connection is broken (81002))
Thanks
Pramod
Failed to connect to host ?
Moderators: chulett, rschirm, roy
Failed to connect to host ?
Thanks
Pramod
Pramod
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
This error code can mean that the connection has timed out based on the inactivity timeout setting. This is most often seen when you've left the client unattended for some time.
It might also mean that the DataStage RPC daemon (dsrpcd) is no longer running.
It might also mean that the DataStage RPC daemon (dsrpcd) is no longer running.
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.
-
- Premium Member
- Posts: 70
- Joined: Thu Aug 14, 2003 6:24 am
- Contact:
Help: HOW to get my DS server up and running
Ray,
1. A client was connected to DS server, when it was brought down.
2. After sometime the DS server was started. When client was trying to connect to the server it gave RPC daemon failed.
3. We killed a dsrpc process (fin_wait_2) thread
4. after which we tried to connect to the DS, it gave the error.
Now my question is ,
How to get back the DS server up and running so that i can connect to the DS server thru client.
Thanks
Pramod
1. A client was connected to DS server, when it was brought down.
2. After sometime the DS server was started. When client was trying to connect to the server it gave RPC daemon failed.
3. We killed a dsrpc process (fin_wait_2) thread
4. after which we tried to connect to the DS, it gave the error.
Now my question is ,
How to get back the DS server up and running so that i can connect to the DS server thru client.
Thanks
Pramod
ray.wurlod wrote:This error code can mean that the connection has timed out based on the inactivity timeout setting. This is most often seen when you've left the client unattended for some time.
It might also mean that the DataStage RPC daemon (dsrpcd) is no longer running.
Thanks
Pramod
Pramod
-
- Participant
- Posts: 3593
- Joined: Thu Jan 23, 2003 5:25 pm
- Location: Australia, Melbourne
- Contact:
Do you have any dsapi_slave or dscs processes still hanging around? Kill these off and try starting your server again.
Have a look in the install and upgrade guide under the dsrpcd Issues section for a longer description of this. It suggests the sockets can take 6-10 minutes to timeout after you shut down with dsrpc connections open.
Have a look in the install and upgrade guide under the dsrpcd Issues section for a longer description of this. It suggests the sockets can take 6-10 minutes to timeout after you shut down with dsrpc connections open.
Certus Solutions
Blog: Tooling Around in the InfoSphere
Twitter: @vmcburney
LinkedIn:Vincent McBurney LinkedIn
Blog: Tooling Around in the InfoSphere
Twitter: @vmcburney
LinkedIn:Vincent McBurney LinkedIn