Elasticsearch upgrade 5.3 to 5.5.2 failing to restart

Elastic Stack Elasticsearch
1

Hi,

I am currently upgrading Elasticsearch from 5.3.0 to 5.5.2 and doing it as rolling upgrade on a server with Debian Linux.

After updating /bin, /lib and /modules directories for Elasticsearch, the elasticsearch service is failing to restart and I am getting the following messages

alessandro@apollo-elk-server-staging:/var/lib/elk/elk-config/elasticsearch$ sudo service elasticsearch restart
alessandro@apollo-elk-server-staging:/var/lib/elk/elk-config/elasticsearch$ sudo service elasticsearch status
● elasticsearch.service - Elasticsearch
Loaded: loaded (/etc/systemd/system/elasticsearch.service; enabled)
Active: active (running) since Mon 2017-09-04 09:17:28 UTC; 1s ago
Main PID: 14608 (java)
CGroup: /system.slice/elasticsearch.service
└─14608 /usr/bin/java -Xms4g -Xmx4g -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly -XX:+Dis...
Sep 04 09:17:28 apollo-elk-server-staging systemd[1]: Started Elasticsearch.
Sep 04 09:17:28 apollo-elk-server-staging elasticsearch[14608]: Java HotSpot(TM) 64-Bit Server VM warning: Insufficient space for shared memory file:
Sep 04 09:17:28 apollo-elk-server-staging elasticsearch[14608]: 14619
Sep 04 09:17:28 apollo-elk-server-staging elasticsearch[14608]: Try using the -Djava.io.tmpdir= option to select an alternate temp location.
Sep 04 09:17:28 apollo-elk-server-staging elasticsearch[14608]: Java HotSpot(TM) 64-Bit Server VM warning: Insufficient space for shared memory file:
Sep 04 09:17:28 apollo-elk-server-staging elasticsearch[14608]: 14608
Sep 04 09:17:28 apollo-elk-server-staging elasticsearch[14608]: Try using the -Djava.io.tmpdir= option to select an alternate temp location.
alessandro@apollo-elk-server-staging:/var/lib/elk/elk-config/elasticsearch$ sudo service elasticsearch status
● elasticsearch.service - Elasticsearch
Loaded: loaded (/etc/systemd/system/elasticsearch.service; enabled)
Active: activating (auto-restart) (Result: exit-code) since Mon 2017-09-04 09:18:39 UTC; 9s ago
Process: 14786 ExecStart=/var/lib/elk/elk-config/elasticsearch/bin/elasticsearch (code=exited, status=1/FAILURE)
Main PID: 14786 (code=exited, status=1/FAILURE)

I see there is an issue with the temp directory for the JVM but I don know how to solve it.
Does anybody know how I can solve this issue?

Thanks in advance, Alessandro

2

Solved,

basically the disk was nearly full and Elasticsearch didn't have enough space for a restart and I simply had to create some space.

3

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