obd部署单机运行一段时间节点停止

【 使用环境 】测试环境- 单机部署 OceanBase 数据库-
【 OB or 其他组件 】
【 使用版本 oceanbase-all-in-one-4.3.4_20241108.el7.x86_64】
【问题描述】obd部署单机节点运行一段时间节点显示停止,几分钟或者几十几分,怀疑过内存不够,设置过16G也一样必现,但是查询端口进程又存在。observer.log没发现error错误。到底是啥问题啊,好几个服务器装oceanbase都是这样。

配置文件是
mysql_port: 2881
rpc_port: 2882.
obshell_port: 2886
zone: zone1
cluster_id: 1
memory_limit: 6G
system_memory: 1G
datafile_size: 2G
datafile_next: 2G
datafile_maxsize: 20G
log_disk_size: 14G
cpu_count: 0
production_mode: false
enable_syslog_wf: true
max_syslog_file_count: 4

查看集群
obd cluster display observer
Get local repositories and plugins ok
Open ssh connection ok
Cluster status check ok
[WARN] 127.0.0.1 oceanbase-ce is stopped

查看2881端口
netstat -anp|grep 2881
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
tcp 1 0 127.0.0.1:16612 127.0.0.1:2881 CLOSE_WAIT 365313/obclient

【复现路径】执行命令 obd cluster deploy observer -c mini-local-example.yaml ,obd cluster start observer ;本地数据库客户端能正常连接至2881的数据库,但是过一段时间,可能是几分钟或者几十分钟,就无法连接了,到服务器上查看节点已停止,执行obclient -h127.0.0.1 -P2881 -uroot -p’xxxxxxxxx’ -Doceanbase -A 命令也无法连接,提示ERROR 2002 (HY000): Can’t connect to OceanBase server on ‘127.0.0.1’ (115)
【附件及日志】
[2024-11-19 11:10:25.443397] INFO New syslog file info: [address: “127.0.0.1:2882”, observer version: OceanBase_CE 4.3.4.0, revision: 100000162024110717-82547d6edc6ea98ba710e376a736a9a850499a06, sysname: Linux, os release: 5.4.0-1128-gcp, machine: x86_64, tz GMT offset: 08:00]
[2024-11-19 10:13:36.527423] WARN [SERVER] init_local_ip_and_devname (ob_server.cpp:2236) [273702][observer][T0][Y0-0000000000000001-0-0] [lt=81][errcode=-4187] the devname has been rewritten, and the new value comes from local_ip, old value: lo new value: lo local_ip: 127.0.0.1
[2024-11-19 10:13:42.010053] WARN [RPC_OBRPC] decode (ob_rpc_net_handler.cpp:214) [273843][RpcIO][T0][Y0-0000000000000000-0-0] [lt=15][errcode=0] The RPC packet delay is large. [suggestion] check clockdiff and tcp retransmission rate first, it maybe cost by clock skew or network delay. Further more, it may be caused by hardware failure or software failure of the machine
[2024-11-19 10:14:30.322257] WARN [RS] update_fail_count (ob_root_service.cpp:11654) [273782][RSAsyncTask0][T0][YB427F000001-0006273A97712DF0-0-0] [lt=14][errcode=-4752] rootservice start process has failure(msg=“rootservice start()/do_restart() has failure”, ret=-4012, ret=“OB_TIMEOUT”, fail_cnt=1)

[@论坛小助手]

1 个赞

