Question

我在运行Ubuntu 16.04 LTS的ARM Odroid XU4上安装了ELasticsearch 6和JDK 1.8.0_161。没有错误。

当我尝试将Elasticsearch作为服务启动时，我无法在端口9200上连接到localhost并打印服务状态：

~ $ > sudo service elasticsearch status
● elasticsearch.service - LSB: Starts elasticsearch
   Loaded: loaded (/etc/init.d/elasticsearch; bad; vendor preset: enabled)
   Active: active (exited) since Mon 2018-01-22 10:43:18 UTC; 9min ago
     Docs: man:systemd-sysv-generator(8)

Jan 22 10:43:18 lego systemd[1]: Starting LSB: Starts elasticsearch...
Jan 22 10:43:18 lego systemd[1]: Started LSB: Starts elasticsearch.
Jan 22 10:44:07 lego systemd[1]: Started LSB: Starts elasticsearch.

没有日志。不知道在哪里看。 nofile限制在/etc/security/limits.conf中设置为65536。我不知道在哪里寻找诊断。

虽然，当我通过sudo /usr/shared/elasticsearch/bin/elasticsearch手动启动Elasticsearch时，它按预期工作：

~ $ > sudo /usr/share/elasticsearch/bin/elasticsearch
[2018-01-22 10:55:55,944][WARN ][bootstrap                ] jvm uses the client vm, make sure to run `java` with the server vm for best performance by adding `-server` to the command line
[2018-01-22 10:55:56,073][INFO ][node                     ] [Ariel] version[1.7.3], pid[1126], build[NA/NA]
[2018-01-22 10:55:56,074][INFO ][node                     ] [Ariel] initializing ...
[2018-01-22 10:55:56,521][INFO ][plugins                  ] [Ariel] loaded [], sites []
[2018-01-22 10:55:56,638][INFO ][env                      ] [Ariel] using [1] data paths, mounts [[/ (/dev/mmcblk0p2)]], net usable_space 
[54.4gb], net total_space [57.2gb], types [ext4]
[2018-01-22 10:56:01,853][INFO ][node                     ] [Ariel] initialized
[2018-01-22 10:56:01,854][INFO ][node                     ] [Ariel] starting ...
[2018-01-22 10:56:02,080][INFO ][transport                ] [Ariel] bound_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish_address {inet[/192.168.0.103:9300]}
[2018-01-22 10:56:02,125][INFO ][discovery                ] [Ariel] elasticsearch/FtFOljAORnevIAOAFabptg
[2018-01-22 10:56:05,933][INFO ][cluster.service          ] [Ariel] new_master [Ariel][FtFOljAORnevIAOAFabptg][lego]
[inet[/192.168.0.103:9300]], reason: zen-disco-join (elected_as_master)
[2018-01-22 10:56:05,987][INFO ][http                     ] [Ariel] bound_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish_address {inet[/192.168.0.103:9200]}
[2018-01-22 10:56:05,988][INFO ][node                     ] [Ariel] started
[2018-01-22 10:56:06,014][INFO ][gateway                  ] [Ariel] 
recovered [0] indices into cluster_state

我错过了什么重要的一步？我在这里跟踪了所有内容：https://www.elastic.co/guide/en/elasticsearch/reference/current/deb.html

编辑：我尝试在START_DAEMON=true中设置/etc/default/elasticsearch，其中确实非常重要，但这也没有做到。深入研究/etc/default/elasticsearch中设置的值，我发现了问题。有关整体解决方案的完整细分，请参阅我的最终答案。

Answer 1

正如@Suaro所述：我们的问题与第一个链接中this question with nearly identical symptoms和this thread that reiterates the START_DAEMON solution中讨论的问题有关。这是一个良好的开端，但对我来说，并没有提供全面的解决方案。我更深入地研究了权限，堆大小和所有权，以找到最终的解决方案。

截至2018年1月，这些是根据Elasticsearch debian installation instructions安装的Ubuntu 16.04上的Elasticsearch 6的步骤：

在START_DAEMON=true中设置/etc/default/elasticsearch并重新启动服务。
如果系统有2GB的RAM（在我的情况下是真的），请设置ES_HEAP_SIZE=1g
检查/usr/share/elasticsearch中elasticsearch目录的权限。有可能root拥有这些，不理想。 如果您还不知道，以root身份运行任何服务会使您的基础架构暴露给攻击者。
＃3中的诱惑是设置ES_USER=root和ES_GROUP=root来解决您的问题。 Elasticsearch将作为一项服务启动（即使他们的产品文档声称ES不会以root运行）。 不要那样做。
相反，检查elasticsearch用户是否存在于本地，以及同名的组是否也存在。
```
$ cut -d: -f1 /etc/passwd
$ cut -d: -f1 /etc/group
```

