If you are experiencing problems opening your remote projects or establishing remote connections, run the connection diagnostics tool on your development hub to narrow down the problem. The tool runs a number of server-side tests.
Note: There is also a client-side diagnostics tool that you should run from the Eclipse IDE to troubleshoot connection problems.
Note: By default, the diagnostics tool is installed in
$COBDIR/remotedev.
Run the diagnostics tool from the command line, with super user privileges, using the following syntax:
ivp [options] [eclipse-client[:display-number]]
where [options] are:
- -h
- Displays the valid syntax that you can use.
- -d
port-number
- The port number used by the development hub daemon.
- -u
user name
- The name of the user connecting to the development hub.
Note: Not all tests can be run if you do not supply the user name.
- -p
password
- The password for the user name.
Note: If you do not want to enter the password on the command line, you can omit it. You are prompted for it during the appropriate test.
- -v
- Displays verbose output for appropriate tests. For example, the
required tools test lists the individual tools that are required.
And [eclipse-client[:display-number]] is:
- eclipse-client
- The Eclipse client that is unable to connect.
- display-number
- Defaults to 0 (zero) if not specified.
The tool runs a series of tests, which result in a pass or a fail. If a failure occurs, the rest of the tests are not run. Some test fails that are not fatal produce a warning message, and the tool will continue to run the subsequent tests. See the details below for a brief description of each test, and possible reasons for its failure.
