启动集群，obd cluster start zbbob，obproxy 一直处于检查中

OceanBase 技术问题
#1

Get local repositories ok
Load cluster param plugin ok
Open ssh connection ok
cluster scenario: htap
Start observer ok
observer program health check ok
Connect to observer 192.168.1.61:2881 ok
obshell start ok
obshell program health check ok
start obproxy ok
obproxy program health check 一直处于这里检查中。。。

1 个赞
#4

麻烦提供一份obd日志
~/.obd/log/obd.log

#5

[2025-10-23 16:09:12.146] [6b865b42-afe7-11f0-b517-000c29584913] [DEBUG] – exited code 0
[2025-10-23 16:09:12.146] [6b865b42-afe7-11f0-b517-000c29584913] [DEBUG] – admin@192.168.1.63 delete env LD_LIBRARY_PATH
[2025-10-23 16:09:12.146] [6b865b42-afe7-11f0-b517-000c29584913] [DEBUG] – admin@192.168.1.63 execute: ps -aux | grep -e ‘/home/admin/obproxy/bin/obproxy -o obproxy_sys_password=**,enable_obproxy_rpc_service=True,enable_strict_kernel_release=False,enable_cluster_checkout=False,skip_proxy_sys_private_check=True --listen_port 2883 --prometheus_listen_port 2884 --rs_list 192.168.1.61:2881;192.168.1.62:2881;192.168.1.63:2881 --cluster_name zbbobce --rpc_listen_port 2885$’ | grep -v grep | awk ‘{print $2}’ > /home/admin/obproxy/run/obproxy-192.168.1.63-2883.pid
[2025-10-23 16:09:12.532] [6b865b42-afe7-11f0-b517-000c29584913] [DEBUG] – exited code 0
[2025-10-23 16:09:12.608] [6b865b42-afe7-11f0-b517-000c29584913] [DEBUG] - sub start ref count to 0
[2025-10-23 16:09:12.608] [6b865b42-afe7-11f0-b517-000c29584913] [DEBUG] - export start
[2025-10-23 16:09:12.608] [6b865b42-afe7-11f0-b517-000c29584913] [DEBUG] - plugin obproxy-ce-py_script_start-3.1.0 result: True
[2025-10-23 16:09:12.608] [6b865b42-afe7-11f0-b517-000c29584913] [DEBUG] - Searching health_check plugin for components …
[2025-10-23 16:09:12.608] [6b865b42-afe7-11f0-b517-000c29584913] [DEBUG] - Searching health_check plugin for obproxy-ce-4.3.5.0-3.el7-f17b277b681adb1c86bfc3cfda369ad88896da9d
[2025-10-23 16:09:12.608] [6b865b42-afe7-11f0-b517-000c29584913] [DEBUG] - Found for obproxy-ce-py_script_health_check-3.1.0 for obproxy-ce-4.3.5.0
[2025-10-23 16:09:12.608] [6b865b42-afe7-11f0-b517-000c29584913] [DEBUG] - Call plugin obproxy-ce-py_script_health_check-3.1.0 for obproxy-ce-4.3.5.0-3.el7-f17b277b681adb1c86bfc3cfda369ad88896da9d
[2025-10-23 16:09:12.609] [6b865b42-afe7-11f0-b517-000c29584913] [DEBUG] - import health_check
[2025-10-23 16:09:12.610] [6b865b42-afe7-11f0-b517-000c29584913] [DEBUG] - add health_check ref count to 1
[2025-10-23 16:09:12.610] [6b865b42-afe7-11f0-b517-000c29584913] [INFO] obproxy program health check
[2025-10-23 16:09:12.611] [6b865b42-afe7-11f0-b517-000c29584913] [DEBUG] – 192.168.1.61 program health check
[2025-10-23 16:09:12.611] [6b865b42-afe7-11f0-b517-000c29584913] [DEBUG] – admin@192.168.1.61 execute: cat /home/admin/obproxy/run/obproxy-192.168.1.61-2883.pid
[2025-10-23 16:09:12.802] [6b865b42-afe7-11f0-b517-000c29584913] [DEBUG] – exited code 0
[2025-10-23 16:09:12.802] [6b865b42-afe7-11f0-b517-000c29584913] [DEBUG] – admin@192.168.1.61 execute: bash -c 'cat /proc/net/{tcp,udp}’ | awk -F’ ’ ‘{if($4==“0A”) print $2,$4,$10}’ | grep ‘:0B43’ | awk -F’ ’ ‘{print $3}’ | uniq
[2025-10-23 16:09:13.393] [6b865b42-afe7-11f0-b517-000c29584913] [DEBUG] – exited code 0
[2025-10-23 16:09:13.394] [6b865b42-afe7-11f0-b517-000c29584913] [DEBUG] – failed to start 192.168.1.61 obproxy, remaining retries: 599
[2025-10-23 16:09:13.394] [6b865b42-afe7-11f0-b517-000c29584913] [DEBUG] – 192.168.1.62 program health check
[2025-10-23 16:09:13.394] [6b865b42-afe7-11f0-b517-000c29584913] [DEBUG] – admin@192.168.1.62 execute: cat /home/admin/obproxy/run/obproxy-192.168.1.62-2883.pid
[2025-10-23 16:09:13.421] [6b865b42-afe7-11f0-b517-000c29584913] [DEBUG] – exited code 0
[2025-10-23 16:09:13.421] [6b865b42-afe7-11f0-b517-000c29584913] [DEBUG] – admin@192.168.1.62 execute: bash -c 'cat /proc/net/{tcp,udp}’ | awk -F’ ’ ‘{if($4==“0A”) print $2,$4,$10}’ | grep ‘:0B43’ | awk -F’ ’ ‘{print $3}’ | uniq
[2025-10-23 16:09:13.492] [6b865b42-afe7-11f0-b517-000c29584913] [DEBUG] – exited code 0
[2025-10-23 16:09:13.493] [6b865b42-afe7-11f0-b517-000c29584913] [DEBUG] – admin@192.168.1.62 execute: ls -l /proc/70090/fd/ |grep -E ‘socket:[(190089|190092)]’
[2025-10-23 16:09:13.584] [6b865b42-afe7-11f0-b517-000c29584913] [DEBUG] – exited code 0
[2025-10-23 16:09:13.584] [6b865b42-afe7-11f0-b517-000c29584913] [DEBUG] – admin@192.168.1.62 execute: pid=cat /home/admin/obproxy/run/obproxyd-192.168.1.62-2883.pid && ls /proc/$pid
[2025-10-23 16:09:13.659] [6b865b42-afe7-11f0-b517-000c29584913] [DEBUG] – exited code 1, error output:
[2025-10-23 16:09:13.659] [6b865b42-afe7-11f0-b517-000c29584913] [DEBUG] cat: /home/admin/obproxy/run/obproxyd-192.168.1.62-2883.pid: 没有那个文件或目录
[2025-10-23 16:09:13.659] [6b865b42-afe7-11f0-b517-000c29584913] [DEBUG]
[2025-10-23 16:09:13.660] [6b865b42-afe7-11f0-b517-000c29584913] [DEBUG] – admin@192.168.1.62 execute: echo 70090 > /home/admin/obproxy/run/obproxy-192.168.1.62-2883.pid
[2025-10-23 16:09:13.729] [6b865b42-afe7-11f0-b517-000c29584913] [DEBUG] – exited code 0
[2025-10-23 16:09:13.828] [6b865b42-afe7-11f0-b517-000c29584913] [DEBUG] - local execute: rsync -h
[2025-10-23 16:09:13.831] [6b865b42-afe7-11f0-b517-000c29584913] [DEBUG] - exited code 0
[2025-10-23 16:09:13.831] [6b865b42-afe7-11f0-b517-000c29584913] [DEBUG] - admin@192.168.1.62 execute: rsync -h
[2025-10-23 16:09:13.872] [6b865b42-afe7-11f0-b517-000c29584913] [DEBUG] - exited code 0
[2025-10-23 16:09:13.872] [6b865b42-afe7-11f0-b517-000c29584913] [DEBUG] - current remote_transporter RemoteTransporter.RSYNC
[2025-10-23 16:09:13.872] [6b865b42-afe7-11f0-b517-000c29584913] [DEBUG] – admin@192.168.1.62 execute: mkdir -p /home/admin/obproxy
[2025-10-23 16:09:13.949] [6b865b42-afe7-11f0-b517-000c29584913] [DEBUG] – exited code 0
[2025-10-23 16:09:13.949] [6b865b42-afe7-11f0-b517-000c29584913] [DEBUG] – send /home/admin/.obd/plugins/obproxy-ce/3.1.0/obproxyd.sh to /home/admin/obproxy/obproxyd.sh by rsync
[2025-10-23 16:09:13.949] [6b865b42-afe7-11f0-b517-000c29584913] [DEBUG] – local execute: yes | rsync -a -W -L -e “ssh -o StrictHostKeyChecking=no -i /home/admin/.ssh/id_rsa.pub -p 22” /home/admin/.obd/plugins/obproxy-ce/3.1.0/obproxyd.sh admin@192.168.1.62:/home/admin/obproxy/obproxyd.sh

#6

看日志没有报错，麻烦发一份完整的附件日志吧。
obd版本是多少

#7

yaml文件也麻烦提供一份，看下是否是proxy的参数设置有问题导致

#9

obd 版本是OceanBase Deploy: 3.6.0 ，这次部署用的最新版本的all in one 社区版

#10

image
这两个参数需要加上，且ob的yaml文件log盘建议设置为内存的3-4倍大小。

#11

感觉像磁盘或内存资源不足导致的

#12

这两个参数加上了，然后log size 也设置大了，依旧卡start obproxy ok
obproxy program health check 。。。。。

我server服务器都是12GB 启动过程中用了2.2GB ，中控机也是8GB ，才用了2G。

#13

学习一下。

#14

obproxy program health check 这一步是做obproxy的健康检查，看是否可用。可能还是ODP不可用导致

#15

参数加上后执行的是redeploy么。重新部署一下看看如果还是报错麻烦提供一份obproxy的日志