Native controller process has stopped

Elastic Stack Elasticsearch
1

I am not able to start the elasticsearch service, I am getting the following errors. I could find many discussions with the same error but didn't find solution in any of them.

Below are the logs, can anyone please provide a solution for this?

localhost:~ # systemctl status elasticsearch
● elasticsearch.service - Elasticsearch
   Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; disabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Fri 2021-09-17 17:19:54 IST; 11s ago
     Docs: https://www.elastic.co
  Process: 2374 ExecStart=/usr/share/elasticsearch/bin/systemd-entrypoint -p ${PID_DIR}/elasticsearch.pid --quiet (code=exited, status=1/FAILURE)
 Main PID: 2374 (code=exited, status=1/FAILURE)

Sep 17 17:19:54 localhost systemd-entrypoint[2374]:         at org.elasticsearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:75)
Sep 17 17:19:54 localhost systemd-entrypoint[2374]:         at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:116)
Sep 17 17:19:54 localhost systemd-entrypoint[2374]:         at org.elasticsearch.cli.Command.main(Command.java:79)
Sep 17 17:19:54 localhost systemd-entrypoint[2374]:         at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:115)
Sep 17 17:19:54 localhost systemd-entrypoint[2374]:         at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:81)
Sep 17 17:19:54 localhost systemd-entrypoint[2374]: For complete error details, refer to the log at /var/log/elasticsearch/Elastic_Search.log
Sep 17 17:19:54 localhost systemd[1]: elasticsearch.service: Main process exited, code=exited, status=1/FAILURE
Sep 17 17:19:54 localhost systemd[1]: Failed to start Elasticsearch.
Sep 17 17:19:54 localhost systemd[1]: elasticsearch.service: Unit entered failed state.
Sep 17 17:19:54 localhost systemd[1]: elasticsearch.service: Failed with result 'exit-code'.



localhost:~ # sudo tail -f /var/log/elasticsearch/Elastic_Search.log
        at org.elasticsearch.xpack.security.Security.lambda$getHttpTransports$25(Security.java:1145) ~[?:?]
        at org.elasticsearch.node.Node.newHttpTransport(Node.java:1255) ~[elasticsearch-7.14.1.jar:7.14.1]
        at org.elasticsearch.node.Node.<init>(Node.java:652) ~[elasticsearch-7.14.1.jar:7.14.1]
        at org.elasticsearch.node.Node.<init>(Node.java:281) ~[elasticsearch-7.14.1.jar:7.14.1]
        at org.elasticsearch.bootstrap.Bootstrap$5.<init>(Bootstrap.java:219) ~[elasticsearch-7.14.1.jar:7.14.1]
        at org.elasticsearch.bootstrap.Bootstrap.setup(Bootstrap.java:219) ~[elasticsearch-7.14.1.jar:7.14.1]
        at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:399) ~[elasticsearch-7.14.1.jar:7.14.1]
        at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:159) ~[elasticsearch-7.14.1.jar:7.14.1]
        ... 6 more
[2021-09-17T17:19:54,118][INFO ][o.e.x.m.p.NativeController] [node-1] Native controller process has stopped - no new native processes can be started
^C
2

I don’t think Native controller process has stopped - no new native processes can be started is the problem. That’s an info message that is getting logged because the Elasticsearch JVM is dying for some other reason.

In the last 10 lines of the log you tailed I can see the end of a stack trace. Probably that relates to the reason the JVM is dying. Look at the beginning of that stack trace and the messages immediately before it. They will probably hint at the problem that needs to be fixed.

1 Like
3

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