oc企业版V3.2.4启动报错

【 使用环境 】测试环境
【 OB or 其他组件 】oceanbase-3.2.4.1-101000052023010822.el7.x86_64.rpm
【 使用版本 】oceanbase-3.2.4.1-101000052023010822.el7.x86_64.rpm
【问题描述】执行启动指令后报错
指令:cd /home/admin/oceanbase && /home/admin/oceanbase/bin/observer -i ens192 -P 2882 -p 2881 -z zone1 -d /home/admin/oceanbase/store/obdemo -r ‘192.168.88.254:2882:2881’ -c 10001 -n obdemo -o "system_memory=3G,min_full_resource_pool_memory=268435456,datafile_size=100G,config_additional_dir=/data/1/obdemo/etc3;/data/log1/obdemo/etc2"
报错:
[2025-02-24 15:34:35.331397] WDIAG [RS] ob_backup_lease_info_mgr.cpp:417 [9657][0][Y0-0000000000000000-0-0] [lt=6] [dc=0][errcode=-8002] failed to clean backup scheduler leader(ret=-8002, local_addr
=“192.168.88.254:2882”)
[2025-02-24 15:34:35.331404] WDIAG [RS] ob_backup_lease_info_mgr.cpp:396 [9657][0][Y0-0000000000000000-0-0] [lt=5] [dc=0][errcode=-8002] Failed to clean_backup_scheduler_leadear_v1(ret=-8002)
[2025-02-24 15:34:35.331424] INFO [RS] ob_backup_lease_info_mgr.cpp:400 [9657][0][Y0-0000000000000000-0-0] [lt=4] [dc=0] clean_backup_scheduler_leadear
(ret=-8002, local_addr_=“192.168.88.254:2882”)
[2025-02-24 15:34:35.331434] WDIAG [RS] ob_backup_lease_info_mgr.cpp:187 [9657][0][Y0-0000000000000000-0-0] [lt=8] [dc=0][errcode=-8002] failed to clean backup scheduler leader(ret=-8002)
[2025-02-24 15:34:35.331440] WDIAG [RS] ob_backup_lease_service.cpp:367 [9657][0][Y0-0000000000000000-0-0] [lt=4] [dc=0][errcode=-8002] failed to release lease(ret=-8002, next_round=1)
[2025-02-24 15:34:35.331445] INFO [RS] ob_server_fast_recovery.cpp:89 [9508][0][Y0-0000000000000000-0-0] [lt=2] [dc=0] stop zone recovery task mgr success
[2025-02-24 15:34:35.331453] INFO [RS] ob_server_fast_recovery.cpp:91 [9508][0][Y0-0000000000000000-0-0] [lt=4] [dc=0] stop zone server recovery machine success
[2025-02-24 15:34:35.331456] INFO [RS] ob_root_service.cpp:2216 [9508][0][Y0-0000000000000000-0-0] [lt=2] [dc=0] server fast recovery stop
[2025-02-24 15:34:35.331457] INFO [RS] ob_backup_lease_service.cpp:373 [9657][0][Y0-0000000000000000-0-0] [lt=5] [dc=0] clean_backup_leader_info_(ret=-8002, lease_info_={is_leader:false, lease_start_ts:0, leader_epoch:0, leader_takeover_ts:0, round:0, lease_epoch:0}, is_leader_changed=false)
[2025-02-24 15:34:35.331464] WDIAG [RS] ob_backup_lease_service.cpp:326 [9657][0][Y0-0000000000000000-0-0] [lt=6] [dc=0][errcode=-8002] failed to clean backup leader info(ret=-8002, next_round=1)
[2025-02-24 15:34:35.331470] WDIAG [RS] ob_backup_lease_service.cpp:275 [9657][0][Y0-0000000000000000-0-0] [lt=5] [dc=0][errcode=-8002] failed to renew lease(tmp_ret=-8002)
[2025-02-24 15:34:35.331696] INFO [RS] ob_dbms_job_master.cpp:323 [9508][0][Y0-0000000000000000-0-0] [lt=9] [dc=0] dbms job master stoped(ret=0, lbt()=“0x1142dc68 0xcd144ba 0xcd1446e 0x9fe2f93 0xd07dc70 0xd07cfa7 0xd078b35 0x6241d8b 0x7f795087b555 0x62407d9”)
[2025-02-24 15:34:35.331706] INFO [RS] ob_root_service.cpp:2218 [9508][0][Y0-0000000000000000-0-0] [lt=8] [dc=0] dbms job master stop
[2025-02-24 15:34:35.331854] INFO [RS] ob_dbms_sched_job_master.cpp:314 [9508][0][Y0-0000000000000000-0-0] [lt=3] [dc=0] dbms sched job master stoped(ret=0, lbt()=“0x1142dc68 0xcd35ac4 0xcd35a74 0x9fe2fa5 0xd07dc70 0xd07cfa7 0xd078b35 0x6241d8b 0x7f795087b555 0x62407d9”)
[2025-02-24 15:34:35.331865] INFO [RS] ob_root_service.cpp:2220 [9508][0][Y0-0000000000000000-0-0] [lt=10] [dc=0] dbms sched job master stop
[2025-02-24 15:34:35.331887] INFO [RS] ob_root_service.cpp:2222 [9508][0][Y0-0000000000000000-0-0] [lt=4] [dc=0] root_backup stop
[2025-02-24 15:34:35.331902] INFO [RS] ob_root_service.cpp:2224 [9508][0][Y0-0000000000000000-0-0] [lt=5] [dc=0] root_validate stop
[2025-02-24 15:34:35.331913] INFO [RS] ob_root_service.cpp:2226 [9508][0][Y0-0000000000000000-0-0] [lt=4] [dc=0] backup_data_clean stop
[2025-02-24 15:34:35.331932] INFO [RS] ob_root_service.cpp:2228 [9508][0][Y0-0000000000000000-0-0] [lt=13] [dc=0] backup auto delete stop
[2025-02-24 15:34:35.331941] INFO [RS] ob_root_service.cpp:2230 [9508][0][Y0-0000000000000000-0-0] [lt=2] [dc=0] backup archive log stop
[2025-02-24 15:34:35.331963] INFO [RS] ob_root_service.cpp:2232 [9508][0][Y0-0000000000000000-0-0] [lt=4] [dc=0] backup backupset stop
[2025-02-24 15:34:35.331978] INFO [RS] ob_rs_master_key_manager.cpp:85 [9508][0][Y0-0000000000000000-0-0] [lt=5] [dc=0] stop rs master key manager
[2025-02-24 15:34:35.331983] INFO [RS] ob_root_service.cpp:2234 [9508][0][Y0-0000000000000000-0-0] [lt=4] [dc=0] master key mgr stop
[2025-02-24 15:34:35.331987] WDIAG [RS] ob_root_service.cpp:2236 [9508][0][Y0-0000000000000000-0-0] [lt=3] [dc=0][errcode=0] global ctx timer stopped
【复现路径】
按照该文档步骤操作:https://blog.csdn.net/jycjyc/article/details/142557301)
【附件及日志】
[2025-02-24 15:35:28.349124] WDIAG [RS] ob_backup_lease_info_mgr.cpp:417 [9657][0][Y0-0000000000000000-0-0] [lt=3] [dc=0][errcode=-8002] failed to clean backup scheduler leader(ret=-8002, local_addr_=“192.168.88.254:2882”)
[2025-02-24 15:35:28.349130] WDIAG [RS] ob_backup_lease_info_mgr.cpp:396 [9657][0][Y0-0000000000000000-0-0] [lt=4] [dc=0][errcode=-8002] Failed to clean_backup_scheduler_leadear_v1(ret=-8002)
[2025-02-24 15:35:28.349136] INFO [RS] ob_backup_lease_info_mgr.cpp:400 [9657][0][Y0-0000000000000000-0-0] [lt=4] [dc=0] clean_backup_scheduler_leadear_(ret=-8002, local_addr_=“192.168.88.254:2882”)
[2025-02-24 15:35:28.349141] WDIAG [RS] ob_backup_lease_info_mgr.cpp:187 [9657][0][Y0-0000000000000000-0-0] [lt=4] [dc=0][errcode=-8002] failed to clean backup scheduler leader(ret=-8002)
[2025-02-24 15:35:28.349146] WDIAG [RS] ob_backup_lease_service.cpp:367 [9657][0][Y0-0000000000000000-0-0] [lt=3] [dc=0][errcode=-8002] failed to release lease(ret=-8002, next_round=1)
[2025-02-24 15:35:28.349157] INFO [RS] ob_backup_lease_service.cpp:373 [9657][0][Y0-0000000000000000-0-0] [lt=4] [dc=0] clean_backup_leader_info_(ret=-8002, lease_info_={is_leader:false, lease_start_ts:0, leader_epoch:0, leader_takeover_ts:0, round:0, lease_epoch:0}, is_leader_changed=false)
[2025-02-24 15:35:28.349162] WDIAG [RS] ob_backup_lease_service.cpp:326 [9657][0][Y0-0000000000000000-0-0] [lt=4] [dc=0][errcode=-8002] failed to clean backup leader info(ret=-8002, next_round=1)
[2025-02-24 15:35:28.349166] WDIAG [RS] ob_backup_lease_service.cpp:275 [9657][0][Y0-0000000000000000-0-0] [lt=3] [dc=0][errcode=-8002] failed to renew lease(tmp_ret=-8002)
[2025-02-24 15:35:29.349201] INFO [RS] ob_backup_lease_service.cpp:233 [9657][0][Y0-0000000000000000-0-0] [lt=2] [dc=0] [BACKUP_LEASE] stop_backup_schedul

