Database file changed error


i installed the elastic search for the first time along with kibana. everything was working fine until i switched off my pc for the day and started it the next morning. now when i try to start elasticsearch by typing .\bin\elasticsearch in my powershell i get this error

[2021-08-19T09:31:51,021][INFO ][o.e.i.g.DatabaseRegistry ] [SGNMUWQUQYOV3LL] database file changed [C:\Users\Emathew\AppData\Local\Temp\elasticsearch\geoip-databases\yihBnRgdTx-Lh0FovtFCIQ\GeoLite2-City.mmdb], reload database...

and its stuck at this point. any idea whats happening, how do i solve this issue ? i am new to this field, so please be kind


The same issue here, any clues?

Welcome to our community! :smiley:

That is an informational log, not an error.
It'd help if you shared more of your log :slight_smile:

Hi ,

Oh i see , but i was not able to start the elastic and kibana services. Anyways i was able to solve the issue, not sure if its the correct solution, but it worked for me. I just deleted the contents of the Temp folder , restarted my pc and all is well now. :slight_smile:

Im having this same issue. I just installed elastic, configured the elasticsearch.yml file and attempted to start elastic service and its stuck on the following info log:
database file changed [var/lob/elasticsearch/tmp/geoip-database/MEBd6Y11R_6yK4NK4GKwGA/GeoLite2-City.mmdb], reload database

I did exactly what acezeus did to resolve his issue but that didnt work.

Welcome to our community! :smiley:

Can you please share more of the log file you have.

Please format your code/logs/config using the </> button, or markdown style back ticks. It helps to make things easy to read which helps us help you :slight_smile:

This is weird, but I'm also setting up Elasticsearch in my kubernetes cluster and I have exactly the same log. Maybe there is a problem with GeoLite2?

{"type": "server", "timestamp": "2021-09-03T09:48:59,006Z", "level": "INFO", "component": "o.e.i.g.GeoIpDownloader", "": "elasticsearch", "": "elasticsearch-master-0", "message": "updating geoip databases"}
{"type": "server", "timestamp": "2021-09-03T09:48:59,007Z", "level": "INFO", "component": "o.e.i.g.GeoIpDownloader", "": "elasticsearch", "": "elasticsearch-master-0", "message": "fetching geoip databases overview from []"  }
{"type": "server", "timestamp": "2021-09-03T09:49:00,106Z", "level": "INFO", "component": "o.e.i.g.GeoIpDownloader", "": "elasticsearch", "": "elasticsearch-master-0", "message": "geoip database [GeoLite2-ASN.mmdb] is up to date, updated timestamp"  }
{"type": "server", "timestamp": "2021-09-03T09:49:00,500Z", "level": "INFO", "component": "o.e.i.g.GeoIpDownloader", "": "elasticsearch", "": "elasticsearch-master-0", "message": "geoip database [GeoLite2-City.mmdb] is up to date, updated timestamp"  }
{"type": "server", "timestamp": "2021-09-03T09:49:00,999Z", "level": "INFO", "component": "o.e.i.g.GeoIpDownloader", "": "elasticsearch", "": "elasticsearch-master-0", "message": "geoip database [GeoLite2-Country.mmdb] is up to date, updated timestamp" }
{"type": "server", "timestamp": "2021-09-03T09:49:01,002Z", "level": "INFO", "component": "o.e.c.r.a.AllocationService", "": "elasticsearch", "": "elasticsearch-master-0", "message": "Cluster health status changed from [RED] to [YELLOW] (reason: [shards started [[.geoip_databases][0]]])." }
{"type": "server", "timestamp": "2021-09-03T09:49:01,356Z", "level": "INFO", "component": "o.e.i.g.DatabaseRegistry", "": "elasticsearch", "": "elasticsearch-master-0", "message": "downloading geoip database [GeoLite2-Country.mmdb] to [/tmp/elasticsearch-14340479604074439324/geoip-databases/YibBtYa-R5e4OSZd5QII5g/GeoLite2-Country.mmdb.tmp.gz]" }
{"type": "server", "timestamp": "2021-09-03T09:49:01,357Z", "level": "INFO", "component": "o.e.i.g.DatabaseRegistry", "": "elasticsearch", "": "elasticsearch-master-0", "message": "downloading geoip database [GeoLite2-ASN.mmdb] to [/tmp/elasticsearch-14340479604074439324/geoip-databases/YibBtYa-R5e4OSZd5QII5g/GeoLite2-ASN.mmdb.tmp.gz]"  }
{"type": "server", "timestamp": "2021-09-03T09:49:01,358Z", "level": "INFO", "component": "o.e.i.g.DatabaseRegistry", "": "elasticsearch", "": "elasticsearch-master-0", "message": "downloading geoip database [GeoLite2-City.mmdb] to [/tmp/elasticsearch-14340479604074439324/geoip-databases/YibBtYa-R5e4OSZd5QII5g/GeoLite2-City.mmdb.tmp.gz]" }
{"type": "server", "timestamp": "2021-09-03T09:49:04,203Z", "level": "INFO", "component": "o.e.c.r.a.AllocationService", "": "elasticsearch", "": "elasticsearch-master-0", "message": "Cluster health status changed from [YELLOW] to [GREEN] (reason: [shards started [[.geoip_databases][0]]])."  }
{"type": "server", "timestamp": "2021-09-03T09:49:05,125Z", "level": "INFO", "component": "o.e.i.g.DatabaseRegistry", "": "elasticsearch", "": "elasticsearch-master-0", "message": "database file changed [/tmp/elasticsearch-14340479604074439324/geoip-databases/YibBtYa-R5e4OSZd5QII5g/GeoLite2-ASN.mmdb], reload database..." }
{"type": "server", "timestamp": "2021-09-03T09:49:05,508Z", "level": "INFO", "component": "o.e.i.g.DatabaseRegistry", "": "elasticsearch", "": "elasticsearch-master-0", "message": "database file changed [/tmp/elasticsearch-14340479604074439324/geoip-databases/YibBtYa-R5e4OSZd5QII5g/GeoLite2-Country.mmdb], reload database..." }
{"type": "server", "timestamp": "2021-09-03T09:49:09,311Z", "level": "INFO", "component": "o.e.i.g.DatabaseRegistry", "": "elasticsearch", "": "elasticsearch-master-0", "message": "database file changed [/tmp/elasticsearch-14340479604074439324/geoip-databases/YibBtYa-R5e4OSZd5QII5g/GeoLite2-City.mmdb], reload database..." }

If you have any idea what is going on, I'll be thankfull :slight_smile:


Please note that this is not an error. It's an informational entry telling you something has changed, it's not a problem :slight_smile:

Yeah, ok, but my pods are Running with state 0/1. This is not acceptable.

EDIT: I'm using Elasticsearch helm chart v.7.14.

It might be better to start another thread with more info so we can help you.

Do you mean new topic here in


Hi. did you solve your issue? because i have same issue exactly like you.
did you open new topic here or ?

Hey! Yeah so my solution was to remove everything from my cluster, create certs one more time (I am using esConfig field to add specified elasticsearch.yml file) and run helm chart one again. Then it works.

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