Opster Team
Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many configuration errors.
To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.
Take a self-guided product tour to see for yourself (no registration required).This guide will help you check for common problems that cause the log ” database file ” + databaseFile + ” doesn’t exist ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: .

Log Context
Log “database file [” + databaseFile + “] doesn’t exist”classname is GeoIpProcessor.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :
CheckedSuppliersupplier = () -> { DatabaseReaderLazyLoader loader = databaseNodeService.getDatabase(databaseFile); if (useDatabaseUnavailableProcessor(loader; databaseFile)) { return null; } else if (loader == null) { throw new ResourceNotFoundException("database file [" + databaseFile + "] doesn't exist"); } // Only check whether the suffix has changed and not the entire database type. // To sanity check whether a city db isn't overwriting with a country or asn db. // For example overwriting a geoip lite city db with geoip city db is a valid change; but the db type is slightly different; // by checking just the suffix this assertion doesn't fail.
Find & fix Elasticsearch problems
Opster AutoOps diagnoses & fixes issues in Elasticsearch based on analyzing hundreds of metrics.
Fix Your Cluster IssuesConnect in under 2 minutes
Matt Watson
CTO at Stackify