Seata: 1.4版本 [17:39:13] [main] [ERROR] i.s.c.r.n.NettyClientChannelManager can not get cluster name in registry config 'service.vgroupMapping.oauth-seata-service-group', please make sure registry config correct

Created on 3 Jan 2021  ·  8Comments  ·  Source: seata/seata

[17:39:11] [main] [INFO ] o.s.c.s.PostProcessorRegistrationDelegate$BeanPostProcessorChecker Bean 'com.alibaba.cloud.sentinel.custom.SentinelAutoConfiguration' of type [com.alibaba.cloud.sentinel.custom.SentinelAutoConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
[17:39:11] [main] [INFO ] o.s.b.w.e.t.TomcatWebServer Tomcat initialized with port(s): 8905 (http)
[17:39:11] [main] [INFO ] o.a.c.h.Http11NioProtocol Initializing ProtocolHandler ["http-nio-8905"]
[17:39:11] [main] [INFO ] o.a.c.c.StandardService Starting service [Tomcat]
[17:39:11] [main] [INFO ] o.a.c.c.StandardEngine Starting Servlet engine: [Apache Tomcat/9.0.33]
[17:39:11] [main] [INFO ] o.a.c.c.C.[.[.[/] Initializing Spring embedded WebApplicationContext
[17:39:11] [main] [INFO ] o.s.w.c.ContextLoader Root WebApplicationContext: initialization completed in 2002 ms
[17:39:12] [main] [INFO ] c.a.n.c.naming initializer namespace from System Property :null
[17:39:12] [main] [INFO ] c.a.n.c.naming initializer namespace from System Environment :null
[17:39:12] [main] [INFO ] c.a.n.c.naming initializer namespace from System Property :null
[17:39:12] [main] [INFO ] c.a.d.s.b.a.DruidDataSourceAutoConfigure Init DruidDataSource
[17:39:12] [main] [INFO ] c.a.d.p.DruidDataSource {dataSource-1} inited
[17:39:12] [main] [INFO ] i.s.s.a.d.SeataAutoDataSourceProxyCreator Auto proxy of [dataSource]
[17:39:13] [main] [ERROR] i.s.c.r.n.NettyClientChannelManager can not get cluster name in registry config 'service.vgroupMapping.oauth-seata-service-group', please make sure registry config correct
[17:39:13] [main] [INFO ] o.a.c.c.StandardContext Suspicious URL pattern: [/ants/**] in context [], see sections 12.1 and 12.2 of the Servlet specification
[17:39:13] [main] [INFO ] c.a.c.x.XssFilter 初始化进入了过滤器,处理XSS
Logging initialized using 'class org.apache.ibatis.logging.stdout.StdOutImpl' adapter.
[17:39:14] [main] [INFO ] o.s.b.a.e.w.EndpointLinksResolver Exposing 20 endpoint(s) beneath base path '/actuator'
[17:39:14] [main] [INFO ] s.d.s.w.PropertySourcedRequestMappingHandlerMapping Mapped URL path [/v2/api-docs] onto method [springfox.documentation.swagger2.web.Swagger2Controller#getDocumentation(String, HttpServletRequest)]
[17:39:14] [main] [INFO ] o.s.s.c.ThreadPoolTaskExecutor Initializing ExecutorService 'threadPoolTaskExecutor'
[17:39:14] [main] [WARN ] c.n.c.s.URLConfigurationSource No URLs will be polled as dynamic configuration sources.
[17:39:14] [main] [INFO ] c.n.c.s.URLConfigurationSource To enable URLs as dynamic configuration sources, define System property archaius.configurationSource.additionalUrls or make config.properties available on classpath.
[17:39:14] [main] [WARN ] c.n.c.s.URLConfigurationSource No URLs will be polled as dynamic configuration sources.
[17:39:14] [main] [INFO ] c.n.c.s.URLConfigurationSource To enable URLs as dynamic configuration sources, define System property archaius.configurationSource.additionalUrls or make config.properties available on classpath.
[17:39:14] [main] [INFO ] o.s.s.c.ThreadPoolTaskScheduler Initializing ExecutorService 'Nacso-Watch-Task-Scheduler'

Most helpful comment

registry:
type: nacos
nacos:
application: seata-server
server-addr: 127.0.0.1:8848
group: local
namespace: local
cluster: default
username: nacos
password: nacos
这里的namespace 是不是应该是seata

服务我注册到namespace = local中的,但是seata的配置我配置到 namespace = seata 中的,而且我也是按照这个规则引用的,这两个一定要一样吗?

seata
i.s.c.r.n.NettyPoolableFactory register success, cost 291 ms, version:1.5.0-SNAPSHOT,role:RMROLE,channel:[id: 0xf996b1fd, L:/172.30.16.183:64171 - R:/172.30.16.183:8091]
i.s.c.r.n.NettyPoolableFactory register success, cost 292 ms, version:1.5.0-SNAPSHOT,role:TMROLE,channel:[id: 0xaf4e6d0c, L:/172.30.16.183:64170 - R:/172.30.16.183:8091]
我按照您的思路貌似可以了,我总结一下:seata-server 的 registry namespace 一定要与 config namespace一致

All 8 comments

用的是1.4版本,nacos中seata-server已经注册上去了,项目名+seata-service-group总是报错
seata:
enabled: true
enable-auto-data-source-proxy: true
tx-service-group: oauth-seata-service-group
registry:
type: nacos
nacos:
application: seata-server
server-addr: 127.0.0.1:8848
group: local
namespace: local
cluster: default
username: nacos
password: nacos
config:
type: nacos
nacos:
server-addr: 127.0.0.1:8848
group: local
username: nacos
password: nacos
namespace: seata
service:
vgroup-mapping:
oauth-seata-service-group: default
disable-global-transaction: false
client:
rm:
report-success-enable: false
这个是项目中的配置

service.vgroupMapping.oauth-seata-service-group=default
service.default.grouplist=127.0.0.1:8091
service.enableDegrade=false
service.disableGlobalTransaction=false
这个是我导入nacos中的配置的一部分

registry {
type = "nacos"
loadBalance = "RandomLoadBalance"
loadBalanceVirtualNodes = 10
nacos {
application = "seata-server"
serverAddr = "127.0.0.1:8848"
group = "local"
namespace = "local"
cluster = "default"
username = "nacos"
password = "nacos"
}
}
config {
type = "nacos"
nacos {
serverAddr = "127.0.0.1:8848"
namespace = "seata"
group = "local"
username = "nacos"
password = "nacos"
}
}
这个是我seata-server中的配置

帮我看看呢,哪里有问题

oauth-seata-service-group这个事务分组需要配置在配置中心中,同时他的value要等于server的cluster------------------ 原始邮件 ------------------
发件人: "zhaiyh131"<[email protected]>
发送时间: 2021年1月3日(星期天) 下午5:58
收件人: "seata/seata"<[email protected]>;
抄送: "Subscribed"<[email protected]>;
主题: Re: [seata/seata] 1.4版本 [17:39:13] [main] [ERROR] i.s.c.r.n.NettyClientChannelManager can not get cluster name in registry config 'service.vgroupMapping.oauth-seata-service-group', please make sure registry config correct (#3432)

server的cluste

image
这个我都配置了,nacos中已经配置,但是还是没用service.vgroupMapping.oauth-seata-service-group=default我通过config.txt脚本导入进去的 namespace = seata group = local

server的cluste

image
这个我都配置了,nacos中已经配置,但是还是没用service.vgroupMapping.oauth-seata-service-group=default我通过config.txt脚本导入进去的 namespace = seata group = local

截图看不到,理论上就是没通过nacos拿到service.vgroupMapping.oauth-seata-service-group的值,自己好好确认下配置,这个我们测试过很多次,用户这个配置项也遇到过类似问题的不少,都是自己配置有问题,改对了就好了

server的cluste

image
这个我都配置了,nacos中已经配置,但是还是没用service.vgroupMapping.oauth-seata-service-group=default我通过config.txt脚本导入进去的 namespace = seata group = local

截图看不到,理论上就是没通过nacos拿到service.vgroupMapping.oauth-seata-service-group的值,自己好好确认下配置,这个我们测试过很多次,用户这个配置项也遇到过类似问题的不少,都是自己配置有问题,改对了就好了

这个我排查两天了,感觉没有什么问题,我的配置我贴在上面了,能不能帮我看一下啊,谢谢

registry:
type: nacos
nacos:
application: seata-server
server-addr: 127.0.0.1:8848
group: local
namespace: local
cluster: default
username: nacos
password: nacos

这里的namespace 是不是应该是seata

registry:
type: nacos
nacos:
application: seata-server
server-addr: 127.0.0.1:8848
group: local
namespace: local
cluster: default
username: nacos
password: nacos

这里的namespace 是不是应该是seata

服务我注册到namespace = local中的,但是seata的配置我配置到 namespace = seata 中的,而且我也是按照这个规则引用的,这两个一定要一样吗?

registry:
type: nacos
nacos:
application: seata-server
server-addr: 127.0.0.1:8848
group: local
namespace: local
cluster: default
username: nacos
password: nacos
这里的namespace 是不是应该是seata

服务我注册到namespace = local中的,但是seata的配置我配置到 namespace = seata 中的,而且我也是按照这个规则引用的,这两个一定要一样吗?

seata
i.s.c.r.n.NettyPoolableFactory register success, cost 291 ms, version:1.5.0-SNAPSHOT,role:RMROLE,channel:[id: 0xf996b1fd, L:/172.30.16.183:64171 - R:/172.30.16.183:8091]
i.s.c.r.n.NettyPoolableFactory register success, cost 292 ms, version:1.5.0-SNAPSHOT,role:TMROLE,channel:[id: 0xaf4e6d0c, L:/172.30.16.183:64170 - R:/172.30.16.183:8091]
我按照您的思路貌似可以了,我总结一下:seata-server 的 registry namespace 一定要与 config namespace一致

Was this page helpful?
0 / 5 - 0 ratings