记录一次微服务连接Nacos异常-errorMsg: Illegal character in authority at index 7:

城之于域2023-08-24 15:12

组件信息

Nacos 2.2.3

SpringCloud微服务

部署环境：centerOS

部署方式：k8s

前言

  • nacos开启鉴权，nacos地址通过变量方式传入服务中
java 复制代码 
PropsUtil.setProperty(props, "spring.cloud.nacos.discovery.server-addr", "${NACOS_ADDR}");
PropsUtil.setProperty(props, "spring.cloud.nacos.config.server-addr", "${NACOS_ADDR}");
PropsUtil.setProperty(props, "spring.cloud.nacos.discovery.password", "${NACOS_PASSWORD}");
PropsUtil.setProperty(props, "spring.cloud.nacos.discovery.username", "${NACOS_USERNAME}");
PropsUtil.setProperty(props, "spring.cloud.nacos.config.password", "${NACOS_PASSWORD}");
PropsUtil.setProperty(props, "spring.cloud.nacos.config.username", "${NACOS_USERNAME}");
  • k8s在传入${NACOS_ADDR}时先对地址做了base64编码

服务启动异常

下面是服务启动异常的日志

java 复制代码 
2023-08-23 15:25:53.187 [traceId:] [TID: N/A] ERROR 1 --- [           main] c.a.n.c.a.i.process.HttpLoginProcessor  [getResponse][102]: [NacosClientAuthServiceImpl] login http request failed url: http://****.****.svc.cluster.local:8848
/nacos/v1/auth/users/login, params: {username=nacos}, bodyMap: {password=****}, errorMsg: Illegal character in authority at index 7: http://****.****.svc.cluster.local:8848
/nacos/v1/auth/users/login?username=nacos
2023-08-23 15:25:53.191 [traceId:] [TID: N/A] ERROR 1 --- [naming.security] c.a.n.c.a.i.process.HttpLoginProcessor  [getResponse][102]: [NacosClientAuthServiceImpl] login http request failed url: http://****.****.svc.cluster.local:8848
/nacos/v1/auth/users/login, params: {username=nacos}, bodyMap: {password=*******}, errorMsg: Illegal character in authority at index 7: http://****.****.svc.cluster.local:8848
/nacos/v1/auth/users/login?username=nacos
2023-08-23 15:25:53.198 [traceId:] [TID: N/A]  INFO 1 --- [           main] com.alibaba.nacos.common.remote.client  [lambda$createClient$0][108]: [RpcClientFactory] create a new rpc client of e1146c19-413a-4f6f-8371-60242423f418
2023-08-23 15:25:53.205 [traceId:] [TID: N/A]  INFO 1 --- [           main] com.alibaba.nacos.common.remote.client  [printIfInfoEnabled][63]: [e1146c19-413a-4f6f-8371-60242423f418] RpcClient init, ServerListFactory = com.alibaba.nacos.client.naming.core.ServerListManager
2023-08-23 15:25:53.206 [traceId:] [TID: N/A]  INFO 1 --- [           main] com.alibaba.nacos.common.remote.client  [printIfInfoEnabled][63]: [e1146c19-413a-4f6f-8371-60242423f418] Registry connection listener to current client:com.alibaba.nacos.client.naming.remote.gprc.redo.NamingGrpcRedoService
2023-08-23 15:25:53.207 [traceId:] [TID: N/A]  INFO 1 --- [           main] com.alibaba.nacos.common.remote.client  [printIfInfoEnabled][63]: [e1146c19-413a-4f6f-8371-60242423f418] Register server push request handler:com.alibaba.nacos.client.naming.remote.gprc.NamingPushRequestHandler
2023-08-23 15:25:53.208 [traceId:] [TID: N/A]  INFO 1 --- [           main] com.alibaba.nacos.common.remote.client  [printIfInfoEnabled][63]: [e1146c19-413a-4f6f-8371-60242423f418] Try to connect to server on start up, server: {serverIp = '****.****.svc.cluster.local', server main port = 8848}
2023-08-23 15:25:53.208 [traceId:] [TID: N/A]  INFO 1 --- [           main] c.a.n.c.remote.client.grpc.GrpcClient   [createNewManagedChannel][182]: grpc client connection server:****.****.svc.cluster.local ip,serverPort:9848,grpcTslConfig:{"sslProvider":"","enableTls":false,"mutualAuthEnable":false,"trustAll":false}
2023-08-23 15:25:53.326 [traceId:] [TID: N/A]  INFO 1 --- [           main] com.alibaba.nacos.common.remote.client  [printIfInfoEnabled][63]: [e1146c19-413a-4f6f-8371-60242423f418] Success to connect to server [****.****.svc.cluster.local:8848] on start up, connectionId = 1692775552671_200.0.6.31_37904
2023-08-23 15:25:53.327 [traceId:] [TID: N/A]  INFO 1 --- [t.remote.worker] com.alibaba.nacos.common.remote.client  [printIfInfoEnabled][63]: [e1146c19-413a-4f6f-8371-60242423f418] Notify connected event to listeners.
2023-08-23 15:25:53.327 [traceId:] [TID: N/A]  INFO 1 --- [           main] com.alibaba.nacos.common.remote.client  [printIfInfoEnabled][63]: [e1146c19-413a-4f6f-8371-60242423f418] Register server push request handler:com.alibaba.nacos.common.remote.client.RpcClient$ConnectResetRequestHandler
2023-08-23 15:25:53.327 [traceId:] [TID: N/A]  INFO 1 --- [t.remote.worker] com.alibaba.nacos.client.naming         [onConnected][78]: Grpc connection connect
2023-08-23 15:25:53.327 [traceId:] [TID: N/A]  INFO 1 --- [           main] com.alibaba.nacos.common.remote.client  [printIfInfoEnabled][63]: [e1146c19-413a-4f6f-8371-60242423f418] Register server push request handler:com.alibaba.nacos.common.remote.client.RpcClient$$Lambda$253/1690859824
2023-08-23 15:25:54.224 [traceId:] [TID: N/A]  INFO 1 --- [           main] o.s.b.a.e.web.EndpointLinksResolver     [<init>][58]: Exposing 7 endpoint(s) beneath base path ''
2023-08-23 15:25:54.539 [traceId:] [TID: N/A]  WARN 1 --- [           main] c.n.c.sources.URLConfigurationSource    [<init>][126]: No URLs will be polled as dynamic configuration sources.
2023-08-23 15:25:56.889 [traceId:] [TID: N/A]  INFO 1 --- [           main] com.alibaba.nacos.client.naming         [subscribe][167]: [SUBSCRIBE-SERVICE] service:***, group:DEFAULT_GROUP, clusters:DEFAULT 
2023-08-23 15:25:56.909 [traceId:] [TID: N/A] ERROR 1 --- [           main] c.a.cloud.nacos.discovery.NacosWatch    [start][127]: namingService subscribe failed, properties:NacosDiscoveryProperties{serverAddr='nacos-*****.****.svc.cluster.local:8848
', endpoint='', namespace='test', watchDelay=30000, logName='', service='', weight=1.0, clusterName='DEFAULT', group='DEFAULT_GROUP', namingLoadCacheAtStart='false', metadata={management.endpoints.web.base-path=/, preserved.register.source=SPRING_CLOUD}, registerEnabled=true, ip='**.**.**.**', networkInterface='', port=-1, secure=false, accessKey='', secretKey='', heartBeatInterval=null, heartBeatTimeout=null, ipDeleteTimeout=null}

com.alibaba.nacos.api.exception.NacosException: user not found!
	at com.alibaba.nacos.client.naming.remote.gprc.NamingGrpcClientProxy.requestToServer(NamingGrpcClientProxy.java:359)
	at com.alibaba.nacos.client.naming.remote.gprc.NamingGrpcClientProxy.doSubscribe(NamingGrpcClientProxy.java:311)
	at com.alibaba.nacos.client.naming.remote.gprc.NamingGrpcClientProxy.subscribe(NamingGrpcClientProxy.java:296)
	at com.alibaba.nacos.client.naming.remote.NamingClientProxyDelegate.subscribe(NamingClientProxyDelegate.java:173)
	at com.alibaba.nacos.client.naming.NacosNamingService.subscribe(NacosNamingService.java:405)
	at com.alibaba.cloud.nacos.discovery.NacosWatch.start(NacosWatch.java:123)

问题排查

  • 首先通过异常日志com.alibaba.nacos.api.exception.NacosException: user not found!可以看出是服务没有连接到nacos
  • nacos2.2.3是开启鉴权的，所以服务在连接nacos之前肯定先进行登录，调用/nacos/v1/auth/users/login接口
  • 再通过日志找到登录是报错的：[NacosClientAuthServiceImpl] login http request failed url
  • 日志打印出的nacos url是http://****.****.svc.cluster.local:8848
    /nacos/v1/auth/users/login, params: {username=nacos}, bodyMap: {password=****}
  • 且打印出errorMsg日志：errorMsg: Illegal character in authority at index 7:

问题定位

通过排查过程，通过 errorMsg: Illegal character in authority at index 7: 把问题最终定位到nacos url上;

前言中已经提到 "k8s在传入${NACOS_ADDR}时先对地址做了base64编码" ，所以把编码之后的地址解析出来发现k8s在编码时多加了换行；

这也是日志打印出nacos地址时，uri和接口地址不在同一行的原因，正确的url地址应该是 http://****.****.svc.cluster.local:8848/nacos/v1/auth/users/login 不会换行；

解决办法

重新对nacos url 进行正确的base64编码，修改${NACOS_ADDR}的base64值。

结束

至此，nacos连接异常问题解决。

相关推荐
秋饼1 分钟前
【手撕 @EnableAsync：揭秘 SpringBoot @Enable 注解的魔法开关】
java·spring boot·后端
Good_Starry5 分钟前
Java——正则表达式
java·开发语言·正则表达式
萤丰信息8 分钟前
开启园区“生命体”时代——智慧园区系统，定义未来的办公与生活
java·大数据·运维·数据库·人工智能·生活·智慧园区
IT 行者9 分钟前
微服务架构选型指南：中小型软件公司的理性思考
微服务·云原生·架构
欧洵.12 分钟前
Java.基于UDP协议的核心内容
java·开发语言·udp
xunyan623419 分钟前
第九章 JAVA常用类
java·开发语言
China_Yanhy35 分钟前
AWS S3 深度配置指南：每一栏每个选项有什么作用
java·数据库·aws
秃了也弱了。44 分钟前
FASTJSON库：阿里出品java界json解析库，使用与踩坑记录
java·开发语言·json
安全渗透Hacker1 小时前
参数未校验导致的DOS（服务拒绝）问题典型场景
java·安全·web安全·网络安全·安全性测试
oMcLin1 小时前
如何在 Manjaro Linux 上通过配置systemd服务管理，提升微服务架构的启动速度与资源效率
linux·微服务·架构
热门推荐
01GitHub 镜像站点02Labelme从安装到标注：零基础完整指南03安娜的档案(Anna’s Archive) 镜像网站/国内最新可访问入口（持续更新）04Linux下V2Ray安装配置指南05jdk21下载、安装（Windows、Linux、macOS）06【踩坑笔记】50系显卡适配的 PyTorch 安装07手把手教你通过Gemini3 pro 学生认证，白用一年，手慢无！08Opencode CLI 安装成功,但是启动失败09全球最强模型Grok4，国内已可免费使用！（附教程）10Claude Code Plan 模式完全指南：从入门到精通