开发者社区 > 云原生 > 正文

nacos and zipkin exception

组件信息

Nacos

描述你遇到的问题

request data to zipkin success,but nacos exception

2019-03-28 14:11:48.637 ERROR [ins-user,,,] 43273 --- [com.alibaba.nacos.client.naming.updater] com.alibaba.nacos.client.naming : [] [] [CALL-SERVER] failed to req API:http://192.168.0.253:8848/nacos/v1/ns/api/srvIPXT. code:404 msg: dom not found: 192.168.0.251 2019-03-28 14:11:48.638 ERROR [ins-user,,,] 43273 --- [com.alibaba.nacos.client.naming.updater] com.alibaba.nacos.client.naming : [] [] [NA] req api:/nacos/v1/ns/api/srvIPXT failed, server(192.168.0.253:8848

com.alibaba.nacos.api.exception.NacosException: null at com.alibaba.nacos.client.naming.net.NamingProxy.callServer(NamingProxy.java:304) at com.alibaba.nacos.client.naming.net.NamingProxy.reqAPI(NamingProxy.java:327) at com.alibaba.nacos.client.naming.net.NamingProxy.reqAPI(NamingProxy.java:310) at com.alibaba.nacos.client.naming.net.NamingProxy.reqAPI(NamingProxy.java:257) at com.alibaba.nacos.client.naming.core.HostReactor.updateServiceNow(HostReactor.java:340) at com.alibaba.nacos.client.naming.core.HostReactor$UpdateTask.run(HostReactor.java:429) 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:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)

2019-03-28 14:11:48.715 ERROR [ins-user,,,] 43273 --- [com.alibaba.nacos.client.naming.updater] com.alibaba.nacos.client.naming : [] [] [CALL-SERVER] failed to req API:http://192.168.0.253:8849/nacos/v1/ns/api/srvIPXT. code:404 msg: dom not found: 192.168.0.251 2019-03-28 14:11:48.715 ERROR [ins-user,,,] 43273 --- [com.alibaba.nacos.client.naming.updater] com.alibaba.nacos.client.naming : [] [] [NA] req api:/nacos/v1/ns/api/srvIPXT failed, server(192.168.0.253:8849

com.alibaba.nacos.api.exception.NacosException: null at com.alibaba.nacos.client.naming.net.NamingProxy.callServer(NamingProxy.java:304) at com.alibaba.nacos.client.naming.net.NamingProxy.reqAPI(NamingProxy.java:327) at com.alibaba.nacos.client.naming.net.NamingProxy.reqAPI(NamingProxy.java:310) at com.alibaba.nacos.client.naming.net.NamingProxy.reqAPI(NamingProxy.java:257) at com.alibaba.nacos.client.naming.core.HostReactor.updateServiceNow(HostReactor.java:340) at com.alibaba.nacos.client.naming.core.HostReactor$UpdateTask.run(HostReactor.java:429) 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:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)

2019-03-28 14:11:48.716 ERROR [ins-user,,,] 43273 --- [com.alibaba.nacos.client.naming.updater] com.alibaba.nacos.client.naming : [] [] [NA] failed to update serviceName: 192.168.0.251

java.lang.IllegalStateException: failed to req API:/nacos/v1/ns/api/srvIPXT after all servers([192.168.0.253:8848, 192.168.0.253:8849, 192.168.0.253:8850]) tried at com.alibaba.nacos.client.naming.net.NamingProxy.reqAPI(NamingProxy.java:335) at com.alibaba.nacos.client.naming.net.NamingProxy.reqAPI(NamingProxy.java:310) at com.alibaba.nacos.client.naming.net.NamingProxy.reqAPI(NamingProxy.java:257) at com.alibaba.nacos.client.naming.core.HostReactor.updateServiceNow(HostReactor.java:340) at com.alibaba.nacos.client.naming.core.HostReactor$UpdateTask.run(HostReactor.java:429) 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:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)

描述你期望发生的事情

1.通过nacos注册中心和配置中心,并获得conf数据

cloud: nacos: discovery: server-addr: 192.168.0.253:8848,192.168.0.253:8849,192.168.0.253:8850 config: server-addr: 192.168.0.253:8848,192.168.0.253:8849,192.168.0.253:8850 file-extension: yaml shared-dataids: all-service-common.yaml refreshable-dataids: all-service-common.yaml

2.添加 zipkin

org.springframework.cloud spring-cloud-starter-zipkin zipkin: discovery-client-enabled: false base-url: http://192.168.0.251:9411/ sleuth: sampler: probability: 1

3.任意springmvc请求,出现异常

您的环境

SpringBoot 2.1.3.RELEASE SpringCloud Greenwich.RELEASE spring-cloud-alibaba 0.2.1.RELEASE nacos-server 0.8

原提问者GitHub用户Fyuxuan

展开
收起
白夜行fighting 2023-06-11 10:48:20 86 0
1 条回答
写回答
取消 提交回答
  • spring cloud alibaba 0.2.1.RELEASE是在SpringCloud Finchley中构建的,spring引导版本是2.0.X。也许降级您的spring-boot/cloud版本可以解决这个问题。

    原回答者GitHub用户fangjian0423

    2023-06-11 11:34:18
    赞同 展开评论 打赏
问答分类:
问答标签:
问答地址:

阿里云拥有国内全面的云原生产品技术以及大规模的云原生应用实践,通过全面容器化、核心技术互联网化、应用 Serverless 化三大范式,助力制造业企业高效上云,实现系统稳定、应用敏捷智能。拥抱云原生,让创新无处不在。

相关电子书

更多
Nacos架构&原理 立即下载
workshop专场-微服务专场-开发者动手实践营-微服务-使用Nacos进行服务的动态发现和流量调度 立即下载
Nacos 启航,发布第一个版本, 云原生时代助力用户微服务平台建设 立即下载