根据文档库中的信息,您的问题可能涉及多个方面,以下是一些可能的原因及解决方案:

  1. 内存不足

    • 文档片段 3 提到,如果内存不足,obd 的启动会严格按照 MemAvailable 来计算内存。即使存在可以释放的缓存,您也可以尝试释放缓存:
      sudo sysctl -w vm.drop_caches=1
      # 或
      sudo echo 1 > /proc/sys/vm/drop_caches
      
    • 如果内存仍然不足,请调整 memory_limitsystem_memory。通常情况下,memory_limit/3 ≤ system_memory ≤ memory_limit/2。对于您的配置文件,建议将 memory_limit 设置为 16G,system_memory 设置为 5G。
  2. 端口冲突

    • 文档片段 1 提到,配置文件中存在端口冲突可能导致问题。请检查您的配置文件中的端口配置,确保没有冲突。您可以通过以下命令查看端口使用情况:
      netstat -anp | grep 2881
      netstat -anp | grep 2882
      netstat -anp | grep 2886
      
  3. 网络延迟或时钟偏移

    • 文档片段 10 中的日志提到,RPC 包延迟较大,建议检查时钟偏移和 TCP 重传率。这可能是由于网络延迟或硬件故障引起的。您可以使用以下命令检查时钟偏移:
      ntpdate -q pool.ntp.org
      
    • 如果时钟偏移较大,可以使用 NTP 服务同步时间:
      sudo ntpdate pool.ntp.org
      
  4. 日志文件分析

    • 您提到 observer.log 没有发现 error 错误,但日志中有一些警告信息。特别是关于 rootservice start process has failure 的警告,这可能表明根服务启动过程中出现了问题。您可以进一步查看 rootservice 相关的日志文件,例如 ob_root_service.log,以获取更多信息。
  5. 进程状态检查

    • 您提到端口进程仍然存在,但节点显示停止。请检查 observer 进程的状态:
      ps -ef | grep observer
      
    • 如果 observer 进程存在但状态异常,可以尝试重启 observer 进程:
      kill -9 `pidof observer`
      obd cluster start observer
      
  6. 系统资源限制

    • 检查系统的资源限制,确保没有达到系统资源的上限。您可以使用以下命令查看系统资源限制:
      ulimit -a
      

如果以上方法都无法解决问题,建议您联系 OceanBase 的技术支持人员进行进一步的排查。希望这些信息对您有所帮助。

更多信息请查看:

  1. 错误码
  2. 快速启动 OceanBase 数据库
  3. 单机部署 OceanBase 数据库
  4. OceanBase 安装部署工具 V2.4.0
  5. 使用 systemd 部署 OceanBase 数据库
  6. 少数派节点故障
  7. 查看节点
  8. 清理旧集群
  9. SYS 租户/RS 服务问题
  10. 4000 ~ 4499
  11. OceanBase 术语
1 个赞

rootservice.log.wf 没日志

当前状态
ps -ef | grep observer
um 346702 1 0 11:00 pts/0 00:00:00 /home/um/apps/base/oceanbase/observer/bin/obshell daemon --ip 127.0.0.1 --port 2886
um 346741 346702 0 11:00 pts/0 00:00:05 /home/um/apps/base/oceanbase/observer/bin/obshell server --ip 127.0.0.1 --port 2886
um 433604 277895 0 11:57 pts/0 00:00:00 grep --color=auto observer

1 个赞

执行
netstat -anp | grep 2881
netstat -anp | grep 2882
netstat -anp | grep 2886

就2882没有进程,那意味着2882的rpc_port挂了?所以这个单节点挂了的问题是这个吗?有遇过同意问题的大哥吗 :confounded:

1 个赞

OceanBase部署出现xxx lo fail to ping - #8,来自 逆流SD186vsmw_gaNjMwMzYyMDM2LjE3MzEyOTE0MDM._ga_T35KTM57DZ*MTczMTk5NDY0MS4yMi4xLjE3MzE5OTYxMDkuNDkuMC4w
看之前的帖子,部署的时候使用业务ip和对应网卡试试呢,好像用127.0.0.1和lo网卡会有问题

1 个赞

部署的时候有ip和devname配置项,指定一下外部ip

1 个赞

oceanbase-ce:

servers:

# Please don't use hostname, only IP can be supported

- 127.0.0.1
# devname: eth0

内网服务器部署的,一开始他能正常运行,我本地数据库客户端能正常连接,只是过一段时间那个节点出问题了,和这个配置有关系吗,我本地客户端连接是用内网服务器的ip,感觉不相关啊

1 个赞

上面日志显示,rootserver启动失败。
查一下你clockdiff命令是否在/usr/bin/下如果没有可以之间cp一个

提供一份全的 yaml文件。
建议修改部署使用外网ip

看日志报错的信息和lo网卡有关系,可能是127.0.0.1就是挂在lo网卡上的

