Unable to install DataStage Server on UNIX environment

daryl317 · Post by **daryl317** » Wed Apr 22, 2009 7:08 am

During the install of DataStage Server in UNIX, it hangs where the install.sh checks the client connection:

$ ./install.sh

[DataStage Server 7.5.2 - Installation and Maintenance Utility]

Initializing setup

[DataStage Server 7.5.2 - Installation and Maintenance Utility]

Checking command line options

[DataStage Server 7.5.2 - Installation and Maintenance Utility]

=================================================================
--------------- W A R N I N G ---------------
=================================================================

Install was unable to detect a previous DataStage server.
By default, this will be treated as a new installation.

Existing DataStage installations, if any, will NOT be upgraded.

Continue with installation? [y|n]: y

[DataStage Server 7.5.2 - Installation and Maintenance Utility]

[DataStage Server 7.5.2 - Installation and Maintenance Utility]

Checking kernel parameters

[DataStage Server 7.5.2 - Installation and Maintenance Utility]

Checking client connections

Checking the Install log:

============================================================
Checking kernel parameters
Wed Apr 22 14:56:11 MESZ 2009
============================================================

DataStage server engine location specified by FROM_NOT_FOUND

============================================================
Checking client connections
Wed Apr 22 14:56:11 MESZ 2009
============================================================

We did not encounter any such problem when we have installed in the UA and DEV environments. The server is newly built so I'm not sure what we are missing here. Maybe an issue in the UNIX server perhaps?

daryl317 · Post by **daryl317** » Wed Apr 22, 2009 7:24 am

BTW, we tried root and non-root install but same issue.

chulett · Post by **chulett** » Wed Apr 22, 2009 7:37 am

Best to contact your official support provider for help with this, they're the only ones who will really know what it is attempting to do at the point that it hangs.

daryl317 · Post by **daryl317** » Thu Apr 23, 2009 4:11 am

Ok. I already resolved the issue. Here were the steps I have done.

1. To figure out what was causing the issue, I opened 2 Putty sessions. On the 1st window, I ran the install.sh script and while it is in the "Checking client connections" stage, I opened the other Putty session and did a "ps -ef | grep dsadm":

dsadm 2519142 2646306 0 11:47:11 pts/0 0:00 /usr/bin/netstat
dsadm 2646306 3232132 0 11:47:11 pts/0 0:00 tee -a /tmp/dsinstall/logfiles/dsinstall.log.042309.114704 /dev/tty
dsadm 3027270 2646306 0 11:47:11 pts/0 0:00 grep [.]dsrpc
dsadm 3211570 1 0 10:53:49 pts/0 0:01 /usr/bin/netstat
dsadm 3232132 3199472 0 11:47:04 pts/0 0:00 /bin/sh install.sh

2. Two processes caught my attention: "/usr/bin/netstat" and "grep [.]dsrpc". I came to assume that the install script is trying to do a "netstat | grep [.]dsrpc" in the server. I manually ran that script and to our surprise, it is also not completing and it seems that it got hung also. I tried to run this on our DEV server and was able to retrieve the DSRPC processes that were started by the DS server.

3. So to resolve the issue, I just killed the process where it got hung since the PID is different to the install.sh instance anyway. I only killed the "grep [.]dsrpc" (kill -9 3027270) and after this, the install.sh script seem to resume normally. Since this is a new installation, it wouldn't be a problem to kill this instance.

chulett · Post by **chulett** » Thu Apr 23, 2009 7:34 am

Odd... so 'netstat' is hanging on that server? I would bring that to the attention of your Admins, if you haven't already.

ray.wurlod · Post by **ray.wurlod** » Thu Apr 23, 2009 2:23 pm

... or are/were you just being impatient? netstat -a can take quite a while to complete even on moderately-sized systems; it has a lot of information to gather.

daryl317 · Post by **daryl317** » Sun May 03, 2009 10:09 pm

I know netstat could return a lot of result but it got hung there for about 2 hours already. The netstat command I believe is not a problem since I can run "netstat -aAn" just fine. But if I only run "netstat" then it wouldn't finish searching. I'm starting to believe that the server itself may have a lot of connections hanging up and thus causes problems for netstat to complete. Will be checking this up to the server admins to see what's going on.