Could not login: Login is currently disabled. Administrators should consult the Kibana logs for more details

[Shree]

I am having this Issue, also I am new for ELK field Please someone could help me out from this , it will be great.

I am using Elasticsearch 6.3.2, kibana 6.3.2 and I did not use/install xpack

my kibana logs:

Aug 01 07:48:22 localhost.localdomain kibana[3988]: {"type":"log","@timestamp":"2018-08-01T07:48:22Z","tags":["warning","elasticsearch
","admin"],"pid":3988,"message":"Unable to revive connection: http://localhost:9200/"}
Aug 01 07:48:22 localhost.localdomain kibana[3988]: {"type":"log","@timestamp":"2018-08-01T07:48:22Z","tags":["warning","elasticsearch
","admin"],"pid":3988,"message":"No living connections"}
Aug 01 07:48:25 localhost.localdomain kibana[3988]: {"type":"log","@timestamp":"2018-08-01T07:48:25Z","tags":["warning","elasticsearch
","admin"],"pid":3988,"message":"Unable to revive connection: http://localhost:9200/"}
Aug 01 07:48:25 localhost.localdomain kibana[3988]: {"type":"log","@timestamp":"2018-08-01T07:48:25Z","tags":["warning","elasticsearch
","admin"],"pid":3988,"message":"No living connections"}
Aug 01 07:48:27 localhost.localdomain kibana[3988]: {"type":"log","@timestamp":"2018-08-01T07:48:27Z","tags":["warning","elasticsearch
","admin"],"pid":3988,"message":"Unable to revive connection: http://localhost:9200/"}
Aug 01 07:48:27 localhost.localdomain kibana[3988]: {"type":"log","@timestamp":"2018-08-01T07:48:27Z","tags":["warning","elasticsearch
","admin"],"pid":3988,"message":"No living connections"}
Aug 01 07:48:30 localhost.localdomain kibana[3988]: {"type":"log","@timestamp":"2018-08-01T07:48:30Z","tags":["warning","elasticsearch
","admin"],"pid":3988,"message":"Unable to revive connection: http://localhost:9200/"}
Aug 01 07:48:30 localhost.localdomain kibana[3988]: {"type":"log","@timestamp":"2018-08-01T07:48:30Z","tags":["warning","elasticsearch
","admin"],"pid":3988,"message":"No living connections"}
Aug 01 07:48:32 localhost.localdomain kibana[3988]: {"type":"log","@timestamp":"2018-08-01T07:48:32Z","tags":["warning","elasticsearch
","admin"],"pid":3988,"message":"Unable to revive connection: http://localhost:9200/"}
Aug 01 07:48:32 localhost.localdomain kibana[3988]: {"type":"log","@timestamp":"2018-08-01T07:48:32Z","tags":["warning","elasticsearch
","admin"],"pid":3988,"message":"No living connections"}
root@localhost:~#

[tsullivan (Tim Sullivan)]

Hi Shree,

When you see Unable to revive connection: http://localhost:9200/ and No living connections that means Kibana is configured to use a default address to talk to Elasticsearch, but the Elasticsearch you are running isn't available at that address. It's not an ELK issue, it's just getting 2 services to see each other on a network.

You'll need to update the kibana.yml file and change the elasticsearch.url configuration to the address of your Elasticsearch node.

[Shree]

Thank you so much
I put localhost in elasticsearch network host., and I had to change it to my server ip address.
Also I changed the elasticsearch.url in kibana with elasticsearch network address.
It works fine now.

[tsullivan (Tim Sullivan)]

Great!

[Shree]

I am getting the same error again.
Yesterday I enabled metric beat, and it was working fine but when I opened today it's not working, looks very strange.

root@localhost:~# sudo service elasticsearch status
● elasticsearch.service - Elasticsearch
   Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; disabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sat 2018-08-04 07:57:56 UTC; 22min ago
     Docs: http://www.elastic.co
  Process: 3818 ExecStart=/usr/share/elasticsearch/bin/elasticsearch -p ${PID_DIR}/elasticsearch.pid --quiet (code=exited, s
tatus=1/FAILURE)
 Main PID: 3818 (code=exited, status=1/FAILURE)

Aug 04 07:57:47 localhost.localdomain systemd[1]: Started Elasticsearch.
Aug 04 07:57:56 localhost.localdomain systemd[1]: elasticsearch.service: Main process exited, code=exited, status=1/FAILURE

Aug 04 07:57:56 localhost.localdomain systemd[1]: elasticsearch.service: Unit entered failed state.
Aug 04 07:57:56 localhost.localdomain systemd[1]: elasticsearch.service: Failed with result 'exit-code'.

[tsullivan (Tim Sullivan)]

I'm not 100% sure, but it looks like your Elasticsearch service is unable to stay running, and it exits immediately.

There should be some clues in Elasticsearch logs, that give more detail beyond the service status.