When you run the server-side connection diagnosis tool from the
Visual COBOL Development Hub server, the following tests are run:
Warning: Some tests require super-user privileges in order to diagnose correctly.
- Eclipse client machine
- The test attempts to ping the client machine specified by
eclipse-client.
- When the
-v flag is also set, the ping results are displayed. If no client machine is specified, the test is skipped.
- If the test fails, the server cannot ping the client machine, which suggests some sort of network configuration issue (such
as a failed DNS lookup, or a firewall or routing issue). Contact your network administrator to troubleshoot further.
- Development Hub daemon status
- The test checks that the Development Hub daemon is running. The daemon is required if you are using either the
Micro Focus DevHub using RSE or the
Micro Focus DevHub using SAMBA, NFS etc connection type. If you are using another type of connection, the test is skipped.
- If the test fails, see
To launch a server on the remote host using a daemon process for details on restarting the daemon.
- Development Hub daemon connect
- The test checks that it can connect to the daemon.
- If the test fails, it could suggest a firewall problem, in which case, temporarily turn off the firewall and rerun the test.
We also advise stopping and restarting the daemon; see
Configuring the Remote System Explorer Support for details.
- JVM version
- The test checks that the version of Java is from one of the supported vendors, and a supported version.
- If the test fails, you should check the version of Java against the list of supported versions listed in the
Java JDK topic under
Additional Software Requirements.
- Check for required tools
- The test checks that all the required tools are present on the
Visual COBOL Development Hub server. When the
-v flag is also set, a list of the required tools is displayed.
-
If the test fails, re-install the tools highlighted as missing.
Note: If the test indicates that
sed or
ed is missing, we advise that you also reinstall the Development Hub after the required tools have been re-installed.
- SE Linux state
- The test checks if the SELinux security module is enabled. This module is not supported with the
Visual COBOL Development Hub.
- If the test fails, you must disable the SELinux module.
- Firewall checks supported OS and version
- The test checks for a supported platform for the firewall checks, which are only supported on the following platforms/versions:
Red Hat 7.2 (and later), CentOS 7.2 (and later).
- Required tools for firewall checks
- The test checks for the existence of the following tools:
systemctl and
firewall-cmd.
- Firewall state
- The test checks the status of the firewall, as reported by the
systemctl status firewalld command.
- Firewall bind zone
- The test checks for an active firewall zone to which the client address is bound.
- Firewall ports
- The test checks whether the RDO daemon port (4075 by default) is open in the firewall-bound zone.
If you need to grant more ports access through the firewall, use the
configrdo utility
.
- Firewall ssh service
- The test checks whether the ssh service is open in the firewall-bound zone.
- Firewall samba service
- The test checks whether the samba service is open in the firewall-bound zone.
- Firewall ICMP packets blocking
- The test checks whether the firewall is blocking any ICMP (Internet Control Message Protocol) packets, such as Echo requests,
from the client-bound zone.
- Check for license daemons
- The test checks that the license daemons are running during compilation and run time.
- If the test fails, you must start the license daemons by logging in with super user privileges and running:
/var/microfocuslicensing/bin/startmfcesd.sh
- Password crypt
-
The test checks if the password supplied is valid for a user ID. Run the
ivp command with the
-u parameter to specify the user. As the test runs, you are prompted to enter the password of the specified user.
Note: The test uses the
etc/passwd function as its authentication model.
-
If the test fails, check the user credentials using the substitute user (su) command.
- Compile and run COBOL 32-/64-bit and PL/I 32-/64-bit
- The test checks that it can compile and run a program.
- If the test fails, rerun the test with the
-v flag set to provide more information, then troubleshoot as you would for a standard compilation or run-time problem.
- X Display
- The test checks that an X Server installation is running on the client machine.
- If the test fails, it indicates that either the specified X Server is not running or not configured to allow remote connections.
Either start the X Server on the client machine, or if it is already running, configure it to allow remote connections. Refer
to your X Server installation documentation for details on allowing remote connections.
- Check for xterm
- Checks that xterm is found in $COBDIR/bin.
- If the test fails, you need to install xterm into the required location.
- su to user
- The test checks that it can execute the
su command for the specified user name. Run the
ivp command with the
-u parameter to specify the user.
- If the test fails, contact your network administrator to troubleshoot further.