关于#nacoscom#的问题，如何解决？(标签-Rpc|关键词-lambda)

Question

关于#nacoscom#的问题，如何解决？

启动服务连接nacos报错

17:00:19.296 [main] INFO  c.a.n.c.r.client - [lambda$createClient$0,80] - [RpcClientFactory] create a new rpc client of bbb837ee-218e-4bc1-8045-da2d168ec583_config-0
17:00:19.329 [main] INFO  o.r.Reflections - [scan,232] - Reflections took 21 ms to scan 1 urls, producing 3 keys and 6 values 
17:00:19.352 [main] INFO  o.r.Reflections - [scan,232] - Reflections took 12 ms to scan 1 urls, producing 4 keys and 9 values 
17:00:19.361 [main] INFO  o.r.Reflections - [scan,232] - Reflections took 7 ms to scan 1 urls, producing 3 keys and 10 values 
17:00:19.489 [main] INFO  o.r.Reflections - [scan,232] - Reflections took 125 ms to scan 175 urls, producing 0 keys and 0 values 
17:00:19.497 [main] INFO  o.r.Reflections - [scan,232] - Reflections took 7 ms to scan 1 urls, producing 1 keys and 5 values 
17:00:19.506 [main] INFO  o.r.Reflections - [scan,232] - Reflections took 7 ms to scan 1 urls, producing 1 keys and 7 values 
17:00:19.514 [main] INFO  o.r.Reflections - [scan,232] - Reflections took 6 ms to scan 1 urls, producing 2 keys and 8 values 
17:00:19.640 [main] INFO  o.r.Reflections - [scan,232] - Reflections took 124 ms to scan 175 urls, producing 0 keys and 0 values 
17:00:19.641 [main] INFO  c.a.n.c.r.client - [printIfInfoEnabled,60] - [bbb837ee-218e-4bc1-8045-da2d168ec583_config-0] RpcClient init label, labels = {module=config, Vipserver-Tag=null, source=sdk, Amory-Tag=null, Location-Tag=null, taskId=0, AppName=unknown}
17:00:19.641 [main] INFO  c.a.n.c.r.client - [printIfInfoEnabled,60] - [bbb837ee-218e-4bc1-8045-da2d168ec583_config-0] Register server push request handler:com.alibaba.nacos.client.config.impl.ClientWorker$ConfigRpcTransportClient$$Lambda$338/47918293
17:00:19.642 [main] INFO  c.a.n.c.r.client - [printIfInfoEnabled,60] - [bbb837ee-218e-4bc1-8045-da2d168ec583_config-0] Register server push request handler:com.alibaba.nacos.client.config.impl.ClientWorker$ConfigRpcTransportClient$$Lambda$339/1894144426
17:00:19.642 [main] INFO  c.a.n.c.r.client - [printIfInfoEnabled,60] - [bbb837ee-218e-4bc1-8045-da2d168ec583_config-0] Registry connection listener to current client:com.alibaba.nacos.client.config.impl.ClientWorker$ConfigRpcTransportClient$1
17:00:19.643 [main] INFO  c.a.n.c.r.client - [printIfInfoEnabled,60] - [bbb837ee-218e-4bc1-8045-da2d168ec583_config-0] RpcClient init, ServerListFactory = com.alibaba.nacos.client.config.impl.ClientWorker$ConfigRpcTransportClient$2
17:00:19.648 [main] INFO  c.a.n.c.r.client - [printIfInfoEnabled,60] - [bbb837ee-218e-4bc1-8045-da2d168ec583_config-0] Try to connect to server on start up, server: {serverIp = 'jwcrm-nacos', server main port = 20007}
17:00:22.939 [main] ERROR c.a.n.c.r.c.g.GrpcClient - [printIfErrorEnabled,99] - Server check fail, please check server jwcrm-nacos ,port 21007 is available , error ={}
java.util.concurrent.TimeoutException: Waited 3000 milliseconds (plus 12 milliseconds, 217000 nanoseconds delay) for com.alibaba.nacos.shaded.io.grpc.stub.ClientCalls$GrpcFuture@aa004a0[status=PENDING, info=[GrpcFuture{clientCall={delegate={delegate=ClientCallImpl{method=MethodDescriptor{fullMethodName=Request/request, type=UNARY, idempotent=false, safe=false, sampledToLocalTracing=true, requestMarshaller=com.alibaba.nacos.shaded.io.grpc.protobuf.lite.ProtoLiteUtils$MessageMarshaller@4d8126f, responseMarshaller=com.alibaba.nacos.shaded.io.grpc.protobuf.lite.ProtoLiteUtils$MessageMarshaller@6d3c232f, schemaDescriptor=com.alibaba.nacos.api.grpc.auto.RequestGrpc$RequestMethodDescriptorSupplier@6b587673}}}}}]]
    at com.alibaba.nacos.shaded.com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:508)
    at com.alibaba.nacos.common.remote.client.grpc.GrpcClient.serverCheck(GrpcClient.java:148)
    at com.alibaba.nacos.common.remote.client.grpc.GrpcClient.connectToServer(GrpcClient.java:264)
    at com.alibaba.nacos.common.remote.client.RpcClient.start(RpcClient.java:390)
    at com.alibaba.nacos.client.config.impl.ClientWorker$ConfigRpcTransportClient.ensureRpcClient(ClientWorker.java:885)
    at com.alibaba.nacos.client.config.impl.ClientWorker$ConfigRpcTransportClient.getOneRunningClient(ClientWorker.java:1044)
    at com.alibaba.nacos.client.config.impl.ClientWorker$ConfigRpcTransportClient.queryConfig(ClientWorker.java:940)
    at com.alibaba.nacos.client.config.impl.ClientWorker.getServerConfig(ClientWorker.java:397)
    at com.alibaba.nacos.client.config.NacosConfigService.getConfigInner(NacosConfigService.java:166)
    at com.alibaba.nacos.client.config.NacosConfigService.getConfig(NacosConfigService.java:94)
    at com.alibaba.cloud.nacos.client.NacosPropertySourceBuilder.loadNacosData(NacosPropertySourceBuilder.java:85)
    at com.alibaba.cloud.nacos.client.NacosPropertySourceBuilder.build(NacosPropertySourceBuilder.java:73)
    at com.alibaba.cloud.nacos.client.NacosPropertySourceLocator.loadNacosPropertySource(NacosPropertySourceLocator.java:199)
    at com.alibaba.cloud.nacos.client.NacosPropertySourceLocator.loadNacosDataIfPresent(NacosPropertySourceLocator.java:186)
    at com.alibaba.cloud.nacos.client.NacosPropertySourceLocator.loadNacosConfiguration(NacosPropertySourceLocator.java:158)
    at com.alibaba.cloud.nacos.client.NacosPropertySourceLocator.loadSharedConfiguration(NacosPropertySourceLocator.java:116)
    at com.alibaba.cloud.nacos.client.NacosPropertySourceLocator.locate(NacosPropertySourceLocator.java:101)
    at org.springframework.cloud.bootstrap.config.PropertySourceLocator.locateCollection(PropertySourceLocator.java:51)
    at org.springframework.cloud.bootstrap.config.PropertySourceLocator.locateCollection(PropertySourceLocator.java:47)
    at org.springframework.cloud.bootstrap.config.PropertySourceBootstrapConfiguration.initialize(PropertySourceBootstrapConfiguration.java:95)
    at org.springframework.boot.SpringApplication.applyInitializers(SpringApplication.java:604)
    at org.springframework.boot.SpringApplication.prepareContext(SpringApplication.java:373)
    at org.springframework.boot.SpringApplication.run(SpringApplication.java:306)
    at org.springframework.boot.SpringApplication.run(SpringApplication.java:1303)
    at org.springframework.boot.SpringApplication.run(SpringApplication.java:1292)
    at com.ruoyi.auth.RuoYiAuthApplication.main(RuoYiAuthApplication.java:19)

Answer 1

根据错误日志，连接Nacos服务器时出现了超时异常。异常信息显示等待了3000毫秒，但仍然没有得到服务器的响应。这可能是由于服务器不可用或端口号错误导致的。

建议检查以下几点：

1. 确保Nacos服务器可用。可以尝试使用浏览器或其他工具访问Nacos服务器，确保能够正常连接。
2. 检查端口号是否正确。错误日志中显示尝试连接的端口号为21007，可能需要确认Nacos服务器的实际端口号是否为该值。
3. 检查防火墙或网络配置。如果服务器在防火墙后面或有其他网络配置限制，可能需要相应地进行配置调整，以确保客户端能够正常连接到服务器。

如果以上方法仍然无法解决问题，可能需要更详细的调试和分析。