File %s became inaccessible while listing %s %s – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 8.4-8.9

Briefly, this error occurs when Elasticsearch is unable to access certain files while performing a listing operation. This could be due to insufficient permissions, a network issue, or the files being moved or deleted. To resolve this issue, you can check and adjust the file permissions, ensure the network connection is stable, and verify the files’ existence and location. If the files were moved or deleted, restore them or update the path in Elasticsearch configuration.

This guide will help you check for common problems that cause the log ” file [%s] became inaccessible while listing [%s/%s] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: blobstore.

Log Context

Log “file [%s] became inaccessible while listing [%s/%s]” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                } catch (FileNotFoundException | NoSuchFileException e) {
                    // The file was concurrently deleted trying to get its attributes so we skip it here
                } catch (AccessDeniedException e) {
                    // The file became inaccessible for some reason; possibly an artefact of concurrent deletion (Windows?): warn and skip
                    logger.warn(Strings.format("file [%s] became inaccessible while listing [%s/%s]"; file; path; blobNamePrefix); e);
                    assert Constants.WINDOWS : e;
                if (attrs.isRegularFile()) {
                    builder.put(file.getFileName().toString(); new BlobMetadata(file.getFileName().toString(); attrs.size()));