License is not available #349
Comments
|
Could you please provide steps to reproduce your issue? |
|
I just ran the docker image as "sudo docker run -p 5601:5601 -p 9200:9200 -p 5044:5044 -it --name elkstack sebp/elk" |
|
I waited about 30 minutes and still nothing ==> /var/log/logstash/logstash-plain.log <== |
|
Looks as if Elasticsearch isn’t running. |
|
Here are the logs, I think you are referring to, you are correct I did not change anything I tried up the "latest" image sudo docker run -p 5601:5601 -p 9200:9200 -p 5044:5044 -it --name elkstack sebp/elk
==> /var/log/logstash/logstash-plain.log <== ==> /var/log/kibana/kibana5.log <== ==> /var/log/elasticsearch/elasticsearch.log <== ==> /var/log/kibana/kibana5.log <== ==> /var/log/logstash/logstash-plain.log <== ==> /var/log/kibana/kibana5.log <== ==> /var/log/logstash/logstash-plain.log <== |
|
Seems that Elasticsearch stopped running after starting up normally. |
|
You are correct it works fine on my Linux box but no my MAC Book thanks for pointing me in that direction |
|
That's my issue, works great on Linux but not on MAC thanks again |
|
Glad it helped understand your issue, but why this image isn’t working well on Macs remains a mystery at this point. |
|
I have the same issue with MAC |
|
Same issue with Docker for Windows |
|
Still a mystery :') |
|
So still doesn't work on MACs? I can share my snippet of docker-compose: version: '3'
services:
elasticsearch:
image: docker.elastic.co/elasticsearch/elasticsearch:7.15.0
container_name: elasticsearch
environment:
- cluster.name=integration-test
- discovery.type=single-node
- 'ES_JAVA_OPTS=-Xms512m -Xmx512m'
- logger.level=ERROR
ulimits:
memlock:
soft: -1
hard: -1
nofile:
soft: 65536
hard: 65536
ports:
- '9200:9200'
- '9300:9300'
networks:
- elastic
kibana:
image: docker.elastic.co/kibana/kibana:7.15.0
ports:
- 5601:5601
environment:
ELASTICSEARCH_URL: http://elasticsearch:9200
ELASTICSEARCH_HOSTS: http://elasticsearch:9200
networks:
- elastic
networks:
elastic:
driver: bridge |
|
It works actually. I allocated 16 gb ram and 10 CPU cores in order to make this image work! Elastic search is very resource intensive (thinking to outsource it from AWS in Production Env). |
|
@manjotsk I have it running fine on 2 GB RAM and 2 CPUs on Ubuntu Server, I don't have tons of data going through it about 50K DNS queries an hour. |
|
You mean the standalone Elastic search or the elk-docker? I guess I should think before coming to conclusions! It is strange that elastic search fell off on 8gb ram and 8 cpus on my MacBook Pro i9! However, increasing the limits helped to make the elk-docker image stable on my MacBook! |
|
I had a sort a like issue with the elk-docker image, MBP Specs: Start command: Solution: |
|
Spring cleaning: closing this issue due to inactivity. |
|
For me this got resolved by adding the following under elasticsearch container in docker-compose.yml |
👋🏼 howdy, team! When Kibana can't connect to Elasticsearch (past finding master / network issue, just unhealthy cluster ballpark), its code logic cascades into first tripping warn/error log `license is not available`. This is a red-herring in that the license can not be determined and user should investigate the network connection / Elasticsearch health rather than investigating for lapsed licenses. Adding this into the "Kibana not ready" docs since it raises at this point in the flow to hopefully allow users to search-find it in our content rather than e.g. top-goggle-results: [Discuss](https://discuss.elastic.co/t/license-not-available/265931), [external Github](spujadas/elk-docker#349).
👋🏼 howdy, team! When Kibana can't connect to Elasticsearch (past finding master / network issue, just unhealthy cluster ballpark), its code logic cascades into first tripping warn/error log `license is not available`. This is a red-herring in that the license can not be determined and user should investigate the network connection / Elasticsearch health rather than investigating for lapsed licenses. Adding this into the "Kibana not ready" docs since it raises at this point in the flow to hopefully allow users to search-find it in our official docs rather than e.g. top-goggle-results: [Elastic Discuss](https://discuss.elastic.co/t/license-not-available/265931), [external Github](spujadas/elk-docker#349).
👋🏼 howdy, team! When Kibana can't connect to Elasticsearch (past finding master / network issue, just unhealthy cluster ballpark), its code logic cascades into first tripping warn/error log `license is not available`. This is a red-herring in that the license can not be determined and user should investigate the network connection / Elasticsearch health rather than investigating for lapsed licenses. Adding this into the "Kibana not ready" docs since it raises at this point in the flow to hopefully allow users to search-find it in our official docs rather than e.g. top-goggle-results: [Elastic Discuss](https://discuss.elastic.co/t/license-not-available/265931), [external Github](spujadas/elk-docker#349). (cherry picked from commit b340cb3)
#161191) # Backport This will backport the following commits from `main` to `8.9`: - [[DOC+] License not available is KB-ES connection error (#161176)](#161176) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Stef Nestor","email":"26751266+stefnestor@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-07-04T14:26:43Z","message":"[DOC+] License not available is KB-ES connection error (#161176)\n\n👋🏼 howdy, team! When Kibana can't connect to Elasticsearch (past finding master /\r\nnetwork issue, just unhealthy cluster ballpark), its code logic cascades\r\ninto first tripping warn/error log `license is not available`.\r\n\r\nThis is a red-herring in that the license can not be determined and user\r\nshould investigate the network connection / Elasticsearch health rather\r\nthan investigating for lapsed licenses.\r\n\r\nAdding this into the \"Kibana not ready\" docs since it raises at this\r\npoint in the flow to hopefully allow users to search-find it in our\r\nofficial docs rather than e.g. top-goggle-results: [Elastic\r\nDiscuss](https://discuss.elastic.co/t/license-not-available/265931),\r\n[external Github](spujadas/elk-docker#349 License not available is KB-ES connection error (#161176)\n\n👋🏼 howdy, team! When Kibana can't connect to Elasticsearch (past finding master /\r\nnetwork issue, just unhealthy cluster ballpark), its code logic cascades\r\ninto first tripping warn/error log `license is not available`.\r\n\r\nThis is a red-herring in that the license can not be determined and user\r\nshould investigate the network connection / Elasticsearch health rather\r\nthan investigating for lapsed licenses.\r\n\r\nAdding this into the \"Kibana not ready\" docs since it raises at this\r\npoint in the flow to hopefully allow users to search-find it in our\r\nofficial docs rather than e.g. top-goggle-results: [Elastic\r\nDiscuss](https://discuss.elastic.co/t/license-not-available/265931),\r\n[external Github](spujadas/elk-docker#349 License not available is KB-ES connection error (#161176)\n\n👋🏼 howdy, team! When Kibana can't connect to Elasticsearch (past finding master /\r\nnetwork issue, just unhealthy cluster ballpark), its code logic cascades\r\ninto first tripping warn/error log `license is not available`.\r\n\r\nThis is a red-herring in that the license can not be determined and user\r\nshould investigate the network connection / Elasticsearch health rather\r\nthan investigating for lapsed licenses.\r\n\r\nAdding this into the \"Kibana not ready\" docs since it raises at this\r\npoint in the flow to hopefully allow users to search-find it in our\r\nofficial docs rather than e.g. top-goggle-results: [Elastic\r\nDiscuss](https://discuss.elastic.co/t/license-not-available/265931),\r\n[external Github](spujadas/elk-docker#349"}}]}] BACKPORT--> Co-authored-by: Stef Nestor <26751266+stefnestor@users.noreply.github.com>
👋🏼 howdy, team! When Kibana can't connect to Elasticsearch (past finding master / network issue, just unhealthy cluster ballpark), its code logic cascades into first tripping warn/error log `license is not available`. This is a red-herring in that the license can not be determined and user should investigate the network connection / Elasticsearch health rather than investigating for lapsed licenses. Adding this into the "Kibana not ready" docs since it raises at this point in the flow to hopefully allow users to search-find it in our official docs rather than e.g. top-goggle-results: [Elastic Discuss](https://discuss.elastic.co/t/license-not-available/265931), [external Github](spujadas/elk-docker#349). (cherry picked from commit b340cb3)
{"type":"log","@timestamp":"2021-04-11T14:38:57+00:00","tags":["error","plugins","security","authentication"],"pid":395,"message":"License is not available, authentication is not possible."}
The text was updated successfully, but these errors were encountered: