Elasticsearch cannot be started after an upgrade: Temporary file directory [${ES_TMPDIR}] does not exist or is not accessible

Elastic Stack Elasticsearch
1

Hi all,

I am trying to upgrade my Elasticsearch cluster from 7.4.0 to 7.5.2. It is running on CentOS 7 with Java 1.8.0. I used the rpm files from https://www.elastic.co/downloads/elasticsearch. I successfully upgraded the first node, but now I am having some issues with the second one. I would be grateful for help.

Steps to reproduce :

  1. sudo rpm -Uvh elasticsearch-7.5.2-x86_64.rpm
  2. systemctl daemon-reload
  3. sudo systemctl start elasticsearch.service

Service cannot be started, see the logs below.

Provide logs (if relevant) :

 -- Unit elasticsearch.service has begun starting up.
 Feb 04 16:01:59 xxx-server-3 elasticsearch[129216]: OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future rele
 Feb 04 16:02:00 xxx-server-3 elasticsearch[129216]: ERROR: Temporary file directory [${ES_TMPDIR}] does not exist or is not accessible
 Feb 04 16:02:00 xxx-server-3 systemd[1]: elasticsearch.service: main process exited, code=exited, status=78/n/a
 Feb 04 16:02:00 xxx-server-3 systemd[1]: Failed to start Elasticsearch.
 -- Subject: Unit elasticsearch.service has failed
 -- Defined-By: systemd
 -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
 --
 -- Unit elasticsearch.service has failed.
 --
 -- The result is failed.
 Feb 04 16:02:00 xxx-server-3 systemd[1]: Unit elasticsearch.service entered failed state.
 Feb 04 16:02:00 xxx-server-3 systemd[1]: elasticsearch.service failed.
2

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