Elasticsearch on a single node docker container after mounting azure storage gives .es_temp_file file not found error

Hi. I am running elasticsearch as single node. While starting the container it gives

.es_temp_file not found error. Tried mounting blobfuse2 but didnot help.

{"type": "server", "timestamp": "2023-08-05T08:53:25,540Z", "level": "ERROR", "component": "o.e.m.f.FsHealthService", "cluster.name": "elastic-cluster", "node.name": "my-node", "message": "health check of [/usr/share/elasticsearch/data/nodes/0] failed", "cluster.uuid": "Ook2u1TCQiG-u0x0m584tw", "node.id": "Pl-caT0yQH2e4taVUYAWDA" ,
"stacktrace": ["java.nio.file.NoSuchFileException: /usr/share/elasticsearch/data/nodes/0/.es_temp_file",
"at sun.nio.fs.UnixException.translateToIOException(UnixException.java:92) ~[?:?]",
"at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:106) ~[?:?]",
"at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:111) ~[?:?]",
"at sun.nio.fs.UnixFileSystemProvider.implDelete(UnixFileSystemProvider.java:248) ~[?:?]",
"at sun.nio.fs.AbstractFileSystemProvider.delete(AbstractFileSystemProvider.java:105) ~[?:?]",
"at java.nio.file.Files.delete(Files.java:1146) ~[?:?]",
"at org.elasticsearch.monitor.fs.FsHealthService$FsHealthMonitor.monitorFSHealth(FsHealthService.java:175) [elasticsearch-7.10.2.jar:7.10.2]",
"at org.elasticsearch.monitor.fs.FsHealthService$FsHealthMonitor.run(FsHealthService.java:146) [elasticsearch-7.10.2.jar:7.10.2]",
"at org.elasticsearch.threadpool.Scheduler$ReschedulingRunnable.doRun(Scheduler.java:213) [elasticsearch-7.10.2.jar:7.10.2]",
"at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingAbstractRunnable.doRun(ThreadContext.java:743) [elasticsearch-7.10.2.jar:7.10.2]",
"at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:37) [elasticsearch-7.10.2.jar:7.10.2]",
"at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130) [?:?]",
"at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:630) [?:?]",
"at java.lang.Thread.run(Thread.java:832) [?:?]"] }

elasticsearch.yaml file conf is
cluster.name: elastic-cluster
discovery.type: single-node
node.name: "my-node"
network.host: 0.0.0.0
#bootstrap.system_call_filter: false
path.data: /usr/share/elasticsearch/data

logs: /var/log/elasticsearch

#----------------------- BEGIN SECURITY AUTO CONFIGURATION -----------------------

The following settings, TLS certificates, and keys have been automatically

generated to configure Elasticsearch security features on 22-03-2023 12:12:43

--------------------------------------------------------------------------------

Enable security features

#xpack.security.enabled: false
#xpack.security.enrollment.enabled: true

Enable encryption for HTTP API client connections, such as Kibana, Logstash, and Agents

#xpack.security.http.ssl:

enabled: false

keystore.path: certs/http.p12

Enable encryption and mutual authentication between cluster nodes

#xpack.security.transport.ssl:

enabled: true

verification_mode: certificate

keystore.path: certs/transport.p12

truststore.path: certs/transport.p12

#----------------------- END SECURITY AUTO CONFIGURATION -------------------------

Not sure about what is happening but you should definitely upgrade as your version is too old.

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