Elasticsearch preflight checks (traditional)
Before you begin the installation process, you must verify that the required ports are open on each host. This verification is accomplished with a command-line tool, such as Netcat.
Here is an example:
Description | Commands |
|---|---|
Jama Core → Elasticsearch node(s) | nc -vz -w 2 <IP address> 9200 nc -vz -w 2 <IP address> 9300 |
Elasticsearch node(s) ↔ Elasticsearch node(s) | nc -vz -w 2 <IP address> 9300 |
Elasticsearch node(s) → Jama Core | nc -vz -w 2 <IP address> 9500 nc -vz -w 2 <IP address> 9874–9880 |
When you check port status from the command line, you see these possible responses:
Response | Meaning |
|---|---|
Connection to <DESTINATION> <PORT> port [<TCP/UDP>] succeeded! | The port is open on the remote host and a process is listening. |
nc: connect to <DESTINATION&> port <PORT> [<TCP/UDP>] failed: Connection refused | The port is open on the remote host, but no process is listening. |
nc: connect to <DESTINATION> port <PORT> [<TCP/UDP>] timed out: Operation now in progress | The port is not open on the remote host. |