ElasticSearch无法在Ubuntu 16.04.3上启动-status = 1失败 [英] ElasticSearch Fails to Start on Ubuntu 16.04.3 - status=1 Failure

问题描述

此Ubuntu 16.04.3计算机上的ElasticSearch 6.2.2服务已经运行了好几个月.我今天重启了机器，发现ElasticSearch服务没有启动.所以我尝试了 sudo systemctl start elasticsearch.service .没有给我任何错误.但是我注意到它仍然没有开始.

The ElasticSearch 6.2.2 service on this Ubuntu 16.04.3 machine has been running fine for a few months. I rebooted the machine today and found the ElasticSearch service had not started. So I tried sudo systemctl start elasticsearch.service. I was not given any error. But I noticed it still hadn't started.

运行 systemctl status elasticsearch 后，我得到了:

`● elasticsearch.service - Elasticsearch
   Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; enabled; vendor preset: enabled)
  Drop-In: /etc/systemd/system/elasticsearch.service.d
           └─override.conf
   Active: inactive (dead) (Result: exit-code) since Tue 2018-09-18 02:35:58 UTC; 19min ago
     Docs: http://www.elastic.co
  Process: 14147 ExecStart=/usr/share/elasticsearch/bin/elasticsearch -p ${PID_DIR}/elasticsearch.pid --quiet (code=exited, status=1/FAILURE)
 Main PID: 14147 (code=exited, status=1/FAILURE)

Sep 18 02:35:58 elastic-eu-vm-000 systemd[1]: elasticsearch.service: Unit entered failed state.
Sep 18 02:35:58 elastic-eu-vm-000 systemd[1]: elasticsearch.service: Failed with result 'exit-code'.
Sep 18 02:35:58 elastic-eu-vm-000 systemd[1]: elasticsearch.service: Service hold-off time over, scheduling restart.
Sep 18 02:35:58 elastic-eu-vm-000 systemd[1]: Stopped Elasticsearch.
Sep 18 02:35:58 elastic-eu-vm-000 systemd[1]: elasticsearch.service: Start request repeated too quickly.
Sep 18 02:35:58 elastic-eu-vm-000 systemd[1]: Failed to start Elasticsearch.

该解决方案似乎可以帮助许多无法在Ubuntu上启动ES服务的人找到此处(

The solution which seemed to help many people who couldn't start the ES service on Ubuntu found here (Can not start elasticsearch as a service in ubuntu 16.04), the one accepted as the answer, did not help me.

这是一台生产机器，所以希望有人能提供帮助！谢谢！

This is a production machine so I hope someone can help! Thanks!!

编辑1-在尝试查找日志文件很费劲之后，根据@ArnavRay的建议，它现在位于以下URL https://file.io/ASnEG4

EDIT 1 - after much pain trying to track down the log file, it's now at the following url per suggestion from @ArnavRay https://file.io/ASnEG4

推荐答案

日志中唯一的错误与x-pack安全性有关.您是否正在使用x-pack的任何功能?这里的链接描述了x-pack许可证过期时发生的情况. https://www.elastic.co/guide/zh/x-pack/current/license-expiration.html

The only error on the logs are related to the x-pack security. Are you using any of the features of x-pack? Here is a link that describes what happens when the x-pack license expires. https://www.elastic.co/guide/en/x-pack/current/license-expiration.html

尝试跑步 elasticsearch-plugin删除x-pack

elasticsearch-plugin的默认位置是/usr/share/elasticsearch/bin/.您可能需要使用sudo.从elasticsearch.yml中删除所有与x-pack相关的配置，然后重新启动ElasticSearch.

Default location for the elasticsearch-plugin is /usr/share/elasticsearch/bin/. You might need to use sudo. Remove all the x-pack related configuration from elasticsearch.yml and restart ElasticSearch.

https://github.com/deviantony/docker-elk/issues/154-与您的问题相同.

如果您仍然遇到问题，可以尝试以下操作.

If you are still facing issues you can try the following things.

1. 增加/etc/elasticsearch/
下jvm.options上的堆内存
2. 使用ls -a并检查是否已创建任何其他elasticsearch.yml文件.如果是这样，请将其删除.

3. 运行这些命令

1. Increase the heap memory on jvm.options under /etc/elasticsearch/
2. Use ls -a and check if any other elasticsearch.yml files has been created. If so remove them.

3. Run these commands

echo -e"elasticsearch-无限内存锁\ nstorm-nproc 257597"/etc/security/limits.confulimit -n 32768ulimit -u 65536echo -e"*-nofile 32768 \ n *-nproc 65536">>/etc/security/limits.conf

这篇关于ElasticSearch无法在Ubuntu 16.04.3上启动-status = 1失败的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！