a

    acoustic-printer-83045

    1 year ago
    👋 Just wondering if anyone else is experiencing an elasticsearch failure when running
    ./docker/quickstart.sh
    When I try to fire up elasticsearch I get this (snipped) log:
    elasticsearch             | {"type": "server", "timestamp": "2021-03-21T22:25:21,301Z", "level": "ERROR", "component": "o.e.b.ElasticsearchUncaughtExceptionHandler", "cluster.name": "docker-cluster", "node.name": "elasticsearch", "message": "uncaught exception in thread [main]", 
    elasticsearch             | "stacktrace": ["org.elasticsearch.bootstrap.StartupException: java.lang.IllegalStateException: failed to obtain node locks, tried [[/usr/share/elasticsearch/data]] with lock id [0]; maybe these locations are not writable or multiple nodes were started without increasing [node.max_local_storage_nodes] (was [1])?",
    elasticsearch             | "at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:174) ~[elasticsearch-7.9.3.jar:7.9.3]",
    elasticsearch             | "at org.elasticsearch.bootstrap.Elasticsearch.execute(Elasticsearch.java:161) ~[elasticsearch-7.9.3.jar:7.9.3]",
    elasticsearch             | "at org.elasticsearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:86) ~[elasticsearch-7.9.3.jar:7.9.3]",
    elasticsearch             | "at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:127) ~[elasticsearch-cli-7.9.3.jar:7.9.3]",
    elasticsearch             | "at org.elasticsearch.cli.Command.main(Command.java:90) ~[elasticsearch-cli-7.9.3.jar:7.9.3]",
    elasticsearch             | "at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:126) ~[elasticsearch-7.9.3.jar:7.9.3]",
    elasticsearch             | "at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:92) ~[elasticsearch-7.9.3.jar:7.9.3]",
    elasticsearch             | "Caused by: java.lang.IllegalStateException: failed to obtain node locks, tried [[/usr/share/elasticsearch/data]] with lock id [0]; maybe these locations are not writable or multiple nodes were started without increasing [node.max_local_storage_nodes] (was [1])?",
    I don't think this is caused by resource contention but I could be wrong. Thanks!
    m

    mammoth-bear-12532

    1 year ago
    @acoustic-printer-83045 : could this be because of the recent elasticsearch upgrade from 5.x to 7.x?
    a

    acoustic-printer-83045

    1 year ago
    That was it, thanks. Ran the
    nuke.sh
    script and it worked fine after that.