【备注】基于 LLM 和开源文档 RAG 的论坛小助手已开放测试,在发帖时输入 [@论坛小助手] 即可召唤小助手,欢迎试用!@论坛小助手

1 个赞

您好,您提的这个技术问题可能牵涉到 OceanBase 企业版范围内的功能细节;针对此类问题,建议你通过以下方式寻求帮助:

  1. 如你所在的企业客户已签署 OceanBase 企业版销售合同,请你联系客户经理;

  2. 如你所在的企业客户尚未签署 OceanBase 企业版销售合同,你可通过OceanBase官网商务咨询页面留下你的联系方式,OceanBase企业版的业务顾问会在一个工作日内与你联系。

另外,我们欢迎你使用社区版,并在论坛/社群中分享你对社区版本的想法、经验和问题,与其他社区成员共同交流。

(小助手的答复已结束,如未能解决您的问题,请继续提问并等待其他同学的回复,谢谢!)

2 个赞

ps -ef |grep observer
netstat -ntlp |grep 288
看看

2 个赞

没有进程的,没启动成功
image

2 个赞

用的新机器第一次部署么,再执行这个看看

cd /home/admin/oceanbase/log grep “ret=-8002” rootservice.log* | grep “ob_backup_lease_service”

2 个赞

是新机器,这个执行结果也是空的

