Device Server installation failed with timeout errors

Products

VMware Smart Assurance Network Observability

Issue/Introduction

Symptoms:

Unable to complete installation of Smarts NCM

Below is an error snippet of this issue from the NCM daemon logs :

<body class="normal" bgcolor="#FFFFFF">
<H1>Setup Manager: Review Actions</H1>
<p>The following actions were performed:</p>
<ol><li>Stopping Device Server Daemons...</li><li><font color="red">Can't create IDX for this server: Error: HTTP Error: Remote connection failed: Connection timed out</font></li><li>Starting Device Server Daemons...</li></ol><p><font color="red">An error has occurred.</font> Please click your browser "back" button
to correct the error. To restart setup, click "Setup" below. If the problem continues to
occur, please contact Customer Support.</p>
<form method="POST" name="Setup">
    <input type="submit" name="Script" value="Setup" onClick="window.location='/voyence-bin/setupmgr.cgi';return false;">
</form>
<table border="0" width="100%">
    <tr>
        <td>
            &copy;2008 <a target="_blank" href="http://www.voyence.com">Voyence</a>        </td>
        <td align="right" valign="bottom">
            <font size="2">Version ==version==.==build==</font>
        </td>
    </tr>
</table>
</body>
</html>
Stopping voyence service
Starting service voyence
0 :Waiting for sync...
1 :Waiting for sync...
2 :Waiting for sync...
3 :Waiting for sync...
4 :Waiting for sync...
 
ERROR: Timeout exceeded waiting for server configuration to sync.
ERROR: The server registration process failed.  Verify that the Apache HTTP Server is running and listening on both TCP 80 and TCP 443.
 
<Date & Time> -281663520#1: llPROF: check1 after setup milli 0, secs 0
<Date & Time> -281663520#1: Connect failed: Connection timed out
<Date & Time> -281663520#1: HTTP Error: Remote connection failed: Connection timed out
<Date & Time> -281663520#1: Error: Configuration can't be set
<Date & Time> -281663520#1: Error: HTTP Error: Remote connection failed: Connection timed out
<Date & Time> -281663520#1: Starting Voyence Control!...
<Date & Time> setupmgr#1| 5204: -------- setupmgr: stopped ######## --------
 
 
Copying /tmp/lockb.clb /apps/smarts-ncm/data/
==> Retrieving the test secret...
Error: Lockbox Access Error: The system hostname key is missing from the Lockbox.
Resolution:Lockbox Access Error: Please check the lockbox access on this server, Please refer to the NCM troubleshooting guide for possible resolution.

Environment

All Supported NCM releases

Cause

Smarts NCM installation fails because the tcp ports 80 and 443 being occupied by other processes.

Resolution

We need to ensure that the tcp ports 80 and 443 are open and not occupied by any other processes, before proceeding with the installation.

Use to following commands to check the same:

netstat -anpt | grep <port>

For instance port 80:

netstat -anpt | grep 80
tcp        0      0 :::80                       :::*                        LISTEN      4382/httpd

In this case the pid which is using port 80 is 4382

Get in touch with the server administrators to ensure if the process occupying these ports could be stopped so that NCM services can be operational on the same.

Additional Information

List of Communication ports used by NCM are listed at: Communication Security Settings