然后，将所有elasticsearch文件夹和资源的所有权更改为elasticsearch用户和组。

$ ~ $ > ll /usr/share/elasticsearch/
total 8.0K
drwxr-xr-x 2 elasticsearch 4.0K Jan 22 10:02 bin/
lrwxrwxrwx 1 elasticsearch   18 Dec 24  2015 config -> /etc/elasticsearch/
lrwxrwxrwx 1 elasticsearch   22 Dec 24  2015 data -> /var/lib/elasticsearch/
lrwxrwxrwx 1 elasticsearch   22 Dec 24  2015 logs -> /var/log/elasticsearch/
drwxr-xr-x 2 elasticsearch 4.0K Dec 24  2015 plugins/

# ^-- Take note that the symlinked directories need to be adjusted too

$ sudo chown -R elasticsearch:elasticsearch /usr/share/elasticsearch
$ sudo chown -R elasticsearch:elasticsearch /etc/elasticsearch/
$ sudo chown -R elasticsearch:elasticsearch /var/lib/elasticsearch/
$ sudo chown -R elasticsearch:elasticsearch /var/log/elasticsearch/

然后，在ES_USER=elasticsearch中设置值ES_GROUP=elasticsearch和/etc/default/elasticsearch，如果它们没有按照这种方式设置（如果您按照＃4的情况放弃了诱惑）。

再试一次......

~ $ > sudo service elasticsearch status
● elasticsearch.service - LSB: Starts elasticsearch
   Loaded: loaded (/etc/init.d/elasticsearch; bad; vendor preset: enabled)
   Active: active (exited) since Mon 2018-01-22 20:51:29 UTC; 2min 25s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 3133 ExecStop=/etc/init.d/elasticsearch stop (code=exited, status=0/SUCCESS)
  Process: 3209 ExecStart=/etc/init.d/elasticsearch start (code=exited, status=0/SUCCESS)

~ $ > sudo systemctl restart elasticsearch.service

~ $ > sudo service elasticsearch status
● elasticsearch.service - LSB: Starts elasticsearch
   Loaded: loaded (/etc/init.d/elasticsearch; bad; vendor preset: enabled)
   Active: active (running) since Mon 2018-01-22 20:54:05 UTC; 2s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 3306 ExecStop=/etc/init.d/elasticsearch stop (code=exited, status=0/SUCCESS)
  Process: 3340 ExecStart=/etc/init.d/elasticsearch start (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/elasticsearch.service
           └─3391 /usr/lib/jvm/java-8-openjdk-armhf/bin/java -Xms1g -Xmx1g -Djava.awt.headless=true -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly -XX:+HeapDumpOnOutOfMemoryError -XX:+DisableExplicitGC -Dfile.encoding=UTF-8 -Delasticsearch -Des.pidfil

Jan 22 20:54:04 lego systemd[1]: Starting LSB: Starts elasticsearch...
Jan 22 20:54:05 lego elasticsearch[3340]:  * Starting Elasticsearch Server
Jan 22 20:54:05 lego elasticsearch[3340]:    ...done.
Jan 22 20:54:05 lego systemd[1]: Started LSB: Starts elasticsearch.
Jan 22 20:51:29 lego systemd[1]: Starting LSB: Starts elasticsearch...

EtViolà！

~ $ > curl -XGET 'localhost:9200/?pretty'
{
  "status" : 200,
  "name" : "Svarog",
  "cluster_name" : "elasticsearch",
  "version" : {
    "number" : "1.7.3",
    "build_hash" : "NA",
    "build_timestamp" : "NA",
    "build_snapshot" : false,
    "lucene_version" : "4.10.4"
  },
  "tagline" : "You Know, for Search"
}

Answer 2

可能您的问题与此问题中讨论的内容有关。

Can not start elasticsearch as a service in ubuntu 16.04

和

https://discuss.elastic.co/t/cant-start-elasticsearch-with-ubuntu-16-04/48730/9

如果是这种情况，您必须在/ etc / default / elasticsearch中将START_DAEMON更改为true并重新启动服务。

为什么Elasticsearch手动启动但不是作为Ubuntu 16.04上的服务启动？

2 个答案: