Page 1 of 1

dssh hang and client not able to connect

Posted: Fri Jul 18, 2014 3:14 pm
by mandyli
Hi

Past one day we are not able to connect datastage server. we are getting following error.

Error message: We are getting following error when we try to connect from Datastage client

Failed to connect to Information Server Engine: abcd:31539, project: aaaaa.
(The connection has timed out (81015))
Loaded modules:
C:\WINDOWS\WinSxS\x86_Microsoft.Windows.GdiPlus_6595b64144ccf1df_1.0.6002.23084_x-ww_f3f35550\gdiplus.dll 5.2.6002.23084
C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.6028_x-ww_61e65202\comctl32.dll 6.0.2900.6028
C:\WINDOWS\WinSxS\x86_Microsoft.VC90.CRT_1fc8b3b9a1e18e3b_9.0.30729.6161_x-ww_31a54e43\MSVCR90.dll 9.0.30729.6161
C:\WINDOWS\system32\xpsp2res.dll 5.1.2600.5512

//-------------------------------------------------------------

But I can able to connect XMETA database via sql plus from same Datastage server and able to ping also.

And also I noticed that dssh also hung in that datastage server

/opt/IBM91/InformationServer/Server/DSEngine$ . $DSHOME/dsenv

/opt/IBM91/InformationServer/Server/DSEngine$ cd $DSHOME
/opt/IBM91/InformationServer/Server/DSEngine$ bin/dssh "LIST.READU"

But other server I can able to run same dssh without any issue.

Is there any issue with UV repository or issue with XMETA ?

Thanks for your help.

Thanks
Man

Posted: Fri Jul 18, 2014 6:45 pm
by ray.wurlod
What service do you have configured to listen on port number 31539? Is this service actually running? Or, perhaps, is someone using an incorrect port number in the login credentials?

Posted: Fri Jul 18, 2014 9:09 pm
by mandyli
What service do you have configured to listen on port number 31539 :

Sorry I am not able to get this. Are you referring telnet services?


Thanks

Man

Posted: Fri Jul 18, 2014 9:11 pm
by mandyli
My network/firewall team saying

the rule permits all tcp and udp high-ports (1023-65535).

Thanks
Man

Posted: Tue Jul 22, 2014 12:06 pm
by mandyli
Hi Ray,

I have fixed this issue. I asked AIX team to reboot the whole box.


Thanks
Man