Skip to main content

ElasticSearch–Uninstall failed on Windows

Yesterday I shared how I got into trouble when trying to uninstall an ElasticSearch instance. I explained how we could investigate the issue and find the root cause by checking the log files. Today I want to continue by explaining what I found in the log files and how I solved the problem.

While browsing through the log file, I noticed the following error message:

Calling custom action Elastic.Installer.Msi!Elastic.Installer.Msi.Elasticsearch.CustomActions.Immediate.ElasticsearchExistingDirectoriesAction.ElasticsearchExistingDirectories

System.Exception: Can not execute Elastic.InstallerHosts.Elasticsearch.Tasks.Install.ExistingDirectoriesTask the model that it was passed has the following errors

BADELASTICSEARCHYAMLFILE: The elasticsearch.yml file we found in ES_PATH_CONF appears to be invalid  and prevented seeding current values.

It seems that ElasticSearch checks the elasticsearch.yml configuration file during the uninstall and doesn’t like what it finds there(which seems quite strange as the ElasticSearch instance was happily running with this configuration). Anyway, let’s have a look at this elasticsearch.yml file:

Most information in there are default settings, the only thing I added extra was the following line:

cluster.initial_master_nodes: node-1

So let’s remove this line and see if that helps.  Here is the updated elasticsearch.yml file:

And indeed when I now tried to uninstall ElasticSearch, it worked!. Problem solved…

Popular posts from this blog

XUnit - Assert.Collection

A colleague asked me to take a look at the following code inside a test project: My first guess would be that this code checks that the specified condition(the contains) is true for every element in the list.  This turns out not to be the case. The Assert.Collection expects a list of element inspectors, one for every item in the list. The first inspector is used to check the first item, the second inspector the second item and so on. The number of inspectors should match the number of elements in the list. An example: The behavior I expected could be achieved using the Assert.All method:

Angular --deploy-url and --base-href

As long you are running your Angular application at a root URL (e.g. ) you don’t need to worry that much about either the ‘--deploy-url’ and ‘--base-href’ parameters. But once you want to serve your Angular application from a server sub folder(e.g. ) these parameters become important. --base-href If you deploy your Angular app to a subfolder, the ‘--base-href’ is important to generate the correct routes. This parameter will update the <base href> tag inside the index.html. For example, if the index.html is on the server at /angularapp/index.html , the base href should be set to <base href="/angularapp/"> . More information: --deploy-url A second parameter that is important is ‘--deploy-url’. This parameter will update the generated url’s for our assets(scripts, css) inside the index.html. To make your assets available at /angularapp/, the deploy url should

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.