ElasticSearch service stopped by Java update

[webbouk]

We had an issue this evening where a server was restarted but the ElasticSearch service wouldn't re-start automatically.

The tech guys had a look into it and it turns out that a Java update on the server had prevented ES from restarting, here are their findings...

---

It seems Java may have automatically updated on the server as ElasticSearch was producing the following error:

"C:\elastic\logs\elasticsearch-service-x64.2020-11-08.log"

[2020-11-08 19:04:34] [error] [ 7116] Failed creating Java C:\Program Files\Java\jre1.8.0_221\bin\server\jvm.dll
[2020-11-08 19:04:34] [error] [ 7116] The system cannot find the path specified.
[2020-11-08 19:04:34] [error] [ 7116] ServiceStart returned 1
[2020-11-08 19:04:34] [error] [ 7116] The system cannot find the path specified.
[2020-11-08 19:04:34] [info] [ 7092] Run service finished.
[2020-11-08 19:04:34] [info] [ 7092] Commons Daemon procrun finished

Checking the current Java variables the below location is returned:

C:\Users\host.support>echo %JAVA_HOME%
C:\Program Files\Java\jre1.8.0_221

I have checked the filesystem manually and a later version of Java has been installed:
C:\Program Files\Java\jre1.8.0_271

I have updated the associated Java variables and the ElasticSearch service has now started.

---

This isn't the first time it has happened, it seems that whenever Java updates it causes an issue with ES.

Has anyone else found this, and is there anything that can be done to prevent it from reoccurring?

 

[Mouth]

is there anything that can be done to prevent it from reoccurring?

Prevent java from auto-updating would be the logical action?