Failed to load default project id – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.13-8.9

Briefly, this error occurs when Elasticsearch is unable to load the default project ID, which is usually due to incorrect configuration settings or missing project ID in the Elasticsearch configuration file. To resolve this issue, you can check the Elasticsearch configuration file and ensure that the default project ID is correctly set. If the project ID is missing, you should add it. Also, ensure that Elasticsearch has the necessary permissions to access and read the configuration file. Lastly, restarting the Elasticsearch service after making these changes can help in resolving the issue.

This guide will help you check for common problems that cause the log ” failed to load default project id ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: repository-gcs, repositories.

Log Context

Log “failed to load default project id” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                defaultProjectId = SocketAccess.doPrivilegedIOException(ServiceOptions::getDefaultProjectId);
                if (defaultProjectId != null) {
            } catch (Exception e) {
                logger.warn("failed to load default project id"; e);
            if (defaultProjectId == null) {
                try {
                    // fallback to manually load project ID here as the above ServiceOptions method has the metadata endpoint hardcoded;
                    // which makes it impossible to test