ocpV4.2.1部署报这个错误ocp-server program health check [ERROR] failed to start 192.168.87.200 ocp-server

OceanBase
,
#1

image
image1011×695 32.9 KB

image
image1676×836 113 KB

obd.txt (238.1 KB)

#2

有没有大佬帮看一下

#3

～/ocp/log/的ocp-server.log提供一下

#4

ocp-server.log (37.9 KB)

#5

image
image2900×106 101 KB

但是看报错信息应该是时钟偏移的问题，需要配置一下服务器的时钟同步，保证部署 OCP 的机器和meta集群之间的时钟差 < 1s
最好去修改部署 OCP 的机器，让它和 OB 集群的时间同步

检查 NTP 偏移量

https://www.oceanbase.com/docs/common-oceanbase-database-cn-1000000000507671

1 个赞
#6

ocp-server的时间比metadb的时间快了12个小时

[2024-10-24 05:15:28.463] [19d20112-91e7-11ef-8355-000c2902cbe1] [DEBUG] -- exited code 0
[2024-10-24 05:15:28.464] [19d20112-91e7-11ef-8355-000c2902cbe1] [DEBUG] -- failed to start 192.168.87.200 ocp-server, remaining retries: 35
[2024-10-24 05:15:43.479] [19d20112-91e7-11ef-8355-000c2902cbe1] [DEBUG] -- 192.168.87.200 program health check
[2024-10-24 05:15:43.479] [19d20112-91e7-11ef-8355-000c2902cbe1] [DEBUG] -- root@192.168.87.200 execute: ls /proc/5323 
[2024-10-24 05:15:43.579] [19d20112-91e7-11ef-8355-000c2902cbe1] [DEBUG] -- exited code 0
[2024-10-24 05:15:43.580] [19d20112-91e7-11ef-8355-000c2902cbe1] [DEBUG] -- root@192.168.87.200 execute: bash -c 'cat /proc/net/{tcp*,udp*}' | awk -F' ' '{print $2,$10}' | grep '00000000:1F90' | awk -F' ' '{print $2}' | uniq 
[2024-10-24 05:15:43.706] [19d20112-91e7-11ef-8355-000c2902cbe1] [DEBUG] -- exited code 0
[2024-10-24 05:15:43.707] [19d20112-91e7-11ef-8355-000c2902cbe1] [DEBUG] -- failed to start 192.168.87.200 ocp-server, remaining retries: 34
[2024-10-24 05:15:58.722] [19d20112-91e7-11ef-8355-000c2902cbe1] [DEBUG] -- 192.168.87.200 program health check
[2024-10-24 05:15:58.722] [19d20112-91e7-11ef-8355-000c2902cbe1] [DEBUG] -- root@192.168.87.200 execute: ls /proc/5323 
[2024-10-24 05:15:58.820] [19d20112-91e7-11ef-8355-000c2902cbe1] [DEBUG] -- exited code 0
[2024-10-24 05:15:58.821] [19d20112-91e7-11ef-8355-000c2902cbe1] [DEBUG] -- root@192.168.87.200 execute: bash -c 'cat /proc/net/{tcp*,udp*}' | awk -F' ' '{print $2,$10}' | grep '00000000:1F90' | awk -F' ' '{print $2}' | uniq 
[2024-10-24 05:15:58.946] [19d20112-91e7-11ef-8355-000c2902cbe1] [DEBUG] -- exited code 0
[2024-10-24 05:15:58.946] [19d20112-91e7-11ef-8355-000c2902cbe1] [DEBUG] -- failed to start 192.168.87.200 ocp-server, remaining retries: 33
[2024-10-24 05:16:13.961] [19d20112-91e7-11ef-8355-000c2902cbe1] [DEBUG] -- 192.168.87.200 program health check
[2024-10-24 05:16:13.962] [19d20112-91e7-11ef-8355-000c2902cbe1] [DEBUG] -- root@192.168.87.200 execute: ls /proc/5323 
[2024-10-24 05:16:14.059] [19d20112-91e7-11ef-8355-000c2902cbe1] [DEBUG] -- exited code 0
[2024-10-24 05:16:14.059] [19d20112-91e7-11ef-8355-000c2902cbe1] [DEBUG] -- root@192.168.87.200 execute: bash -c 'cat /proc/net/{tcp*,udp*}' | awk -F' ' '{print $2,$10}' | grep '00000000:1F90' | awk -F' ' '{print $2}' | uniq 
[2024-10-24 05:16:14.258] [19d20112-91e7-11ef-8355-000c2902cbe1] [DEBUG] -- exited code 0
[2024-10-24 05:16:14.258] [19d20112-91e7-11ef-8355-000c2902cbe1] [DEBUG] -- failed to start 192.168.87.200 ocp-server, remaining retries: 32
[2024-10-24 05:16:29.273] [19d20112-91e7-11ef-8355-000c2902cbe1] [DEBUG] -- 192.168.87.200 program health check
[2024-10-24 05:16:29.273] [19d20112-91e7-11ef-8355-000c2902cbe1] [DEBUG] -- root@192.168.87.200 execute: ls /proc/5323 
[2024-10-24 05:16:29.364] [19d20112-91e7-11ef-8355-000c2902cbe1] [DEBUG] -- exited code 0
[2024-10-24 05:16:29.366] [19d20112-91e7-11ef-8355-000c2902cbe1] [DEBUG] -- root@192.168.87.200 execute: bash -c 'cat /proc/net/{tcp*,udp*}' | awk -F' ' '{print $2,$10}' | grep '00000000:1F90' | awk -F' ' '{print $2}' | uniq 
[2024-10-24 05:16:29.552] [19d20112-91e7-11ef-8355-000c2902cbe1] [DEBUG] -- exited code 0
[2024-10-24 05:16:29.553] [19d20112-91e7-11ef-8355-000c2902cbe1] [DEBUG] -- failed to start 192.168.87.200 ocp-server, remaining retries: 31
[2024-10-24 05:16:44.569] [19d20112-91e7-11ef-8355-000c2902cbe1] [DEBUG] -- 192.168.87.200 program health check
[2024-10-24 05:16:44.569] [19d20112-91e7-11ef-8355-000c2902cbe1] [DEBUG] -- root@192.168.87.200 execute: ls /proc/5323 
[2024-10-24 05:16:44.684] [19d20112-91e7-11ef-8355-000c2902cbe1] [DEBUG] -- exited code 2, error output:
[2024-10-24 05:16:44.685] [19d20112-91e7-11ef-8355-000c2902cbe1] [DEBUG] ls: cannot access /proc/5323: No such file or directory
[2024-10-24 05:16:44.686] [19d20112-91e7-11ef-8355-000c2902cbe1] [DEBUG] 
[2024-10-24 05:16:44.686] [19d20112-91e7-11ef-8355-000c2902cbe1] [ERROR] failed to start 192.168.87.200 ocp-server
[2024-10-24 05:16:44.687] [19d20112-91e7-11ef-8355-000c2902cbe1] [ERROR] start ocp-server failed
1 个赞
#7

我在装虚拟机的时候将时区改到国内是不是可以解决这个问题

#8

现在是选择的什么时区？ocp server和metadb是在同一台机器吗？什么操作系统及版本？

1 个赞
#9

美国纽约，都在一台机器上，ceantos7

#10

查询下meta租户的时区信息

obclient -hxxx -P2881 -uroot@ocp_meta -p’xxx’ -Doceanbase -A

show variables like ‘%zone%’;

image
image1028×328 56 KB

#11

timedatectl 也查看下

#12

image
image1675×787 53.4 KB

我这个好像有问题

#13

标点的问题，我重发了一遍

show variables like '%zone%';
#14

image
image

#15

timedatectl 这个是操作系统的命令

#16

image
image1019×731 54.4 KB

image
image1673×866 143 KB

我把时区切到中国又重装了一遍，好像还是这个样子

#17

image
image1100×816 35.4 KB

耶？成功了，好像就是时区的问题

#18

嗯，要保证ocp server 系统时区和ocp meta数据库时区一致，时间一致