License for base elasticsearch

Hi Team,

As we known, the basic are free, after i install the basic version, when I install elasticsearch, kibana, it's prompt me "Elasticsearch cluster did not respond with license information."

Please advise

Thanks
Wayne

What version did you install?
Where does it prompt this?
Can you show logs?

Thanks warkolm

Please check version with below json

{
"name" : "node-1",
"cluster_name" : "elasticsearch",
"cluster_uuid" : "na",
"version" : {
"number" : "7.1.0",
"build_flavor" : "default",
"build_type" : "rpm",
"build_hash" : "606a173",
"build_date" : "2019-05-16T00:43:15.323135Z",
"build_snapshot" : false,
"lucene_version" : "8.0.0",
"minimum_wire_compatibility_version" : "6.8.0",
"minimum_index_compatibility_version" : "6.0.0-beta1"
},
"tagline" : "You Know, for Search"
}

Below is the elasticsearch detail log, after I start kibana

log [10:13:38.654] [error][status][plugin:xpack_main@7.1.0] Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.
log [10:13:38.655] [error][status][plugin:graph@7.1.0] Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.
log [10:13:38.656] [error][status][plugin:spaces@7.1.0] Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.
log [10:13:38.657] [error][status][plugin:security@7.1.0] Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.
log [10:13:38.657] [error][status][plugin:searchprofiler@7.1.0] Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.
log [10:13:38.658] [error][status][plugin:ml@7.1.0] Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.
log [10:13:38.658] [error][status][plugin:tilemap@7.1.0] Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.
log [10:13:38.658] [error][status][plugin:watcher@7.1.0] Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.
log [10:13:38.659] [error][status][plugin:grokdebugger@7.1.0] Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.
log [10:13:38.659] [error][status][plugin:logstash@7.1.0] Status

Which exact link did you download elasticsearch from? Could you share elasticsearch full logs?

Please format your code, logs or configuration files using </> icon as explained in this guide and not the citation button. It will make your post more readable.

Or use markdown style like:

```
CODE
```

This is the icon to use if you are not using markdown format:

There's a live preview panel for exactly this reasons.

Lots of people read these forums, and many of them will simply skip over a post that is difficult to read, because it's just too large an investment of their time to try and follow a wall of badly formatted text.
If your goal is to get an answer to your questions, it's in your interest to make it as easy to read and understand as possible.

Ensure what type of licence you are using:

GET /_xpack/license

If your ES node is alive, try:

POST _xpack/license/start_basic?acknowledge=true

Thanks a lots, I will try it tomorrow.

获取 Outlook for iOS

Hi vasek

I reinstall elasticsearch 7.1.1 OOS version today, elasticsearch could start normal, but when I start kibana, It's still below errors

  log   [03:44:18.524] [error][status][plugin:xpack_main@7.1.0] Status changed f                                                                             rom yellow to red - [data] Elasticsearch cluster did not respond with license in                                                                             formation.
  log   [03:44:18.529] [error][status][plugin:graph@7.1.0] Status changed from y                                                                             ellow to red - [data] Elasticsearch cluster did not respond with license informa                                                                             tion.
  log   [03:44:18.542] [error][status][plugin:spaces@7.1.0] Status changed from                                                                              yellow to red - [data] Elasticsearch cluster did not respond with license inform                                                                             ation.
  log   [03:44:18.542] [error][status][plugin:security@7.1.0] Status changed fro                                                                             m yellow to red - [data] Elasticsearch cluster did not respond with license info                                                                             rmation.
  log   [03:44:18.544] [error][status][plugin:searchprofiler@7.1.0] Status chang                                                                             ed from yellow to red - [data] Elasticsearch cluster did not respond with licens                                                                             e information.
  log   [03:44:18.544] [error][status][plugin:ml@7.1.0] Status changed from yell                                                                             ow to red - [data] Elasticsearch cluster did not respond with license informatio                                                                             n.
  log   [03:44:18.549] [error][status][plugin:tilemap@7.1.0] Status changed from  
[03:44:19.387] [warning][reporting] The Reporting plugin encountered iss                                                                             ues launching Chromium in a self-test. You may have trouble generating reports:                                                                              Error: socket hang up
  log   [03:44:19.387] [warning][reporting] See Chromium's log output at "/var/l                                                                             ib/kibana/headless_shell-linux/chrome_debug.log"
 error  [03:44:48.441] [warning][process] UnhandledPromiseRejectionWarning: Error: Request Timeout after 30000ms
    at /usr/share/kibana/node_modules/elasticsearch/src/lib/transport.js:355:15
    at Timeout.<anonymous> (/usr/share/kibana/node_modules/elasticsearch/src/lib/transport.js:384:7)
    at ontimeout (timers.js:436:11)
    at tryOnTimeout (timers.js:300:5)
    at listOnTimeout (timers.js:263:5)
    at Timer.processTimers (timers.js:223:10)
    at emitWarning (internal/process/promises.js:81:15)
    at emitPromiseRejectionWarnings (internal/process/promises.js:120:9)
    at process._tickCallback (internal/process/next_tick.js:69:34)
 error  [03:44:48.442] [warning][process] Error: Request Timeout after 30000ms
    at /usr/share/kibana/node_modules/elasticsearch/src/lib/transport.js:355:15
    at Timeout.<anonymous> (/usr/share/kibana/node_modules/elasticsearch/src/lib/transport.js:384:7)
    at ontimeout (timers.js:436:11)
    at tryOnTimeout (timers.js:300:5)
    at listOnTimeout (timers.js:263:5)
    at Timer.processTimers (timers.js:223:10)
  log   [03:44:49.239] [warning][reporting] Could not retrieve cluster settings, because of Request Timeout after 30000ms
  log   [03:44:49.319] [warning][task_manager] PollError Request Timeout after 30000ms

I use your provide the command to set base license failed to, below is the screenshot

image

Hi Wayne,

Cluster state
What is your cluster state? Is your cluster green?

 GET /_cat/health?h=st

Ports and IPs of ES and Kibana instances

#Linux Command
netstat -tulpn | grep '\(9[23]00\|5601\)'

There is a documentation for netstat running on Windows OS.

Nodes in cluster
How many ES nodes do you have in cluster?

GET /_cat/nodes

Configuration of ES and Kibana instances
Post configuration of elasticsearch.yml and kibana.yml please (ideally without comments).

sed -n '/^[^#]\+/p' /etc/elasticsearch/elasticsearch.yml
sed -n '/^[^#]\+/p' /etc/kibana/kibana.yml

Post the outputs of these commands (IN TEXT FORM PLEASE).

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.