2 个赞

第一次启动失败,有试过再次启动吗

2 个赞

有的,在启动指令中添加不同参数,或者调整参数值,都有试过,但都没有启动成功 :joy:
cd /home/admin/oceanbase && /home/admin/oceanbase/bin/observer -i ens192 -P 2882 -p 2881 -z zone1 -d /home/admin/oceanbase/store/obdemo -r ‘192.168.88.254:2882:2881’ -c 10001 -n obdemo -o “system_memory=3G,__min_full_resource_pool_memory=268435456,datafile_size=100G,config_additional_dir=/data/1/obdemo/etc3;/data/log1/obdemo/etc2”

cd /home/admin/oceanbase && /home/admin/oceanbase/bin/observer -i ens192 -P 2882 -p 2881 -z zone1 -d /home/admin/oceanbase/store/obdemo -r ‘192.168.88.254:2882:2881’ -c 10001 -n obdemo -o “memory_limit=3G,cache_wash_threshold=1G,__min_full_resource_pool_memory=268435456,system_memory=3G,memory_chunk_cache_size=128M,cpu_count=4,net_thread_count=4,datafile_size=100G,stack_size=1536K,config_additional_dir=/data/1/obdemo/etc3;/data/log1/obdemo/etc2”

2 个赞

机器资源多大,memory_limit调整为10G或者更大再启动看下

2 个赞

一开始是10G,也是同样的报错;
资源应该是够的:

2 个赞

/data挂在/home下还是?我看你没有单独的数据盘

2 个赞

挂在根目录下

1 个赞

根目录只有七个g太小,并且datafile大小是预占用,你配的100g明显不够,目前看着就是磁盘大小不够,你可以扩容再启动试试。

1 个赞

不太好括了,home下还有400G空间,可以挂在到home路径下不?

1 个赞

看不大懂啊

也可以,你改下创建下目录,再改路径启动

还是有报错 :joy:
observer.log


rootservice.log

进程起来了吗

进程是有的,但是obclient无法连接,日志一直刷上面的报错信息

1 个赞

看日志还是启动配置问题,你环境清理下,重新来一遍,启动参数检查启动前也检查一遍。

1 个赞