Elasticsearch: ES not able to start

Created on 17 Oct 2017  Â·  10Comments  Â·  Source: elastic/elasticsearch

][WARN ][o.e.b.ElasticsearchUncaughtExceptionHandler] [********] uncaught exception in thread [main]
org.elasticsearch.bootstrap.StartupException: java.lang.NullPointerException
        at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:136) ~[elasticsearch-5.6.3.jar:5.6.3]
        at org.elasticsearch.bootstrap.Elasticsearch.execute(Elasticsearch.java:123) ~[elasticsearch-5.6.3.jar:5.6.3]
        at org.elasticsearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:70) ~[elasticsearch-5.6.3.jar:5.6.3]
        at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:134) ~[elasticsearch-5.6.3.jar:5.6.3]
        at org.elasticsearch.cli.Command.main(Command.java:90) ~[elasticsearch-5.6.3.jar:5.6.3]
        at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:91) ~[elasticsearch-5.6.3.jar:5.6.3]
        at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:84) ~[elasticsearch-5.6.3.jar:5.6.3]
Caused by: java.lang.NullPointerException
        at sun.nio.fs.UnixFileSystem.getPath(UnixFileSystem.java:273) ~[?:?]
        at org.elasticsearch.common.io.PathUtils.get(PathUtils.java:60) ~[elasticsearch-5.6.3.jar:5.6.3]
        at org.elasticsearch.monitor.os.OsProbe.readSysFsCgroupCpuAcctCpuAcctUsage(OsProbe.java:274) ~[elasticsearch-5.6.3.jar:5.6.3]
        at org.elasticsearch.monitor.os.OsProbe.getCgroupCpuAcctUsageNanos(OsProbe.java:261) ~[elasticsearch-5.6.3.jar:5.6.3]
        at org.elasticsearch.monitor.os.OsProbe.getCgroup(OsProbe.java:419) ~[elasticsearch-5.6.3.jar:5.6.3]
        at org.elasticsearch.monitor.os.OsProbe.osStats(OsProbe.java:464) ~[elasticsearch-5.6.3.jar:5.6.3]
        at org.elasticsearch.monitor.os.OsService.<init>(OsService.java:45) ~[elasticsearch-5.6.3.jar:5.6.3]
        at org.elasticsearch.monitor.MonitorService.<init>(MonitorService.java:45) ~[elasticsearch-5.6.3.jar:5.6.3]
        at org.elasticsearch.node.Node.<init>(Node.java:362) ~[elasticsearch-5.6.3.jar:5.6.3]
        at org.elasticsearch.node.Node.<init>(Node.java:245) ~[elasticsearch-5.6.3.jar:5.6.3]
        at org.elasticsearch.bootstrap.Bootstrap$5.<init>(Bootstrap.java:233) ~[elasticsearch-5.6.3.jar:5.6.3]
        at org.elasticsearch.bootstrap.Bootstrap.setup(Bootstrap.java:233) ~[elasticsearch-5.6.3.jar:5.6.3]
        at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:342) ~[elasticsearch-5.6.3.jar:5.6.3]
        at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:132) ~[elasticsearch-5.6.3.jar:5.6.3]
:CorInfrCore

Most helpful comment

I’ll take this one @dadoonet, it’s a problem with the cgroups on the system for this user.

All 10 comments

Java version
openjdk version "1.8.0_144"
OpenJDK Runtime Environment (build 1.8.0_144-b01)
OpenJDK 64-Bit Server VM (build 25.144-b01, mixed mode)

Did you change any settings? What are they? How are you launching elasticsearch? How did you install it?

I’ll take this one @dadoonet, it’s a problem with the cgroups on the system for this user.

What exactly cgroup means?

On Oct 17, 2017 2:47 PM, "Jason Tedor" notifications@github.com wrote:

I’ll take this one @dadoonet https://github.com/dadoonet, it’s a
problem with the cgroups on the system for this user.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/elastic/elasticsearch/issues/27031#issuecomment-337169679,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AVi94rusggqJn-Ymh6lFjxCKCiRDe6V1ks5stHCTgaJpZM4P7vy8
.

Is this Linux parameters?

On Oct 17, 2017 2:47 PM, "Jason Tedor" notifications@github.com wrote:

I’ll take this one @dadoonet https://github.com/dadoonet, it’s a
problem with the cgroups on the system for this user.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/elastic/elasticsearch/issues/27031#issuecomment-337169679,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AVi94rusggqJn-Ymh6lFjxCKCiRDe6V1ks5stHCTgaJpZM4P7vy8
.

How can we fix cgroup issue?

On Oct 17, 2017 2:47 PM, "Jason Tedor" notifications@github.com wrote:

I’ll take this one @dadoonet https://github.com/dadoonet, it’s a
problem with the cgroups on the system for this user.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/elastic/elasticsearch/issues/27031#issuecomment-337169679,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AVi94rusggqJn-Ymh6lFjxCKCiRDe6V1ks5stHCTgaJpZM4P7vy8
.

There seems to be an issue while accessing a path on file system which seems to be getting returned as NULL. Did you check to make sure all paths used are accessible?

Caused by: java.lang.NullPointerException
at sun.nio.fs.UnixFileSystem.getPath(UnixFileSystem.java:273) ~[?:?]
at org.elasticsearch.common.io.PathUtils.get(PathUtils.java:60)

@hello4usharath
Did you find a solution? I have currently the same problem.

Ok, find a solution (https://discuss.elastic.co/t/why-elasticsearch-5-2-0-throw-nullpointerexception-when-start/74739/12).
sudo mount -t cgroup -o rw,nosuid,nodev,noexec,relatime,cpu,cpuacct cgroup /sys/fs/cgroup/cpu,cpuacct
Thanks to @jasontedor

Closing as this is due to a cgroup configuration issue.

Was this page helpful?
0 / 5 - 0 ratings