I have this error on clearml-elastic when I launch the docker-compose
learml-elastic | {"@timestamp":"2025-06-23T15:58:38.987Z", "log.level":"ERROR", "message":"fatal exception while booting Elasticsearch", "ecs.version": "1.2.0","service.name":"ES_ECS","event.dataset":"elasticsearch.server","process.thread.name":"main","log.logger":"org.elasticsearch.bootstrap.Elasticsearch","elasticsearch.node.name":"clearml","elasticsearch.cluster.name":"clearml","error.type":"java.lang.IllegalStateException","error.message":"failed to obtain node locks, tried [/usr/share/elasticsearch/data]; maybe these locations are not writable or multiple nodes were started on the same data path?","error.stack_trace":"java.lang.IllegalStateException: failed to obtain node locks, tried [/usr/share/elasticsearch/data]; maybe these locations are not writable or multiple nodes were started on the same data path?\n\tat org.elasticsearch.server@8.17.0/org.elasticsearch.env.NodeEnvironment.<init>(NodeEnvironment.java:294)\n\tat org.elasticsearch.server@8.17.0/org.elasticsearch.node.NodeConstruction.validateSettings(NodeConstruction.java:536)\n\tat org.elasticsearch.server@8.17.0/org.elasticsearch.node.NodeConstruction.prepareConstruction(NodeConstruction.java:280)\n\tat org.elasticsearch.server@8.17.0/org.elasticsearch.node.Node.<init>(Node.java:200)\n\tat org.elasticsearch.server@8.17.0/org.elasticsearch.bootstrap.Elasticsearch$2.<init>(Elasticsearch.java:247)\n\tat org.elasticsearch.server@8.17.0/org.elasticsearch.bootstrap.Elasticsearch.initPhase3(Elasticsearch.java:247)\n\tat org.elasticsearch.server@8.17.0/org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:76)\nCaused by: java.io.IOException: failed to obtain lock on /usr/share/elasticsearch/data\n\tat org.elasticsearch.server@8.17.0/org.elasticsearch.env.NodeEnvironment$NodeLock.<init>(NodeEnvironment.java:239)\n\tat org.elasticsearch.server@8.17.0/org.elasticsearch.env.NodeEnvironment$NodeLock.<init>(NodeEnvironment.java:207)\n\tat org.elasticsearch.server@8.17.0/org.elasticsearch.env.NodeEnvironment.<init>(NodeEnvironment.java:286)\n\t... 6 more\nCaused by: java.nio.file.NoSuchFileException:
When I press f 12 I have those errors:
Failed to load resource: the server responded with a status of 404 (Not Found)Understand this error
:8080/api/v999.0/server.report_stats_option:1
Failed to load resource: the server responded with a status of 404 (Not Found)Understand this error
core.mjs:6686 ERROR ie
handleError @ core.mjs:6686Understand this error
:8080/api/v999.0/users.get_current_user:1
Failed to load resource: the server responded with a status of 404 (Not Found)Understand this error
:8080/api/v999.0/users.get_preferences:1
Failed to load resource: the server responded with a status of 404 (Not Found)Understand this error
:8080/api/v999.0/server.info:1
Failed to load resource: the server responded with a status of 404 (Not Found)Understand this error
:8080/api/v999.0/users.set_preferences:1
Failed to load resource: the server responded with a status of 404 (Not Found)Understand this error
core.mjs:6686 ERROR ie
handleError @ core.mjs:6686Understand this error
zotero.js:338 Could not establish connection. Receiving end does not exist. at None
logError @ zotero.js:338Understand this error
inject.js:92 Uncaught (in promise) ObjectUnderstand this error
:8080/api/v999.0/users.set_preferences:1
Failed to load resource: the server responded with a status of 404 (Not Found)Understand this error
core.mjs:6686 ERROR ie
handleError @ core.mjs:6686Understand this error
the output of the logs ( command docker-compose -f /opt/clearml/docker-compose.yml ) are :
Are you seeing any errors in the developer tools (F12) console?
It looks that ES is unable to write to the volume that you provided.
Did you provide access to the folder where ES is trying to write? On what OS are you running the server?
Thats strange, you don't have a create new credentials button?
Hi @<1638349756755349504:profile|MistakenTurtle88> , it simply looks like a new server without any data registered to it yet
In some case people have the same mistake:
Sometimes when you reload your server or when you are developping, the error can come from the browser cookies and not directly the server, my server started right but I restarted it and nothing appeared on my browser, switching to another browser fixed the issue
shouldn't we have a clearml interface like the one on the website ?
Like my connect configuration on clearml look like this 😞