【 使用环境 】生产环境
【 OB or 其他组件 】其他组件
【 使用版本 】4.3.5
【问题描述】目前发现通过ocp all in one白屏部署ocp的时候,会卡在 start ocp server fail,然后日志也没打印相关错误信息,只有一个启动server失败的信息
[2025-04-15 18:59:15.026] [e1e449e2-19e3-11f0-b0f8-0050569782a6] [DEBUG] – admin@192.168.135.149 execute: cd /oceanbase//ocp; export JDBC_URL=jdbc:oceanbase://192.168.135.149:2883/meta_database; export JDBC_USERNAME=root@ocp_meta;export JDBC_PASSWORD=****** export JDBC_PUBLIC_KEY=;export OCP_INITIAL_ADMIN_PASSWORD=******
[2025-04-15 18:59:15.026] [e1e449e2-19e3-11f0-b0f8-0050569782a6] [DEBUG] java -Dfile.encoding=UTF-8 -jar -Xms8g -Xmx8g -Docp.iam.encrypted-system-password=****** /oceanbase//ocp/lib/ocp-server.jar --bootstrap --with-property=server.port:8080 --with-property=logging.file.max-size:100MB --with-property=ocp.logging.file.total.size.cap:1GB --with-property=ocp.monitordb.host:192.168.135.149 --with-property=ocp.monitordb.username:root@ocp_monitor --with-property=ocp.monitordb.port:2883 --with-property=ocp.monitordb.password:****** --with-property=ocp.monitordb.database:monitor_database --with-property=logging.file.name:/oceanbase/logs/ocp-server.log --with-property=ocp.site.url:http://192.168.135.149:8080 --progress-log=/oceanbase/logs/bootstrap.log --with-property=obsdk.ob.connection.mode:direct --with-property=ocp.iam.login.client.max-attempts:60 --with-property=ocp.iam.login.client.lockout-minutes:1 --with-property=ocp.file.local.built-in.dir:/oceanbase//ocp/ocp-server/lib --with-property=ocp.log.download.tmp.dir:/oceanbase//ocp/logs/ocp --with-property=ocp.file.local.dir:/oceanbase/software > /dev/null 2>&1 &
[2025-04-15 18:59:15.084] [e1e449e2-19e3-11f0-b0f8-0050569782a6] [DEBUG] – exited code 0
[2025-04-15 18:59:15.084] [e1e449e2-19e3-11f0-b0f8-0050569782a6] [DEBUG] – admin@192.168.135.149 execute: ps -aux | grep -F ‘java -Dfile.encoding=UTF-8 -jar -Xms8g -Xmx8g -Docp.iam.encrypted-system-password=****** /oceanbase//ocp/lib/ocp-server.jar --bootstrap’ | grep -v grep | awk ‘{print $2}’
[2025-04-15 18:59:15.159] [e1e449e2-19e3-11f0-b0f8-0050569782a6] [DEBUG] – exited code 0
[2025-04-15 18:59:15.159] [e1e449e2-19e3-11f0-b0f8-0050569782a6] [ERROR] failed to start 192.168.135.149 ocp server
[2025-04-15 18:59:15.159] [e1e449e2-19e3-11f0-b0f8-0050569782a6] [INFO] [ERROR] failed to start 192.168.135.149 ocp server
[2025-04-15 18:59:15.159] [e1e449e2-19e3-11f0-b0f8-0050569782a6] [INFO]
[2025-04-15 18:59:15.160] [e1e449e2-19e3-11f0-b0f8-0050569782a6] [DEBUG] - plugin ocp-server-ce-py_script_start-4.2.1 result: False
[2025-04-15 18:59:15.160] [e1e449e2-19e3-11f0-b0f8-0050569782a6] [DEBUG] - connect 192.168.135.149 -P2881 -uroot@sys -p******
[2025-04-15 19:15:20.720] [e1e449e2-19e3-11f0-b0f8-0050569782a6] [DEBUG] - exclusive lock /home/admin/.obd/lock/deploy_metadb
, count 15
[2025-04-15 19:15:20.725] [e1e449e2-19e3-11f0-b0f8-0050569782a6] [DEBUG] - Get local repository oceanbase-ce-4.2.1.8-499b676f2ede5a16e0c07b2b15991d1160d972e8