/usr/bin/ 没有,我执行sudo apt install iputils-clockdiff 安装了一个有了,还是启动不久后就节点关闭了

oceanbase-ce:

servers:

# Please don't use hostname, only IP can be supported

- 127.0.0.1

global:

#  The working directory for OceanBase Database. OceanBase Database is started under this directory. This is a required field.

home_path: /home/sysadmin/apps/base/oceanbase/observer

# The directory for data storage. The default value is $home_path/store.

data_dir: /home/sysadmin/apps/base/oceanbase/data

# The directory for clog, ilog, and slog. The default value is the same as the data_dir value.

redo_dir: /home/sysadmin/apps/base/oceanbase/redo

# Starting from observer version 4.2, the network selection for the observer is based on the 'local_ip' parameter, and the 'devname' parameter is no longer mandatory.

# If the 'local_ip' parameter is set, the observer will first use this parameter for the configuration, regardless of the 'devname' parameter.

# If only the 'devname' parameter is set, the observer will use the 'devname' parameter for the configuration.

# If neither the 'devname' nor the 'local_ip' parameters are set, the 'local_ip' parameter will be automatically assigned the IP address configured above.

# devname: eth0

mysql_port: 2881 # External port for OceanBase Database. The default value is 2881. DO NOT change this value after the cluster is started.

rpc_port: 2882 # Internal port for OceanBase Database. The default value is 2882. DO NOT change this value after the cluster is started.

obshell_port: 2886 # Operation and maintenance port for Oceanbase Database. The default value is 2886. This parameter is valid only when the version of oceanbase-ce is 4.2.2.0 or later.

zone: zone1

cluster_id: 1

# please set memory limit to a suitable value which is matching resource.

memory_limit: 6G # The maximum running memory for an observer

system_memory: 1G # The reserved system memory. system_memory is reserved for general tenants. The default value is 30G.

datafile_size: 2G # Size of the data file.

datafile_next: 2G # the auto extend step. Please enter an capacity, such as 2G

datafile_maxsize: 20G # the auto extend max size. Please enter an capacity, such as 20G

log_disk_size: 14G # The size of disk space used by the clog files.

cpu_count: 0

production_mode: false

enable_syslog_wf: true # Print system logs whose levels are higher than WARNING to a separate log file. The default value is true.

max_syslog_file_count: 4 # The maximum number of reserved log files before enabling auto recycling. The default value is 0.

root_password: xxxxxxxxxxxxxxxxxxxxxxxxxxx

ifconfig看一下

我销毁集群再重启
启动后有两个告警
[2024-11-19 15:18:28.107347] WARN [SERVER] init_local_ip_and_devname (ob_server.cpp:2236) [749307][observer][T0][Y0-0000000000000001-0-0] [lt=91][errcode=-4187] the devname has been rewritten, and the new value comes from local_ip, old value: lo new value: lo local_ip: 127.0.0.1
[2024-11-19 15:19:20.790725] WARN [RS] update_fail_count (ob_root_service.cpp:11654) [749387][RSAsyncTask2][T0][YB427F000001-0006273ED9949D42-0-0] [lt=18][errcode=-4752] rootservice start process has failure(msg=“rootservice start()/do_restart() has failure”, ret=-4012, ret=“OB_TIMEOUT”, fail_cnt=1)
数据库是可以正常连接上的,在等几分钟重复断开和连接,测试是不是节点又停止了。
过了十分钟左右,节点又停止了,这次clockdiff有安装,查看observer.log.wf 错误还是之前那两个告警,election.log.wf和rootservice.log.wf都没有数据,搞不懂

