【 使用环境 】生产环境
【 OB or 其他组件 】OB组件
【 使用版本 】4.5.0
【问题描述】obd cluster edit-config culster时vim报错
【复现路径】无其他操作
【附件及日志】
[root@10-35-10-132 oceanbase]# obd cluster edit-config CLUSTER
Search param plugin and load ok
/usr/bin/vim: symbol lookup error: /lib64/libncurses.so.6: undefined symbol: _nc_safe_fopen
Search param plugin and load ok
Parameter check ok
Deploy "CLUSTER" config unchange
Trace ID: bd3b6a7c-93d5-11f1-82ea-005056aed794
If you want to view detailed obd logs, please run: obd display-trace bd3b6a7c-93d5-11f1-82ea-005056aed794
[2026-08-09 17:36:05.664] [DEBUG] - import get_generate_keys
[2026-08-09 17:36:05.664] [DEBUG] - add get_generate_keys ref count to 1
[2026-08-09 17:36:05.665] [DEBUG] - sub get_generate_keys ref count to 0
[2026-08-09 17:36:05.665] [DEBUG] - export get_generate_keys
[2026-08-09 17:36:05.665] [DEBUG] - plugin alertmanager-py_script_workflow_get_generate_keys-0.1 result: True
[2026-08-09 17:36:05.665] [DEBUG] - Found for alertmanager-py_script_workflow_get_generate_keys-0.1 for alertmanager-0.1
[2026-08-09 17:36:05.666] [DEBUG] - IP oceanbase-ce-4.6.0.0-100000162026071511.el8-abd4e73500fd4fe40071427b1e879e45b9066d51 param check
[2026-08-09 17:36:05.667] [DEBUG] - IP obproxy-ce-4.3.6.1-2.el8-ce7f4ebf7170fd7f0d3ebbaa31904c528a42a69a param check
[2026-08-09 17:36:05.667] [DEBUG] - IP obagent-4.2.6-100000152026051118.el8-57b6d08f6db0932eeadd06d112e5a8a555b5f059 param check
[2026-08-09 17:36:05.668] [DEBUG] - IP ob-configserver-1.0.0-2.el8-664f93205c913d5dc84e0779d565768fd60f1d5e param check
[2026-08-09 17:36:05.668] [DEBUG] - IP prometheus-2.37.1-10000102022110211.el8-e4f8a3e784512fca75bf1b3464247d1f31542cb9 param check
[2026-08-09 17:36:05.668] [DEBUG] - IP grafana-7.5.17-1-1bf1f338d3a3445d8599dc6902e7aeed4de4e0d6 param check
[2026-08-09 17:36:05.668] [DEBUG] - IP alertmanager-0.28.1-32025073111.el8-13b24d72fe5296a68a9dca70193ed693f5697a5e param check
[2026-08-09 17:36:05.768] [DEBUG] - configure change check
[2026-08-09 17:36:05.768] [INFO] Deploy "CLUSTER" config unchange
[2026-08-09 17:36:05.769] [DEBUG] - share lock /root/.obd/lock/mirror_and_repo release, count 6
[2026-08-09 17:36:05.770] [DEBUG] - share lock /root/.obd/lock/mirror_and_repo release, count 5
[2026-08-09 17:36:05.770] [DEBUG] - share lock /root/.obd/lock/mirror_and_repo release, count 4
[2026-08-09 17:36:05.770] [DEBUG] - share lock /root/.obd/lock/mirror_and_repo release, count 3
[2026-08-09 17:36:05.770] [DEBUG] - share lock /root/.obd/lock/mirror_and_repo release, count 2
[2026-08-09 17:36:05.770] [DEBUG] - share lock /root/.obd/lock/mirror_and_repo release, count 1
[2026-08-09 17:36:05.770] [DEBUG] - share lock /root/.obd/lock/mirror_and_repo release, count 0
[2026-08-09 17:36:05.770] [DEBUG] - unlock /root/.obd/lock/mirror_and_repo
[2026-08-09 17:36:05.771] [DEBUG] - exclusive lock /root/.obd/lock/deploy_CLUSTER release, count 0
[2026-08-09 17:36:05.771] [DEBUG] - unlock /root/.obd/lock/deploy_CLUSTER
[2026-08-09 17:36:05.771] [DEBUG] - share lock /root/.obd/lock/global release, count 0
[2026-08-09 17:36:05.771] [DEBUG] - unlock /root/.obd/lock/global
[2026-08-09 17:36:05.771] [INFO] Trace ID: bd3b6a7c-93d5-11f1-82ea-005056aed794
[2026-08-09 17:36:05.771] [INFO] If you want to view detailed obd logs, please run: obd display-trace bd3b6a7c-93d5-11f1-82ea-005056aed794