Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to start Elasticsearch #21796

Closed
ghost opened this issue Nov 25, 2016 · 3 comments
Closed

Unable to start Elasticsearch #21796

ghost opened this issue Nov 25, 2016 · 3 comments
Labels
:Delivery/Packaging RPM and deb packaging, tar and zip archives, shell and batch scripts feedback_needed

Comments

@ghost
Copy link

ghost commented Nov 25, 2016

Elasticsearch version: 5.0

JVM version: openjdk version "1.8.0_111"

OS version: Amazon Linux AMI release 2014.03

I am using AWS m3.large instance. I have two elasticsearch nodes. For my data node(node-2) , When I started elasticsearch service with sudo service elasticsearch start


[2016-11-25T09:31:56,884][INFO ][o.e.b.BootstrapCheck     ] [node-2] bound or publishing to a non-loopback or non-link-local address, enforcing bootstrap checks
[2016-11-25T09:31:56,886][ERROR][o.e.b.Bootstrap          ] [node-2] node validation exception
bootstrap checks failed
max number of threads [1024] for user [elasticsearch] is too low, increase to at least [2048]

Then I edited file /usr/lib/systemd/system/elasticsearch.service and added line LimitNPROC=2048.

When I restarted service. I checked status: sudo service elasticsearch status
It returned ,
elasticsearch dead but subsys locked
In Log

[2016-11-25T09:50:32,138][INFO ][o.e.b.BootstrapCheck     ] [node-2] bound or publishing to a non-loopback or non-link-local address, enforcing bootstrap checks
[2016-11-25T09:50:32,140][ERROR][o.e.b.Bootstrap          ] [node-2] node validation exception
bootstrap checks failed
max number of threads [1024] for user [elasticsearch] is too low, increase to at least [2048]

Am I missing something ?

@clintongormley
Copy link
Contributor

As far as I know, Amazon Linux AMI isn't using systemd, so you should be setting the nproc limit with ulimit or by configuring limits.conf

@clintongormley clintongormley added :Delivery/Packaging RPM and deb packaging, tar and zip archives, shell and batch scripts feedback_needed labels Nov 25, 2016
@ghost
Copy link
Author

ghost commented Nov 26, 2016

@clintongormley Thank you for response. I tried troubleshooting as you recommended. Got following things.
ulimit -u command returns:

[root@ip-address-subsys]# ulimit -u
2048

/etc/security/limits.conf

<domain>      <type>  <item>         <value>
#

#*               soft    core            0
#*               hard    rss             10000
#@student        hard    nproc           20
#@faculty        soft    nproc           20
#@faculty        hard    nproc           50
#ftp             hard    nproc           0
#@student        -       maxlogins       4
elasticsearch    hard    nproc           2048

@ghost
Copy link
Author

ghost commented Nov 28, 2016

I updated my Amazon Linux instance from 2014.03 to 2016.09. It worked for me. As I said it was running Amazon Linux 2014.03 previously.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Delivery/Packaging RPM and deb packaging, tar and zip archives, shell and batch scripts feedback_needed
Projects
None yet
Development

No branches or pull requests

2 participants