Elasticsearch dead recently without modify anything

Elastic Stack Elasticsearch
1

i use kibana in Ubuntu16.04 and it shows：
Elasticsearch plugin is red
Unable to connect to Elasticsearch at http://127.0.0.1:9200

and i check about service and elasticsearch already dead. If I use command
"service elasticsearch restart".
It will be run for a while and dead with message shows by fellowing：
""
Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; enabled; vendor preset: enabled)
Active: inactive (dead) since 三 2018-01-24 17:28:29 CST; 19min ago
Docs: http://www.elastic.co
Process: 1321 ExecStart=/usr/share/elasticsearch/bin/elasticsearch -p ${PID_DIR}/elasticsearch.pid --quiet -Edefault.path.logs=${LOG_DIR} -Edefault.path.data=${DATA_DIR} -Edefault.path.co
Process: 1318 ExecStartPre=/usr/share/elasticsearch/bin/elasticsearch-systemd-pre-exec (code=exited, status=0/SUCCESS)
Main PID: 1321 (code=exited, status=0/SUCCESS)
一 24 17:28:27 jupyter elasticsearch[1321]: [2018-01-24T17:28:27,535][WARN ][o.e.c.l.LogConfigurator ] ignoring unsupported logging configuration file [/etc/elasticsearch/logging.yml], l
""

and the ES log shows：
""
[2018-01-24T17:28:27,535][WARN ][o.e.c.l.LogConfigurator ] ignoring unsupported logging configuration file [/etc/elasticsearch/logging.yml], logging is configured via [/etc/elasticsearch/log4j2.properties]
""

So, can anyone help me what is wrong in my computer? Is there somewhere capacity leak? Or something else. THX

2

Same here. Did you update to Java 8 161 recently?

3

Inspecting with
sudo journalctl -xe
showed
Kernel tried to execute NX-protected page - exploit attempt?

I reverted to the 4.13.0-25-generic linux kernel and now the service starts properly.

1 Like
4

@tomcgn confirmed similar behaviour.

Logs showed Kernel tried to execute NX-protected page - exploit attempt? with kernel version 4.13.0-31-generic but rolling back to 4.13.0.26-generic fixed the issue.

Issue only arose after the first reboot. Re-installing after issue arose would not fix.

5

I use sudo journalctl -xe.
And it shows ：
二 06 14:10:04 jupyter kibana[1014]: {"type":"log","@timestamp":"2018-02-06T06:10:04Z","tags":["warning","elasticsearch","admin"],"pid":1014,"message":"Unable to revive connection: http:/
二 06 14:10:04 jupyter kibana[1014]: {"type":"log","@timestamp":"2018-02-06T06:10:04Z","tags":["warning","elasticsearch","admin"],"pid":1014,"message":"No living connections"}
And my java version is 1.8.0 and i am sure i do not update

6

and I also check my another ELK service.
Java version is 1.8.0 and the elasticsearch can work

7

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