br-1502e2c51048: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 172.28.0.1 netmask 255.255.0.0 broadcast 172.28.255.255
ether 02:42:b4:7a:1d:85 txqueuelen 0 (Ethernet)
RX packets 9296121 bytes 1033534547 (1.0 GB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 8463251 bytes 1143052806 (1.1 GB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

br-200e40b74abc: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 172.25.0.1 netmask 255.255.0.0 broadcast 172.25.255.255
ether 02:42:bb:6d:e1:b4 txqueuelen 0 (Ethernet)
RX packets 6447844 bytes 404062466 (404.0 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 5940704 bytes 575678513 (575.6 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

br-558fd1ed5122: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 172.22.0.1 netmask 255.255.0.0 broadcast 172.22.255.255
ether 02:42:68:9c:9d:21 txqueuelen 0 (Ethernet)
RX packets 14872665 bytes 924149450 (924.1 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 12847935 bytes 1010116950 (1.0 GB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

br-60c5d893c1e2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 172.20.0.1 netmask 255.255.0.0 broadcast 172.20.255.255
ether 02:42:39:a3:14:57 txqueuelen 0 (Ethernet)
RX packets 6931059 bytes 3739045591 (3.7 GB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 9104243 bytes 691545604 (691.5 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

br-8e3188bf3731: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 172.27.0.1 netmask 255.255.0.0 broadcast 172.27.255.255
ether 02:42:5f:61:5e:ce txqueuelen 0 (Ethernet)
RX packets 14131782 bytes 876552446 (876.5 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 12110535 bytes 952850259 (952.8 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

br-9ed284d11dfd: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 172.21.0.1 netmask 255.255.0.0 broadcast 172.21.255.255
ether 02:42:35:af:60:dc txqueuelen 0 (Ethernet)
RX packets 10800792 bytes 1366146795 (1.3 GB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 17029300 bytes 1898767294 (1.8 GB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

br-afed950abd22: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 172.24.0.1 netmask 255.255.0.0 broadcast 172.24.255.255
ether 02:42:dc:70:49:8e txqueuelen 0 (Ethernet)
RX packets 50498453 bytes 111162040350 (111.1 GB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 43698707 bytes 4229720765 (4.2 GB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

br-d5ddb4e87638: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 172.19.0.1 netmask 255.255.0.0 broadcast 172.19.255.255
ether 02:42:b0:96:de:54 txqueuelen 0 (Ethernet)
RX packets 15859311 bytes 1910337373 (1.9 GB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 18867940 bytes 1951552035 (1.9 GB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

br-f8be4ab07ee8: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 172.18.0.1 netmask 255.255.0.0 broadcast 172.18.255.255
ether 02:42:e4:d9:76:80 txqueuelen 0 (Ethernet)
RX packets 342771 bytes 2262699518 (2.2 GB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 277169 bytes 631460776 (631.4 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

br-f8cb923f175e: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 172.26.0.1 netmask 255.255.0.0 broadcast 172.26.255.255
ether 02:42:7a:c6:1f:9c txqueuelen 0 (Ethernet)
RX packets 17279747 bytes 1050589854 (1.0 GB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 15240788 bytes 1169926855 (1.1 GB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

docker0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255
ether 02:42:13:d6:68:18 txqueuelen 0 (Ethernet)
RX packets 17467131 bytes 1629174526 (1.6 GB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 26015951 bytes 2662898321 (2.6 GB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

ens18: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.224.169 netmask 255.255.255.0 broadcast 192.168.224.255
inet6 fe80::be24:11ff:fe3f:e8bc prefixlen 64 scopeid 0x20
ether bc:24:11:3f:e8:bc txqueuelen 1000 (Ethernet)
RX packets 159788347 bytes 36548675163 (36.5 GB)
RX errors 0 dropped 654482 overruns 0 frame 0
TX packets 116770355 bytes 169991418759 (169.9 GB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
loop txqueuelen 1000 (Local Loopback)
RX packets 410211 bytes 170235073 (170.2 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 410211 bytes 170235073 (170.2 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

tailscale0: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1280
inet 100.64.0.1 netmask 255.255.255.255 destination 100.64.0.1
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 500 (UNSPEC)
RX packets 85744358 bytes 12220097679 (12.2 GB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 87577068 bytes 44330887880 (44.3 GB)
TX errors 0 dropped 7113 overruns 0 carrier 0 collisions 0

veth06d73ca: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
ether 0a:31:85:4f:db:07 txqueuelen 0 (Ethernet)
RX packets 4155341 bytes 2227017161 (2.2 GB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 4518332 bytes 1981706146 (1.9 GB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

veth0af4b09: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
ether c2:03:6e:1d:35:55 txqueuelen 0 (Ethernet)
RX packets 6931059 bytes 3836080417 (3.8 GB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 9104243 bytes 691545604 (691.5 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

veth1bdc4c6: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
ether d2:41:ab:71:54:80 txqueuelen 0 (Ethernet)
RX packets 342771 bytes 2267498312 (2.2 GB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 277169 bytes 631460776 (631.4 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

veth22aa4c7: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
ether f6:bf:02:28:02:a7 txqueuelen 0 (Ethernet)
RX packets 12898208 bytes 953764172 (953.7 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 11000039 bytes 828597188 (828.5 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

veth273c71e: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
ether ea:52:4b:ac:80:4b txqueuelen 0 (Ethernet)
RX packets 1763300 bytes 268255523 (268.2 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 963392 bytes 384348990 (384.3 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

veth2aec0e8: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
ether 32:32:87:02:5c:c8 txqueuelen 0 (Ethernet)
RX packets 14029696 bytes 1066381952 (1.0 GB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 12026185 bytes 945851588 (945.8 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

veth2e6e1e0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
ether 7e:af:a1:7f:6e:7b txqueuelen 0 (Ethernet)
RX packets 6447844 bytes 494332282 (494.3 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 5940704 bytes 575678513 (575.6 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

veth3a811d9: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
ether 6e:c3:51:0b:ca:74 txqueuelen 0 (Ethernet)
RX packets 1527877 bytes 543355523 (543.3 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 2860583 bytes 556717996 (556.7 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

veth692a00c: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
ether 1a:84:b4:d9:90:bf txqueuelen 0 (Ethernet)
RX packets 20706684 bytes 109268902903 (109.2 GB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 21962086 bytes 2008326432 (2.0 GB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

veth6e99d37: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
ether 32:ee:6e:28:96:59 txqueuelen 0 (Ethernet)
RX packets 5112968 bytes 486263860 (486.2 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 2676442 bytes 367087754 (367.0 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

veth748833b: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
ether e6:04:33:29:aa:0b txqueuelen 0 (Ethernet)
RX packets 9296105 bytes 1163678428 (1.1 GB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 8463238 bytes 1143046633 (1.1 GB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

veth7ccb072: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
ether 02:67:2a:35:e3:75 txqueuelen 0 (Ethernet)
RX packets 17279747 bytes 1292506312 (1.2 GB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 15240788 bytes 1169926855 (1.1 GB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

veth8edad42: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
ether 2a:9f:56:5b:66:10 txqueuelen 0 (Ethernet)
RX packets 7258532 bytes 735661904 (735.6 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 5643909 bytes 609420548 (609.4 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

vetha4a940f: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
ether 42:bf:58:04:08:7d txqueuelen 0 (Ethernet)
RX packets 15859311 bytes 2132367727 (2.1 GB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 18867940 bytes 1951552035 (1.9 GB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

vethb88add2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
ether 2a:9d:94:84:a7:d1 txqueuelen 0 (Ethernet)
RX packets 16 bytes 1813 (1.8 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 14 bytes 6215 (6.2 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

vethb8b78ad: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
ether 06:2a:f7:d8:7c:5f txqueuelen 0 (Ethernet)
RX packets 14749331 bytes 1122393758 (1.1 GB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 12744845 bytes 1001430374 (1.0 GB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

vethccf3b09: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
ether 5a:07:12:ca:d9:17 txqueuelen 0 (Ethernet)
RX packets 4531598 bytes 426297589 (426.2 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 2425886 bytes 418177662 (418.1 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

vethce3de57: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
ether 26:ba:40:62:03:2b txqueuelen 0 (Ethernet)
RX packets 15263269 bytes 3368713196 (3.3 GB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 20596015 bytes 3865978816 (3.8 GB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

vethd96b5ed: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
ether b2:c9:87:f2:ae:ce txqueuelen 0 (Ethernet)
RX packets 17463805 bytes 1873392241 (1.8 GB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 26013506 bytes 2662669284 (2.6 GB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

集群铲掉使用obd demo部署或者obd web白屏化部署试试。

obd web白屏化部署,一样出现同样的问题,部署成功,部署后一阵是正常的,后面就出现停用了

observer日志发一份完整的看看,~/oceanbase/log/

log.zip (35.9 MB)

防火墙关闭了么