Elasticsearch not starting in Docker Environment after update

Technical assistance
1

Hi,

I have installed and configured Zammad in an Docker environment with Portainer stack.

The initial installed Version was 6.5.0.

Last Week I updated Zammad to 6.5.1 documented here: Updating Zammad — Zammad System Documentation documentation at the Docker Tab.

At this time, elasticsearch does not start.

At the console, I get the following error Message:

fatal exception while booting Elasticsearch | @timestamp=2025-08-26T15:09:48.748Z log.level=ERROR 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=23e85dba623a elasticsearch.cluster.name=docker-cluster 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?
	at org.elasticsearch.server@8.19.2/org.elasticsearch.env.NodeEnvironment.<init>(NodeEnvironment.java:294)
	at org.elasticsearch.server@8.19.2/org.elasticsearch.node.NodeConstruction.validateSettings(NodeConstruction.java:513)
	at org.elasticsearch.server@8.19.2/org.elasticsearch.node.NodeConstruction.prepareConstruction(NodeConstruction.java:281)
	at org.elasticsearch.server@8.19.2/org.elasticsearch.node.Node.<init>(Node.java:201)
	at org.elasticsearch.server@8.19.2/org.elasticsearch.bootstrap.Elasticsearch$1.<init>(Elasticsearch.java:402)
	at org.elasticsearch.server@8.19.2/org.elasticsearch.bootstrap.Elasticsearch.initPhase3(Elasticsearch.java:402)
	at org.elasticsearch.server@8.19.2/org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:99)
Caused by: java.io.IOException: failed to obtain lock on /usr/share/elasticsearch/data
	at org.elasticsearch.server@8.19.2/org.elasticsearch.env.NodeEnvironment$NodeLock.<init>(NodeEnvironment.java:239)
	at org.elasticsearch.server@8.19.2/org.elasticsearch.env.NodeEnvironment$NodeLock.<init>(NodeEnvironment.java:207)
	at org.elasticsearch.server@8.19.2/org.elasticsearch.env.NodeEnvironment.<init>(NodeEnvironment.java:286)
	... 6 more
Caused by: java.nio.file.AccessDeniedException: /usr/share/elasticsearch/data/node.lock
	at java.base/sun.nio.fs.UnixException.translateToIOException(UnixException.java:90)
	at java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:106)
	at java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:111)
	at java.base/sun.nio.fs.UnixFileSystemProvider.newFileChannel(UnixFileSystemProvider.java:213)
	at java.base/java.nio.channels.FileChannel.open(FileChannel.java:301)
	at java.base/java.nio.channels.FileChannel.open(FileChannel.java:353)
	at org.apache.lucene.core@9.12.2/org.apache.lucene.store.NativeFSLockFactory.obtainFSLock(NativeFSLockFactory.java:112)
	at org.apache.lucene.core@9.12.2/org.apache.lucene.store.FSLockFactory.obtainLock(FSLockFactory.java:43)
	at org.apache.lucene.core@9.12.2/org.apache.lucene.store.BaseDirectory.obtainLock(BaseDirectory.java:44)
	at org.elasticsearch.server@8.19.2/org.elasticsearch.env.NodeEnvironment$NodeLock.<init>(NodeEnvironment.java:232)
	... 8 more

ERROR: Elasticsearch did not exit normally - check the logs at /usr/share/elasticsearch/logs/docker-cluster.log

ERROR: Elasticsearch died while starting up, with exit code 1

I have checked, if there is another Service running. I also have rebooted the Host Machine and have tried to pull the stack again.

2

Solved by myself:

I have set the Permissions to the Volume:

sudo chown -R 1000:1000 /var/lib/docker/volumes/zammad_elasticsearch-data/_data/
sudo chmod -R 775 /var/lib/docker/volumes/zammad_elasticsearch-data/_data/
1 Like
3

Hi Bjoern,

nice to see, that you’ve solved it yourself. And thank you a ton for sharing that solution with others! For future reference and maybe others that stumble upon the same problem:

1 Like
4

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