-
Notifications
You must be signed in to change notification settings - Fork 135
Closed
Description
Description
Centos 7 系统 使用 all in one(v4.3.5) 安装 obd 后, deploy 的时候一直出现下面的错误((3.1.2 和 3.2.0) 同样的错误):
# obd cluster deploy obtest -f -c deploy.yaml
+--------------------------------------------------------------------------------------------+
| Packages |
+--------------+---------+------------------------+------------------------------------------+
| Repository | Version | Release | Md5 |
+--------------+---------+------------------------+------------------------------------------+
| oceanbase-ce | 4.3.5.1 | 101000042025031818.el7 | 8826bc816ae660198f9ca5fd7e96d93c1ce4fc84 |
+--------------+---------+------------------------+------------------------------------------+
Repository integrity check ok
Load param plugin ok
Open ssh connection ok
Initializes observer work home x
[ERROR] oceanbase-ce-py_script_init-3.1.0 RuntimeError: 'home_path'
[WARN] oceanbase-ce-py_script_init-3.1.0 has animation not been closed
See https://www.oceanbase.com/product/ob-deployer/error-codes .
Trace ID: 91317882-20f3-11f0-b6d9-00163e2c61ca
If you want to view detailed obd logs, please run: obd display-trace 91317882-20f3-11f0-b6d9-00163e2c61ca
display-trace 信息:
[2025-04-24 18:04:54.518] [ERROR] oceanbase-ce-py_script_init-3.1.0 RuntimeError: 'home_path'
[2025-04-24 18:04:54.518] [ERROR] Traceback (most recent call last):
[2025-04-24 18:04:54.518] [ERROR] File "core.py", line 1778, in deploy_cluster
[2025-04-24 18:04:54.518] [ERROR] File "core.py", line 1815, in _deploy_cluster
[2025-04-24 18:04:54.518] [ERROR] File "core.py", line 246, in run_workflow
[2025-04-24 18:04:54.518] [ERROR] File "core.py", line 288, in run_plugin_template
[2025-04-24 18:04:54.518] [ERROR] File "core.py", line 336, in call_plugin
[2025-04-24 18:04:54.518] [ERROR] File "_plugin.py", line 348, in __call__
[2025-04-24 18:04:54.518] [ERROR] File "_plugin.py", line 304, in _new_func
[2025-04-24 18:04:54.518] [ERROR] File "/root/.obd/plugins/oceanbase-ce/3.1.0/init.py", line 85, in init
[2025-04-24 18:04:54.518] [ERROR] home_path = server_config['home_path']
[2025-04-24 18:04:54.518] [ERROR] KeyError: 'home_path'
[2025-04-24 18:04:54.518] [ERROR]
[2025-04-24 18:04:54.518] [DEBUG] - sub init ref count to 0
[2025-04-24 18:04:54.518] [DEBUG] - export init
[2025-04-24 18:04:54.518] [WARNING] oceanbase-ce-py_script_init-3.1.0 has animation not been closed
[2025-04-24 18:04:54.519] [DEBUG] - plugin oceanbase-ce-py_script_init-3.1.0 result: False
[2025-04-24 18:04:54.648] [INFO] [ERROR] oceanbase-ce-py_script_init-3.1.0 RuntimeError: 'home_path'
[2025-04-24 18:04:54.648] [INFO] [WARN] oceanbase-ce-py_script_init-3.1.0 has animation not been closed
[2025-04-24 18:04:54.648] [INFO]
[2025-04-24 18:04:54.648] [INFO] See https://www.oceanbase.com/product/ob-deployer/error-codes .
没有找到这里的 RuntimeError: 'home_path' 具体到底是什么错误? 是配置有什么不对吗?
home_path: /home/admin/
data_dir: /export/observer/data
redo_dir: export/observer/redo
感谢回答!
=======================
检查了下是因为配置错误, servers 没有对应上相应的配置. 关闭此问题
Description
After using all in one(v4.3.5) to install obd in Centos 7 system, the following errors are constantly occurring when deploying ((3.1.2 and 3.2.0)):
# obd cluster deploy obtest -f -c deploy.yaml
+--------------------------------------------------------------------------------------------+
| Packages |
+--------------+---------+------------------------+------------------------------------------+
| Repository | Version | Release | Md5 |
+--------------+---------+------------------------+------------------------------------------+
| oceanbase-ce | 4.3.5.1 | 101000042025031818.el7 | 8826bc816ae660198f9ca5fd7e96d93c1ce4fc84 |
+--------------+---------+------------------------+------------------------------------------+
Repository integrity check ok
Load param plugin ok
Open ssh connection ok
Initializes observer work home x
[ERROR] oceanbase-ce-py_script_init-3.1.0 RuntimeError: 'home_path'
[WARN] oceanbase-ce-py_script_init-3.1.0 has animation not been closed
See https://www.oceanbase.com/product/ob-deployer/error-codes.
Trace ID: 91317882-20f3-11f0-b6d9-00163e2c61ca
If you want to view detailed obd logs, please run: obd display-trace 91317882-20f3-11f0-b6d9-00163e2c61ca
display-trace information:
[2025-04-24 18:04:54.518] [ERROR] oceanbase-ce-py_script_init-3.1.0 RuntimeError: 'home_path'
[2025-04-24 18:04:54.518] [ERROR] Traceback (most recent call last):
[2025-04-24 18:04:54.518] [ERROR] File "core.py", line 1778, in deploy_cluster
[2025-04-24 18:04:54.518] [ERROR] File "core.py", line 1815, in _deploy_cluster
[2025-04-24 18:04:54.518] [ERROR] File "core.py", line 246, in run_workflow
[2025-04-24 18:04:54.518] [ERROR] File "core.py", line 288, in run_plugin_template
[2025-04-24 18:04:54.518] [ERROR] File "core.py", line 336, in call_plugin
[2025-04-24 18:04:54.518] [ERROR] File "_plugin.py", line 348, in __call__
[2025-04-24 18:04:54.518] [ERROR] File "_plugin.py", line 304, in _new_func
[2025-04-24 18:04:54.518] [ERROR] File "/root/.obd/plugins/oceanbase-ce/3.1.0/init.py", line 85, in init
[2025-04-24 18:04:54.518] [ERROR] home_path = server_config['home_path']
[2025-04-24 18:04:54.518] [ERROR] KeyError: 'home_path'
[2025-04-24 18:04:54.518] [ERROR]
[2025-04-24 18:04:54.518] [DEBUG] - sub init ref count to 0
[2025-04-24 18:04:54.518] [DEBUG] - export init
[2025-04-24 18:04:54.518] [WARNING] oceanbase-ce-py_script_init-3.1.0 has animation not been closed
[2025-04-24 18:04:54.519] [DEBUG] - plugin oceanbase-ce-py_script_init-3.1.0 result: False
[2025-04-24 18:04:54.648] [INFO] [ERROR] oceanbase-ce-py_script_init-3.1.0 RuntimeError: 'home_path'
[2025-04-24 18:04:54.648] [INFO] [WARN] oceanbase-ce-py_script_init-3.1.0 has animation not been closed
[2025-04-24 18:04:54.648] [INFO]
[2025-04-24 18:04:54.648] [INFO] See https://www.oceanbase.com/product/ob-deployer/error-codes.
The RuntimeError: 'home_path' here is not found. What exactly is the error? Is there something wrong with the configuration?
home_path: /home/admin/
data_dir: /export/observer/data
redo_dir: export/observer/redo
Thanks for the answer!
================================
Checked that it was because of the configuration error, servers did not have the corresponding configuration. Close this problem
Metadata
Metadata
Assignees
Labels
No labels