社区版 ocp v4.4.1 接管obproxy 失败

AntTech_3PVK9N · 2026 年3 月 11 日 12:01

【使用环境】测试环境
【 OB or 其他组件】
【使用版本】 v4.4.1
【问题描述】

通过obclient 以及 ocp 凭据校验 功能. proxysys 的密码都是可以正常通过的. 但在接管obproxy主机时提示 “OBProxy 无法连接，请确认 OBProxy 是否正常运行或者 root@proxysys 密码是否正确”

凭据校验成功日志:

2026-03-11 11:44:33.526  INFO 1030685 --- [validate-credential-thread,2fb56ae4f01cb50b,9b29c897db24b5ae] c.o.o.s.c.CredentialServiceImpl          : Validating credential:ValidateCredentialParam(targetType=OB_PROXY, obJdbcCredentialProperty=ObJdbcCredentialProperty(clusterId=1000001, tenantId=null, clusterName=xxxxxx, tenantName=proxysys, username=root), sshCredentialProperty=null, agentCredentialProperty=null, batchSshValidateProperty=null, keystoreCredentialProperty=null, slsCredentialProperty=null, esCredentialProperty=null)
2026-03-11 11:44:33.527  INFO 1030685 --- [validate-credential-thread,2fb56ae4f01cb50b,9b29c897db24b5ae] c.o.o.s.c.v.OdpCredentialValidator       : Validating odp credential clusterName=xxxxxx|tenantName=proxysys|username=root
2026-03-11 11:44:33.528  INFO 1030685 --- [http-nio-0.0.0.0-8080-exec-78,2fb56ae4f01cb50b,104e21dc13a66a8f] c.o.o.s.c.v.CredentialValidateExecutor   : Await validate all credential success

添加obproxy时进行校验失败日志:

2026-03-11 11:30:19.274  INFO 1030685 --- [http-nio-0.0.0.0-8080-exec-99,63c5c9a261597e64,47fa1a126b495b79] c.o.o.s.c.trace.RequestTracingAspect     : API: [POST /api/v2/obproxy/clusters/1000001/takeOverPreCheck?id=1000001, client=127.0.0.1, traceId=63c5c9a261597e64, method=IterableResponse com.oceanbase.ocp.server.common.controller.ObproxyController.takeOverPreCheck(Long,ObproxyTakeOverPreCheckParam), args=1000001,ObproxyTakeOverPreCheckParam(hostInfoList=[ObproxyTakeOverPreCheckHostParam(hostId=7, sqlPort=2883, exporterPort=null, rpcPort=null, proxysysPasswd=null), ObproxyTakeOverPreCheckHostParam(hostId=6, sqlPort=2883, exporterPort=null, rpcPort=null, proxysysPasswd=null), ObproxyTakeOverPreCheckHostParam(hostId=5, sqlPort=2883, exporterPort=null, rpcPort=null, proxysysPasswd=null)], lbInstanceList=[]),]
2026-03-11 11:30:19.321  INFO 1030685 --- [ocp-schedules-20,8339c3967fa77c28,761be8049916bab9] c.o.ocp.monitor.OcpMonitorManager        : Refresh cached second exporters
2026-03-11 11:30:19.333  INFO 1030685 --- [http-nio-0.0.0.0-8080-exec-99,63c5c9a261597e64,47fa1a126b495b79] c.o.o.s.o.SystemOdpOperatorFactory       : connect obproxy 172.31.38.239 2883
2026-03-11 11:30:19.338  INFO 1030685 --- [http-nio-0.0.0.0-8080-exec-99,63c5c9a261597e64,47fa1a126b495b79] com.oceanbase.ocp.odpsdk.OdpOperator     : [odpsdk] sql: SHOW proxyconfig, args: []
2026-03-11 11:30:19.352  WARN 1030685 --- [http-nio-0.0.0.0-8080-exec-99,63c5c9a261597e64,47fa1a126b495b79] c.oceanbase.ocp.odpsdk.OdpJdbcOperator   : Failed to check odp connection Connection{driverClassName=com.oceanbase.jdbc.Driver, address=172.31.38.239, port=2883}, error is Failed to obtain JDBC Connection

OCP接管页面: