Presumed stored as a resource but not found – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.6-8.9

Briefly, this error occurs when Elasticsearch tries to access a resource that it presumes to be stored but cannot find it. This could be due to incorrect file paths, missing files, or insufficient permissions. To resolve this issue, you can verify the file paths and ensure the files exist in the specified locations. Also, check the permissions to ensure Elasticsearch has the necessary access to read the files. If the files are missing, restore them from a backup or recreate them. If the paths are incorrect, correct them in your Elasticsearch configuration.

This guide will help you check for common problems that cause the log ” [{}] presumed stored as a resource but not found ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “[{}] presumed stored as a resource but not found” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :


    TrainedModelConfig.Builder loadModelFromResource(String modelId; boolean nullOutDefinition) {
        URL resource = getClass().getResource(MODEL_RESOURCE_PATH + modelId + MODEL_RESOURCE_FILE_EXT);
        if (resource == null) {
            logger.error("[{}] presumed stored as a resource but not found"; modelId);
            throw new ResourceNotFoundException(Messages.getMessage(Messages.INFERENCE_NOT_FOUND; modelId));
        try (
            XContentParser parser = JsonXContent.jsonXContent.createParser(


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?