All Products
Search

This Product

    Enterprise Distributed Application Service:Troubleshoot Nacos configuration query failures

    Document Center

    Enterprise Distributed Application Service:Troubleshoot Nacos configuration query failures

    Last Updated:Mar 12, 2026

    When an Enterprise Distributed Application Service (EDAS) application fails to start because Nacos cannot retrieve its microservices configurations, use these steps to diagnose and resolve the issue.

    Symptoms

    The application fails to start during deployment with a Nacos configuration exception. The error log typically contains one of the following:

    • NacosException in the application startup log

    • Configuration file not found errors in the Nacos client log

    Cause

    An exception exists in the Nacos configuration file.

    Diagnose the issue

    Step 1: Check whether configurations are cached locally

    Log in to the application instance. Navigate to the diamond or nacos directory, and run the following command to search for the cached configuration file:

    find / -name "<your-data-id>"

    Replace <your-data-id> with the actual Data ID of your configuration.

    Expected results:

    Deployment type

    Expected output

    Elastic Compute Service (ECS)

    A file path under the local Nacos cache directory

    Kubernetes

    A file path inside the container's Nacos cache directory

    ECS application example:

    4

    Kubernetes application example:

    5

    Resolve the issue

    No configuration found

    If Step 1 returns no results, the configuration is not reaching the instance. Check the following causes in order:

    1. Verify the Nacos client version. The client version must match the requirements of your EDAS registry. Incompatible versions cannot connect to the EDAS-managed Nacos server.

    2. Confirm the namespace. The application and its configurations must belong to the same microservices namespace. Make sure that no application is configured in the configuration.

    3. Validate the Data ID and group. Check whether the data ID and group that are configured for the microservices are valid. For more information about the data ID of a Spring Boot application, see Nacos Spring Cloud.

    4. Check for a user-defined Nacos client version. Verify whether a user-defined Nacos client version is used, as it may conflict with the EDAS-managed Nacos server.

    Unexpected or garbled configuration

    If Step 1 returns results but the content is garbled or incorrect:

    1. Validate the Data ID and group. Compare the configured values in your application against the values in the EDAS console. For more details, see Nacos Spring Cloud.

    2. Fix garbled configurations. If the configurations are garbled, downgrade the Nacos client to a version earlier than 1.3.

      Note

      If you are using Spring Cloud Alibaba, change the version of Spring Cloud Alibaba to 2.2.6.RELEASE. This will fix the issue of garbled text.

    Related information