我用的是chrony,重启过了。
[root@obd02 ~]#
[root@obd02 ~]# clockdiff 192.168.56.149
.
host=192.168.56.149 rtt=750(187)ms/0ms delta=600ms/600ms Fri Jan 9 14:39:50 2026
[root@obd02 ~]#
[root@obd02 ~]#
我用的是chrony,重启过了。
[root@obd02 ~]#
[root@obd02 ~]# clockdiff 192.168.56.149
.
host=192.168.56.149 rtt=750(187)ms/0ms delta=600ms/600ms Fri Jan 9 14:39:50 2026
[root@obd02 ~]#
[root@obd02 ~]#
我的obd是4.0.0,也没有找到
vim /usr/obd/plugins/oceanbase-ce/x.x.x.x/start_check.py
vim ~/.obd/plugins/oceanbase-ce/x.x.x.x/start_check.py
[admin@obd01 ~]$ obd --version
OceanBase Deploy: 4.0.0
REVISION: 44b780d08efba6de1ce19e6d4a67631eba4cff24
BUILD_BRANCH: HEAD
BUILD_TIME: Nov 17 2025 14:36:56OURCE
Copyright (C) 2025 OceanBase
License Apache 2.0: Apache version 2 or later https://www.apache.org/licenses/LICENSE-2.0.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
[admin@obd01 ~]$
chronyc -a makestep
试试
服务端和客户段服务器的 /etc/chronyc.conf
发下看看
学习一下
服务端 192.168.56.149
[root@obd01 4.0.0.0]# cat /etc/chrony.conf
server 192.168.56.149 minpoll 4 maxpoll 6 iburst
maxslewrate 500
#server 1.centos.pool.ntp.org iburst
#server 2.centos.pool.ntp.org iburst
#server 3.centos.pool.ntp.org iburst
driftfile /var/lib/chrony/drift
makestep 1.0 3
rtcsync
#hwtimestamp *
#minsources 2
allow 192.168.56.0/24
#local stratum 10
#keyfile /etc/chrony.keys
logdir /var/log/chrony
#log measurements statistics tracking
[root@obd01 4.0.0.0]#
客户端192.168.56.150
[root@obd02 ~]# cat /etc/chrony.conf
server 192.168.56.149 minpoll 4 maxpoll 6 iburst
maxslewrate 500
#server 1.centos.pool.ntp.org iburst
#server 2.centos.pool.ntp.org iburst
#server 3.centos.pool.ntp.org iburst
driftfile /var/lib/chrony/drift
makestep 1.0 3
rtcsync
#hwtimestamp *
#minsources 2
allow 192.168.56.0/24
#local stratum 10
#keyfile /etc/chrony.keys
logdir /var/log/chrony
#log measurements statistics tracking
[root@obd02 ~]#
估计是哪里配置有问题吧
[root@obd02 ~]# chronyc -n tracking|grep Leap
Leap status : Not synchronised
[root@obd02 ~]#
[root@obd02 ~]#
问题解决了,还是chrony配置有问题。
[admin@obd01 ~]$ obd cluster start ocp_1
Get local repositories ok
Load cluster param plugin ok
Open ssh connection ok
Check before start ocp-server-ce ok
cluster scenario: None
Start observer ok
observer program health check ok
Connect to observer 192.168.56.149:2881 ok
obshell start ok
obshell program health check ok
start obproxy ok
obproxy program health check ok
Connect to obproxy ok
Start ocp-server-ce ok
ocp-server-ce program health check ok
Connect to ocp-server-ce ok
Connect to ocp-server-ce ok
±------------------------------------------------------------+
| ocp-server-ce |
±---------------------------±---------±-----------±-------+
| url | username | password | status |
±---------------------------±---------±-----------±-------+
| http://192.168.56.149:8080 | admin | ‘aaAA11__’ | active |
| http://192.168.56.150:8080 | admin | ‘aaAA11__’ | active |
±---------------------------±---------±-----------±-------+
Connect to observer 192.168.56.149:2881 ok
Wait for observer init ok
±-------------------------------------------------+
| oceanbase-ce |
±---------------±--------±-----±------±-------+
| ip | version | port | zone | status |
±---------------±--------±-----±------±-------+
| 192.168.56.149 | 4.2.1.8 | 2881 | zone1 | ACTIVE |
| 192.168.56.150 | 4.2.1.8 | 2881 | zone2 | ACTIVE |
±---------------±--------±-----±------±-------+
obclient -h192.168.56.149 -P2881 -uroot@sys -p’aaAA11__’ -Doceanbase -A
cluster unique id: df5a37ab-1e40-5a38-bbb8-607c8e5fb1fd-19b9ca86466-08010204
Connect to obproxy ok
±-------------------------------------------------------------------+
| obproxy-ce |
±---------------±-----±----------------±----------------±-------+
| ip | port | prometheus_port | rpc_listen_port | status |
±---------------±-----±----------------±----------------±-------+
| 192.168.56.150 | 2883 | 2884 | 2885 | active |
±---------------±-----±----------------±----------------±-------+
obclient -h192.168.56.150 -P2883 -uroot@proxysys -p’aaAA11__’ -Doceanbase -A
obshell program health check ok
display obshell dashboard ok
ocp_1 running
Trace ID: b99d2288-eddc-11f0-b8d9-000c29a1a8c4
If you want to view detailed obd logs, please run: obd display-trace b99d2288-eddc-11f0-b8d9-000c29a1a8c4
[admin@obd01 ~]$