Cascade Connect: Version 4.0
Prev	Chapter 4. Testing	Next

4.2. Testing the Connect Server installation

After installing the Connect Server, you should run the casctest program. This program emulates the Cascade Connect executable (cascade.exe), sending information via TCP/IP to the Connect Server, and has been provided to help determine whether the /etc/inetd.conf and /etc/services files are configured correctly. The Connect Server is normally started by Cascade Connect through the inetd task on the data server.

The test procedure uses the Cogent name server nserve, so you must ensure that the Cogent programs qserve and nserve are running. These programs must be started in order, with the commands:
```
    [sh]$ qserve
    [sh]$ nserve
```
If you get one of the following messages it means that qserve or nserve (respectively) are already running.
```
    Queue manager could not attach name 'qserve': Device or resource busy
    nserve: attach O/S name 'sc/nserve' failed: Device or resource busy
```
Run the casctest program from the data server prompt as root:
```
    [sh]$ su
    # casctest
    Cascade>
```
The Cascade> prompt indicates that casctest is ready for interactive input.
Give a name to your casctest task by typing this command at the Cascade> prompt:
```
    Cascade>(qnx_name_attach 0 myname)
    This software is free for non-commercial use, and no valid commercial license
    is installed.  For more information, please contact info@cogent.ca.
```
If the license message appears, it means that you are not using Cascade Connect under a commercial license, but it will still run. If you do have a commercial license and you see this message, contact Cogent.
Now, from another console you should be able to view running tasks by issuing the following command at the shell prompt:
- In QNX:
```
    [sh]$ sin name
```
- In Linux:
```
    [sh]$ nsnames
```
The resulting list of names should include the name myname, which represents the Connect Server. This indicates that the /etc/inetd.conf and /etc/services files are configured correctly.
If you do not see myname, then your installation may not be correct.
If you see myname on the list, terminate the casctest program in the appropriate console by pressing Ctrl C at the Cascade> prompt, and move on to Testing Cascade Connect operation. Othewise, you should refer to the troubleshooting information below.

4.2.1. Troubleshooting the installation

In QNX

Ensure that the data server nameloc program is running (check the sin names list from above). This program is normally started in the file /etc/config/sysinit.node with the command:
```
    [sh]$ nameloc &
```
There must be at least one nameloc program running on your network.
Ensure that the data server task Socket is running (check the sin names list from above). If Socket is not running, then you must start it by issuing the following set of commands as a root user:
```
    # Socket -s1 mymachine.mycompany.mydomain &
    # ifconfig lo0 localhost up
    # ifconfig en1 mymachine.mycompany.mydomain up netmask 255.255.255.0
    # portmap &
    # inetd &
```
As with the nameloc task, these commands should be run automatically, when the computer boots, so the commands should be placed in your /etc/config/sysinit.node file.

In both QNX and Linux

Ensure that your /etc/hosts file has a correct entry for the current node. You must have a line in the file /etc/hosts that maps your IP address to a machine name; it is this name that is used by Cascade Connect as a reference in both the data server and Windows. The name should be of the form:
```
    machine.company.domain
```
For example:
```
    albert.acme.com
```
Ensure that inetd is running (check the list of names from above). You can initiate the inetd task by issuing the following command:
```
    [sh]$ inetd &
```

Ensure that inetd is correctly configured. You should have the following line in the /etc/inetd.conf file:

    cascade stream tcp nowait root /usr/local/bin/cascade cascade

If you need to change /etc/inetd.conf, you must restart inetd.

Some Linux distributions use the command xinetd instead of inetd. If yours does, you will need to add a file called /etc/xinetd.d/cascade with the following information, then restart xinetd:

    service cascade
    {
       flags           = REUSE
       socket_type     = stream
       wait            = no
       user            = root
       server          = /usr/cogent/bin/cascade
       log_on_failure  += USERID
       disable         = no
    }

Then use xinetd instead of inetd when following the rest of these instructions

Ensure that /etc/services file has been correctly configured. You should have the following line at the end of the /etc/services file:
```
    cascade        4501/tcp
```
This line must also appear in c:\windows\services (or the appropriate services file for your Windows installation) on each of your Windows computers that will have Cascade Connect running on them.
Ensure that inetd is listening to the cascade port. If you run the commands:
```
    [sh]$ su
    #netstat -an
```
You should get an output line like this:
```
    tcp   0   0 0.0.0.0:4501    0.0.0.0:*     LISTEN
```
This indicates that inetd is listening to the cascade port. If you don't see this, try either re-starting inetd, or running the following command to cause inetd to re-read its configuration:
```
    #killall -HUP inetd
```
To get a better picture of what is happening, run inetd in debug mode in a separate window by doing this:
```
    #killall inetd
    #inetd -v
```
This will print messages to the console indicating when a program attempts to connect to a port that inetd is serving. You should see inetd start the cserve process when you run casctest, and you should see inetd "reap" the process when you exit casctest.

Once you have confirmed that a task called myname is running after you issue the casctest command, you can now move to the Windows computer to test the installation of the Windows components and the communication from Windows to the data server.