ChangedenCZD opened a new issue #1764:
URL: https://github.com/apache/dubbo-go/issues/1764
<!-- Please use this template while reporting a bug and provide as much info
as possible. Not doing so may result in your bug not being addressed in a
timely manner. Thanks!
-->
**What happened**:
## yml
```yaml
dubbo: # Dubbo Go Service
registries:
gfgfh:
protocol: nacos
timeout: 3s
address: 127.0.0.1:8848
group: DEFAULT_GROUP
namespace: public
protocols:
triple:
name: dubbo
port: 20000
consumer:
references:
ApiPingConsumer:
interface: com.chansos.dubbogo.service.ApiPingService1
version: 1.0.0
group: dubbo-go
provider:
services:
ApiPingProvider:
interface: com.chansos.dubbogo.service.ApiPingService
version: 1.0.0
group: dubbo-go
```
## log
```shell
[GIN-debug] Listening and serving HTTP on 0.0.0.0:8280
2022-02-23T10:16:31.256+0800 INFO config/root_config.go:150
[Config Center] Config center doesn't start
2022-02-23T10:16:31.268+0800 INFO nacos/registry.go:270 [Nacos
Registry] New nacos registry with url = map[host:192.168.1.61 port:8848
protocol:nacos registry:nacos registry.group:DEFAULT_GROUP registry.label:true
registry.namespace:public registry.preferred:false registry.role:0
registry.timeout:3s registry.ttl:10s registry.weight:0 registry.
zone: remote-client-name:dubbo.registries-nacos-192.168.1.61:8848
simplified:false]
2022-02-23T10:16:31.268+0800 INFO nacos/builder.go:138 [Nacos
Client] New nacos client with config = [{Scheme: ContextPath:
IpAddr:192.168.1.61 Port:8848}]
2022-02-23T10:16:31.269+0800 INFO nacos_client/nacos_client.go:79
logDir:<D:\gfgfh\log> cacheDir:<D:\gfgfh\cache>
2022-02-23T10:16:31.270+0800 INFO v3router/router_chain.go:55
[NewUniformRouterChain] Config center does not start, please check if the
configuration center has been properly configured in dubbogo.yml
2022-02-23T10:16:31.270+0800 INFO nacos/registry.go:125 [Nacos
Registry] Registry instance with param = {Ip:192.168.1.108 Port:80 Weight:1
Enable:true Healthy:true Metadata:map[app.version:3.0.0 application:dubbo.io
async:false bean.name:ApiPingConsumer cluster:failover config.tracing:
environment:dev generic: group:dubbo-go interface:com.chan
sos.dubbogo.service.ApiPingService1 loadbalance: metadata-type:local
methods: module:sample nacos.category:consumers name:dubbo.io
organization:dubbo-go owner:dubbo-go
path:/com.chansos.dubbogo.service.ApiPingService1 protocol:tri provided-by:
reference.filter:cshutdown registry.role:0 release:dubbo-golang-3.0.0 retries:
serialization: side:consumer s
ticky:false timestamp:1645582591 version:1.0.0] ClusterName:
ServiceName:consumers:com.chansos.dubbogo.service.ApiPingService1:1.0.0:dubbo-go
GroupName:DEFAULT_GROUP Ephemeral:true}
2022-02-23T10:16:31.280+0800 ERROR nacos/listener.go:128 nacos
subscribe callback error:[client.Subscribe] subscribe failed,hosts is empty ,
subscribe:&{ServiceName:providers:com.chansos.dubbogo.service.ApiPingService1:1.0.0:dubbo-go
Clusters:[] GroupName:DEFAULT_GROUP SubscribeCallback:0x1b830c0}
dubbo.apache.org/dubbo-go/v3/registry/nacos.(*nacosListener).Callback
D:/go/pkg/mod/dubbo.apache.org/dubbo-go/[email protected]/registry/nacos/listener.go:128
github.com/nacos-group/nacos-sdk-go/clients/naming_client.(*SubscribeCallback).ServiceChanged
D:/go/pkg/mod/github.com/nacos-group/[email protected]/clients/naming_client/subscribe_callback.go:76
github.com/nacos-group/nacos-sdk-go/clients/naming_client.(*HostReactor).ProcessServiceJson
D:/go/pkg/mod/github.com/nacos-group/[email protected]/clients/naming_client/host_reactor.go:100
github.com/nacos-group/nacos-sdk-go/clients/naming_client.(*HostReactor).updateServiceNow
D:/go/pkg/mod/github.com/nacos-group/[email protected]/clients/naming_client/host_reactor.go:151
github.com/nacos-group/nacos-sdk-go/clients/naming_client.(*HostReactor).GetServiceInfo
D:/go/pkg/mod/github.com/nacos-group/[email protected]/clients/naming_client/host_reactor.go:108
github.com/nacos-group/nacos-sdk-go/clients/naming_client.(*NamingClient).GetService
D:/go/pkg/mod/github.com/nacos-group/[email protected]/clients/naming_client/naming_client.go:183
github.com/nacos-group/nacos-sdk-go/clients/naming_client.(*NamingClient).Subscribe
D:/go/pkg/mod/github.com/nacos-group/[email protected]/clients/naming_client/naming_client.go:324
dubbo.apache.org/dubbo-go/v3/registry/nacos.(*nacosListener).startListen.func1
D:/go/pkg/mod/dubbo.apache.org/dubbo-go/[email protected]/registry/nacos/listener.go:201
2022-02-23T10:16:34.308+0800 ERROR config/consumer_config.go:150 No
provider available of the service
com.chansos.dubbogo.service.ApiPingService1.please check configuration.
dubbo.apache.org/dubbo-go/v3/config.(*ConsumerConfig).Load
D:/go/pkg/mod/dubbo.apache.org/dubbo-go/[email protected]/config/consumer_config.go:150
dubbo.apache.org/dubbo-go/v3/config.(*RootConfig).Start.func1
D:/go/pkg/mod/dubbo.apache.org/dubbo-go/[email protected]/config/root_config.go:223
sync.(*Once).doSlow
C:/Program Files/Go/src/sync/once.go:68
sync.(*Once).Do
C:/Program Files/Go/src/sync/once.go:59
dubbo.apache.org/dubbo-go/v3/config.(*RootConfig).Start
D:/go/pkg/mod/dubbo.apache.org/dubbo-go/[email protected]/config/root_config.go:221
dubbo.apache.org/dubbo-go/v3/config.(*RootConfig).Init
D:/go/pkg/mod/dubbo.apache.org/dubbo-go/[email protected]/config/root_config.go:216
dubbo.apache.org/dubbo-go/v3/config.Load
D:/go/pkg/mod/dubbo.apache.org/dubbo-go/[email protected]/config/config_loader.go:56
gfgfh/component.initDubboService
D:/gfgfh/component/dubbo.go:50
gfgfh/component.(*dubboComponent).Init
D:/gfgfh/component/dubbo.go:30
gfgfh/component.Install.func1
D:/gfgfh/component/init.go:26
2022-02-23T10:16:39.312+0800 INFO config/root_config.go:150
[Config Center] Config center doesn't start
```
## nacos
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
