Zipkin UI报错‘ERROR: cannot load service names: No message available’求助

Hey there, I’ve run into this exact error a few times when setting up Zipkin with Spring Cloud, so let’s walk through the most common fixes step by step. That error usually means Zipkin’s backend isn’t properly configured to store or retrieve trace data, which breaks the UI’s ability to load service names.

1. Explicitly Configure In-Memory Storage #

By default, Zipkin should use in-memory storage for testing, but sometimes newer Spring Cloud versions require you to explicitly enable it. Without this, Zipkin might try to auto-detect a storage backend (like Elasticsearch or MySQL) that isn’t set up, leading to the error.

Add this line to your application.properties:

zipkin.storage.type=mem

This tells Zipkin to use the simple in-memory store, which is perfect for getting started quickly.

2. Fix Dependency Version Mismatches #

Spring Cloud and Zipkin Java versions need to play nice together. Using outdated or mismatched dependencies can cause hidden initialization issues that break the UI. Also, note that compile is deprecated in modern Gradle—switch to implementation instead.

Update your build.gradle dependencies to something like this (adjust versions to match your Spring Cloud release):

implementation 'org.springframework.cloud:spring-cloud-starter-zipkin'
implementation 'org.springframework.amqp:spring-rabbit'
implementation 'io.zipkin.java:zipkin-autoconfigure-ui:2.12.9' // Match with your Spring Cloud version

For example, if you’re using Spring Cloud Hoxton, stick to Zipkin 2.x versions. If you’re on a newer release like Gateway, check the Spring Cloud documentation for compatible Zipkin versions.

3. Resolve RabbitMQ Connection Issues #

You added the spring-rabbit dependency, which tells Zipkin to expect trace data from RabbitMQ. If RabbitMQ isn’t running, or your connection settings are wrong, this will cause backend failures that affect the UI.

• If you don’t need RabbitMQ right now: Temporarily remove the spring-rabbit dependency to simplify your setup. You can add it back once Zipkin is running correctly.
• If you do need RabbitMQ: Make sure the RabbitMQ server is up and running, then add these configs to application.properties:

  spring.rabbitmq.host=localhost
  spring.rabbitmq.port=5672
  spring.rabbitmq.username=guest
  spring.rabbitmq.password=guest
  

4. Check Startup Logs for Hidden Errors #

Often, the "cannot load service names" error is a symptom of a deeper issue during application startup. Look through your console logs for ERROR or WARN messages—things like failed bean creations, storage connection timeouts, or missing configurations.

For example, if you see a message like "Failed to connect to Elasticsearch", that means Zipkin was trying to use Elasticsearch storage without proper setup. Adjust your storage config to fix that.

Final Steps #

After making these changes:

1. Stop and restart your Zipkin server.
2. Access the UI at http://localhost:8085/zipkin/ (note the trailing slash is important in some versions).
3. Send a few test traces to Zipkin (from a client app configured with Spring Cloud Sleuth) and check if service names load correctly.

内容的提问来源于stack exchange，提问作者Prash