TheHive-Project / TheHive-Project/Cortex

None of the configured nodes are available: [{#transport#-1}{172}{172.17.0.4:9300}

Open
#288 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Scala
Stars
1.6k
Forks
264
PR merge metrics
No merged PRs in 30d

Description

Request Type

Configuration

Work Environment
Question Answer
OS version (server) Ubuntu
OS version (client) 16.04 (Security Onion image)
Cortex version / git hash docker.io/thehiveproject/cortex:3.1.0-0.2RC1
Package Type Docker
Browser type & version Chrome
Problem Description

TheHive is working with my ElasticSearch that come with Security Onion but Cortex that seem to need port 9300 TCP isn't working. The IP in the title is good and TheHive use the same but with port 9200. Elasticsearch is listening to port 9200 and 9300 and I can telnet both port but I get a connection reset with port 9300 so it look like the problem.

Is there a configuration that I need to change to let ElasticSearch port 9300 being able to get connection from Cortex docker environment ?

Thanks

Possible Solutions

Allow connection to ElasticSearch port 9300 for Cortex but how ?

Cortex configuration file application.conf
search {
index = cortex
cluster = "s02"
host = ["172.17.0.4:9300"]
}

Elasticsearch configuration file elasticsearch.yml
cluster.name: "s02"
network.host: 0.0.0.0
http.host: 0.0.0.0
transport.host: 0.0.0.0
transport.tcp.port: 9300

telnet 172.17.0.4 9300
Trying 172.17.0.4...
telnet: Unable to connect to remote host: Connection refused

Firewall (ufw) is open for port 9300 and 9200 and so on ...

lsof -i:9300 show that elasticsearch is listening also

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Cortex application.conf search settings and the Elasticsearch elasticsearch.yml transport and network settings. Reproduce the connection attempt from the Cortex Docker environment on port 9300 and compare it with the reported telnet results. Done means Cortex can connect to the configured Elasticsearch node and no longer reports that none of the configured nodes are available.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, elasticsearch
Domain
databases, devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.