Skip to main content

ElasticSearch–Failed to run ElasticSearch 7.6.1 after upgrade

After upgrading ElasticSearch to 7.6.1, it failed to start when I tried to run ElasticSearch as a windows service.

In the logs I found the following error message:

[2020-03-30 10:04:11] [info]  [ 4516] Service 'elasticsearch-service-x64' installed

[2020-03-30 10:04:11] [info]  [ 4516] Commons Daemon procrun finished

[2020-03-30 10:04:23] [info]  [ 4336] Commons Daemon procrun (1.1.0.0 64-bit) started

[2020-03-30 10:04:23] [info]  [ 4336] Running 'elasticsearch-service-x64' Service...

[2020-03-30 10:04:23] [info]  [ 4992] Starting service...

[2020-03-30 10:04:23] [error] [ 2432] CreateJavaVM Failed

[2020-03-30 10:04:23] [error] [ 2432] The system cannot find the file specified.

[2020-03-30 10:04:23] [error] [ 4992] Failed to start Java

[2020-03-30 10:04:23] [error] [ 4992] ServiceStart returned 4

[2020-03-30 10:04:23] [info]  [ 4336] Run service finished.

[2020-03-30 10:04:23] [info]  [ 4336] Commons Daemon procrun finished

The problem is that ElasticSearch tries to pass on a ‘-server’ option which is no longer supported in the latest JAVA versions.

To fix I had to change the Java Options:

  • Install the windows service through ‘elasticsearch-service install’
  • Open the ElasticSearch service manager through ‘elasticsearch-service manager’
  • Go to the Java tab and remove the ‘-server’ flag from the Java Options

  • Start the service

Popular posts from this blog

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...