elasticsearch-Ansible


(tulasiram) #1

elasticsearch not started and shows the error which is in SS always. it has automated by Ansible. please provide the solution that where the issue has occured and how to resolve?!.

[ansible@ip-172-31-21-60 ~]$ sudo service elasticsearch start
Starting elasticsearch (via systemctl): Job for elasticsearch.service failed because the control process exited with error code. See "systemctl status elasticsearch.service" and "journalctl -xe" for details.
[FAILED]
after execute , Journalctl -xe :

Oct 13 08:23:01 ip-172-31-21-60.ap-south-1.compute.internal kibana[515]: {"type":"log","@timestamp":"2017-10-13T08:23:01Z","tags":["warning","elasticsearch","admin"],"pid":515,"message":"No living connections"}
Oct 13 08:23:03 ip-172-31-21-60.ap-south-1.compute.internal sudo[2936]: ansible : TTY=pts/1 ; PWD=/home/ansible ; USER=root ; COMMAND=/bin/journalctl -xe

in logs :slight_smile:
Oct 13 08:50:49 ip-172-31-21-60.ap-south-1.compute.internal sshd[3563]: Received disconnect from 59.45.175.24 port 37388:11: [preauth]
Oct 13 08:50:49 ip-172-31-21-60.ap-south-1.compute.internal sshd[3563]: Disconnected from 59.45.175.24 port 37388 [preauth]
Oct 13 08:50:51 ip-172-31-21-60.ap-south-1.compute.internal kibana[515]: {"type":"log","@timestamp":"2017-10-13T08:50:51Z","tags":["warning","elasticsearch","admin"],"pid":515,"message":"Unable to revive connection: http://172.31.21.60:9200/"}
Oct 13 08:50:51 ip-172-31-21-60.ap-south-1.compute.internal kibana[515]: {"type":"log","@timestamp":"2017-10-13T08:50:51Z","tags":["warning","elasticsearch","admin"],"pid":515,"message":"No living connections"}
Oct 13 08:50:54 ip-172-31-21-60.ap-south-1.compute.internal kibana[515]: {"type":"log","@timestamp":"2017-10-13T08:50:54Z","tags":["warning","elasticsearch","admin"],"pid":515,"message":"Unable to revive connection: http://172.31.21.60:9200/"}
Oct 13 08:50:54 ip-172-31-21-60.ap-south-1.compute.internal kibana[515]: {"type":"log","@timestamp":"2017-10-13T08:50:54Z","tags":["warning","elasticsearch","admin"],"pid":515,"message":"No living connections"}
Oct 13 08:50:56 ip-172-31-21-60.ap-south-1.compute.internal kibana[515]: {"type":"log","@timestamp":"2017-10-13T08:50:56Z","tags":["warning","elasticsearch","admin"],"pid":515,"message":"Unable to revive connection: http://172.31.21.60:9200/"}
Oct 13 08:50:56 ip-172-31-21-60.ap-south-1.compute.internal kibana[515]: {"type":"log","@timestamp":"2017-10-13T08:50:56Z","tags":["warning","elasticsearch","admin"],"pid":515,"message":"No living connections"}


(Mark Walkom) #2

Please don't post pictures of text, they are difficult to read and some people may not be even able to see them.


(tulasiram) #3

thanks warkolm , i have updated with error mesages and journal log information.


(system) #4

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