搭建zipkin-server踩的坑

当前最新的zipkin-server版本为2.12.9，于是在pom文件中导入以下依赖

		
            io.zipkin.java
            zipkin-server
            2.12.9
        
        
            io.zipkin.java
            zipkin-autoconfigure-ui
            2.12.9
        

启动项目时，提示

SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/D:/MyRepository/ch/qos/logback/logback-classic/1.2.3/logback-classic-1.2.3.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/D:/MyRepository/org/apache/logging/log4j/log4j-slf4j-impl/2.11.2/log4j-slf4j-impl-2.11.2.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [ch.qos.logback.classic.util.ContextSelectorStaticBinder]

SLF4J绑定了多个实现的日志框架，不影响项目启动，但作为一个强迫症肯定是要改好的，pom文件中将zipkin-server绑定的log4j移除即可

		
            io.zipkin.java
            zipkin-server
            2.12.9
            
                
                    log4j-slf4j-impl
                    org.apache.logging.log4j
                
            
        
        
            io.zipkin.java
            zipkin-autoconfigure-ui
            2.12.9
        

使用zipkin-server 2.12.9版本启动的话还会报错

org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'armeriaServer' defined in class path resource [com/linecorp/armeria/spring/ArmeriaAutoConfiguration.class]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.linecorp.armeria.server.Server]: Factory method 'armeriaServer' threw exception; nested exception is java.lang.NullPointerException

网上查了以下，是因为从 2.12.6 版本开始有个较大的更新，迁移使用 Armeria HTTP 引擎。从此版本开始，若直接添加依赖的 Spring Boot 应用启动会存在冲突。既然2.12.6不行的话，那就试试2.12.5版本吧，改完pom文件后重新启动项目，项目完美启动。然后打开浏览器输入http://localhost:9411/

然而还是不行，不得已再降一下zipkin-server的版本试下吧，于是就换成了2.12.3版本

哎呀终于可以了，我太难了

最终引入的zipkin依赖是这样的

		
            io.zipkin.java
            zipkin-server
            2.12.3
            
                
                    log4j-slf4j-impl
                    org.apache.logging.log4j
                
            
        
        
            io.zipkin.java
            zipkin-autoconfigure-ui
            2.12.3
        

注册中心为Nacos，使用的过程中发现控制台一直在打印错误信息

java.lang.IllegalStateException: failed to req API:/nacos/v1/ns/instance/list after all servers([localhost:8848]) tried: failed to req API:http://localhost:8848/nacos/v1/ns/instance/list. code:404 msg: service not found: DEFAULT_GROUP@@localhost
	at com.alibaba.nacos.client.naming.net.NamingProxy.reqAPI(NamingProxy.java:380)
	at com.alibaba.nacos.client.naming.net.NamingProxy.reqAPI(NamingProxy.java:304)
	at com.alibaba.nacos.client.naming.net.NamingProxy.queryList(NamingProxy.java:217)
	at com.alibaba.nacos.client.naming.core.HostReactor.updateServiceNow(HostReactor.java:273)
	at com.alibaba.nacos.client.naming.core.HostReactor$UpdateTask.run(HostReactor.java:318)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)

需要在配置文件application.yml中加入discovery-client-enabled: false，完整配置文件为

  zipkin:
    base-url: http://zipkin-server/
    discovery-client-enabled: false
  sleuth:
    sampler:
      probability: 1.0

这个坑具体可以参考这篇博文 https://blog.csdn.net/lilizhou2008/article/details/100148968