启动不久就CRASH，如何解决？

AntTech_DIDWZM · 2025 年2 月 6 日 15:38

[root@i-lcygh0jd log]# ls -l
总用量 1420040
drwxr-xr-x 2 root root 4096 2月 5 14:23 alert
-rw-r–r-- 1 root root 8204596 2月 6 15:29 election.log
-rw-r–r-- 1 root root 0 2月 5 14:23 election.log.wf
-rw-r–r-- 1 root root 121244023 2月 6 15:29 observer.log
-rw-r–r-- 1 root root 268439994 2月 6 13:27 observer.log.20250206132741278
-rw-r–r-- 1 root root 268440844 2月 6 13:43 observer.log.20250206134300068
-rw-r–r-- 1 root root 268440441 2月 6 14:03 observer.log.20250206140308622
-rw-r–r-- 1 root root 268440437 2月 6 15:20 observer.log.20250206152024646
-rw-r–r-- 1 root root 2351 2月 6 15:20 observer.log.wf
drwxr-xr-x 3 root root 4096 2月 6 15:12 rca
-rw-r–r-- 1 root root 126604033 2月 6 15:29 rootservice.log
-rw-r–r-- 1 root root 0 2月 5 14:23 rootservice.log.wf
-rw-r–r-- 1 root root 124254048 2月 6 15:27 trace.log
[root@i-lcygh0jd log]#

AntTech_DIDWZM · 2025 年2 月 6 日 15:40

obd安装，在obd安装目录下未发现core文件。
observer.log.20250206152024646:CRASH ERROR!!! IP=555d35a653a0, RBP=148d26449a70, sig=4, sig_code=2, sig_addr=0x555d35a653a0, RLIMIT_CORE=unlimited, timestamp=1738823060383527, tid=3873, tname=T1_L0_G28, trace_id=YB427F000001-00062D7327BB2215-0-0, lbt=0x1f96b218 0x1f1b698d 0x148d9d13d4bf 0x8bb63a0 0x9be8a9c 0x9c0812c 0x9c08505 0x9be51fd 0x9a466c5 0xa5f92d9 0xa5fa810 0xa5f85ef 0x924c3cf 0x924cafc 0x9253edc 0x9253edc 0x924ed8d 0x92176d1 0x92177b1 0x9217ad3 0x9224c5c 0x9226bd3 0x9226edb 0x9237427 0x1ef0327a 0x1eee447d 0xebf34b2 0xebf0fc5 0xebe4b4b 0xec2577e 0xec5339b 0xec473c9 0xeaa14cd 0xea7362e 0x14a77faa 0x11bba464 0x7c4fe26 0x7923e9c 0x792151d 0x7c4d9c4 0x7c4cd09 0x7c482ee 0x7cf5030 0x7cf4929 0xf8dbc1a 0xf8f4a69 0x81cfe74 0x78b043b 0x789e118 0xfc77118, SQL_ID=2D33A95D66306851E3C623743C77BA01, SQL_STRING=CALL DBMS_STATS.PURGE_STATS(NULL);
observer.log.20250206152024646:[2025-02-06 15:20:21.897388] INFO print_limit (main.cpp:355) [12383][observer][T0][Y0-0000000000000001-0-0] [lt=11] [operator()] RLIMIT_CORE = unlimited
observer.log.20250206152024646:[2025-02-06 15:20:21.897399] INFO print_limit (main.cpp:355) [12383][observer][T0][Y0-0000000000000001-0-0] [lt=9] [operator()] RLIMIT_CPU = unlimited
observer.log.20250206152024646:[2025-02-06 15:20:21.897408] INFO print_limit (main.cpp:355) [12383][observer][T0][Y0-0000000000000001-0-0] [lt=8] [operator()] RLIMIT_DATA = unlimited
observer.log.20250206152024646:[2025-02-06 15:20:21.897418] INFO print_limit (main.cpp:355) [12383][observer][T0][Y0-0000000000000001-0-0] [lt=8] [operator()] RLIMIT_FSIZE = unlimited
observer.log.20250206152024646:[2025-02-06 15:20:21.897427] INFO print_limit (main.cpp:355) [12383][observer][T0][Y0-0000000000000001-0-0] [lt=8] [operator()] RLIMIT_LOCKS = unlimited
observer.log.20250206152024646:[2025-02-06 15:20:21.897436] INFO print_limit (main.cpp:357) [12383][observer][T0][Y0-0000000000000001-0-0] [lt=8] [operator()] RLIMIT_MEMLOCK = 65536
observer.log.20250206152024646:[2025-02-06 15:20:21.897446] INFO print_limit (main.cpp:357) [12383][observer][T0][Y0-0000000000000001-0-0] [lt=8] [operator()] RLIMIT_NOFILE = 655350
observer.log.20250206152024646:[2025-02-06 15:20:21.897465] INFO print_limit (main.cpp:357) [12383][observer][T0][Y0-0000000000000001-0-0] [lt=18] [operator()] RLIMIT_NPROC = 655350
observer.log.20250206152024646:[2025-02-06 15:20:21.897475] INFO print_limit (main.cpp:355) [12383][observer][T0][Y0-0000000000000001-0-0] [lt=8] [operator()] RLIMIT_STACK = unlimited

AntTech_DIDWZM · 2025 年2 月 6 日 15:41

obd.log位置在哪里，find没有发现

AntTech_DIDWZM · 2025 年2 月 6 日 15:43

PROCEDURE async_gather_stats_job_proc (duration BIGINT DEFAULT NULL);
PRAGMA INTERFACE(C, ASYNC_GATHER_STATS_JOB_PROC);
END dbms_stats", comment:"", route_sql:""}])
[2025-02-06 15:41:08.864583] INFO [SHARE.SCHEMA] get_batch_packages (ob_schema_service_sql_impl.cpp:4068) [4096][T1_L0_G28][T1][YB427F000001-00062D745D081430-0-0] [lt=16] get batch package info finish(schema_version=1738736665582384, ret=0)
[2025-02-06 15:41:08.864667] INFO [PL] get_package_from_plan_cache (ob_pl_package_manager.cpp:1789) [4096][T1_L0_G28][T1][YB427F000001-00062D745D081430-0-0] [lt=17] get pl package from plan cache failed(ret=-5138, package_id=310001)
[2025-02-06 15:41:08.869277] INFO [PL] compile_module (ob_llvm_helper.cpp:625) [4096][T1_L0_G28][T1][YB427F000001-00062D745D081430-0-0] [lt=18] ================Optimized LLVM Module================
[2025-02-06 15:41:08.869692] INFO [PL] dump_module (ob_llvm_helper.cpp:644) [4096][T1_L0_G28][T1][YB427F000001-00062D745D081430-0-0] [lt=27] Dump LLVM Compile Module!
(s.str().c_str()="; ModuleID = ‘PL/SQL’
source_filename = “PL/SQL”
target datalayout = “e-m:e-p270:32:32-p271:32:32-p272:64:64-i64:64-f80:128-n8:16:32:64-S128”

%pl_exec_context = type { i64, i64, i64, %seg_param_store*, %obj*, i32*, i64, i8, i64 }
%seg_param_store = type { i64, i32, %wrapper_allocator, %seg_pointer_array, i64, i64 }
%wrapper_allocator = type { i64, i64 }
%seg_pointer_array = type { i64, [1 x i64], i64, [1 x i64], i64, i64, i64, i32, %wrapper_allocator, i8, %memory_context }
%memory_context = type { i64, i64, i64 }
%obj = type { %obj_meta, i32, i64 }
%obj_meta = type { i8, i8, i8, i8 }
%objparam = type { %obj, i64, i32, %obj.0, i32, i32, %obj_meta }
%obj.0 = type { i64, i8 }
%data_type = type { %obj_meta, i64, i32, i8, i8 }
%unwind_exception = type { i64 }
%pl_condition_value = type { i64, i64, i8, i64, i64, i8 }

declare i32 @spi_calc_expr_at_idx(%pl_exec_context*, i64, i64, %objparam*)

declare i32 @spi_calc_package_expr(%pl_exec_context*, i64, i64, %objparam*)

declare i32 @spi_convert_objparam(%pl_exec_context*, %objparam*, i64, %objparam*, i8)

declare i32 @spi_set_variable_to_expr(%pl_exec_context*, i64, %objparam*, i8, i8)

declare i32 @spi_query_into_expr_idx(%pl_exec_context*, i8*, i64, i64*, i64, %data_type*, i64, i8*, i64*, i8, i8, i8)

declare i32 @spi_end_trans(%pl_exec_context*, i8*, i8)

declare i32 @spi_update_location(%pl_exec_context*, i64)

declare i32 @spi_execute_with_expr_idx(%pl_exec_context*, i8*, i64, i64*, i64, i64*, i64, %data_type*, i64, i8*, i64*, i8, i8, i8, i8)

declare i32 @spi_execute_immediate(%pl_exec_context*, i64, i64, i64*, i64, i64*, i64, %data_type*, i64, i8*, i64*, i8, i8, i8)

declare i32 @spi_alloc_complex_var(%pl_exec_context*, i8, i64, i64, i32, i64*, i64)

淇铭 · 2025 年2 月 6 日 15:45

1、obd日志： 默认保存在安装obd的用户home路径： cd ~/.obd/log/
2、obd cluster list --查看集群名 obd cluster edit-config {集群名} --保存在文本里提供一下

旭辉 · 2025 年2 月 6 日 15:48

看一下cpu指令集： lscpu

AntTech_DIDWZM · 2025 年2 月 6 日 15:50

/var/lib/systemd/coredump/下有core文件，你看和这个问题有关吗？需要上传哪个？

[root@i-lcygh0jd coredump]# ls -lrth
总用量 2.5G
-rw-r----- 1 root root 335K 2月 5 14:18 core.udevadm.0.ba5be4fd6ebc449c95e175cf5eb1c507.636.1738736306000000000000.lz4
-rw-r----- 1 root root 334K 2月 5 14:18 core.udevadm.0.ba5be4fd6ebc449c95e175cf5eb1c507.953.1738736307000000000000.lz4
-rw-r----- 1 root root 335K 2月 5 14:21 core.udevadm.0.d7061597b4d0470399ed1c5b7a0263e8.627.1738736513000000000000.lz4
-rw-r----- 1 root root 334K 2月 5 14:21 core.udevadm.0.d7061597b4d0470399ed1c5b7a0263e8.919.1738736514000000000000.lz4
-rw-r----- 1 root root 243M 2月 5 14:39 core.observer.0.d7061597b4d0470399ed1c5b7a0263e8.1916.1738737560000000000000.lz4
-rw-r----- 1 root root 334K 2月 5 14:55 core.udevadm.0.9ff8ae4bed784b97aabbc783488c8e65.660.1738738507000000000000.lz4
-rw-r----- 1 root root 334K 2月 5 14:55 core.udevadm.0.9ff8ae4bed784b97aabbc783488c8e65.1022.1738738509000000000000.lz4
-rw-r----- 1 root root 130M 2月 5 14:57 core.observer.0.9ff8ae4bed784b97aabbc783488c8e65.2871.1738738670000000000000.lz4
-rw-r----- 1 root root 131M 2月 5 15:09 core.observer.0.9ff8ae4bed784b97aabbc783488c8e65.4109.1738739360000000000000.lz4
-rw-r----- 1 root root 138M 2月 5 17:09 core.observer.0.9ff8ae4bed784b97aabbc783488c8e65.20095.1738746560000000000000.lz4
-rw-r----- 1 root root 140M 2月 5 17:24 core.observer.0.9ff8ae4bed784b97aabbc783488c8e65.22762.1738747460000000000000.lz4
-rw-r----- 1 root root 142M 2月 5 17:39 core.observer.0.9ff8ae4bed784b97aabbc783488c8e65.25083.1738748360000000000000.lz4
-rw-r----- 1 root root 146M 2月 5 19:09 core.observer.0.9ff8ae4bed784b97aabbc783488c8e65.35673.1738753760000000000000.lz4
-rw-r----- 1 root root 136M 2月 5 19:24 core.observer.0.9ff8ae4bed784b97aabbc783488c8e65.39745.1738754660000000000000.lz4
-rw-r----- 1 root root 142M 2月 5 19:39 core.observer.0.9ff8ae4bed784b97aabbc783488c8e65.41508.1738755560000000000000.lz4
-rw-r----- 1 root root 136M 2月 5 20:24 core.observer.0.9ff8ae4bed784b97aabbc783488c8e65.47445.1738758260000000000000.lz4
-rw-r----- 1 root root 140M 2月 6 11:39 core.observer.0.9ff8ae4bed784b97aabbc783488c8e65.153064.1738813160000000000000.lz4
-rw-r----- 1 root root 142M 2月 6 13:39 core.observer.0.9ff8ae4bed784b97aabbc783488c8e65.169268.1738820360000000000000.lz4
-rw-r----- 1 root root 143M 2月 6 13:54 core.observer.0.9ff8ae4bed784b97aabbc783488c8e65.175568.1738821266000000000000.lz4
-rw-r----- 1 root root 334K 2月 6 13:55 core.udevadm.0.2c1935f5f74c4aaa95e0f6dbb5c5be32.662.1738821302000000000000.lz4
-rw-r----- 1 root root 334K 2月 6 13:55 core.udevadm.0.2c1935f5f74c4aaa95e0f6dbb5c5be32.1134.1738821304000000000000.lz4
-rw-r----- 1 root root 334K 2月 6 14:02 core.udevadm.0.62c9d56b86c047b2be55251aa423b4b7.668.1738821744000000000000.lz4
-rw-r----- 1 root root 334K 2月 6 14:02 core.udevadm.0.62c9d56b86c047b2be55251aa423b4b7.1150.1738821746000000000000.lz4
-rw-r----- 1 root root 334K 2月 6 14:06 core.udevadm.0.1859b2017d6a4fd48c72e7d458839317.671.1738822013000000000000.lz4
-rw-r----- 1 root root 335K 2月 6 14:06 core.udevadm.0.1859b2017d6a4fd48c72e7d458839317.1076.1738822015000000000000.lz4
-rw-r----- 1 root root 138M 2月 6 14:09 core.observer.0.1859b2017d6a4fd48c72e7d458839317.1590.1738822160000000000000.lz4
-rw-r----- 1 root root 334K 2月 6 14:13 core.udevadm.0.574702895df74125a5c786cf0450d9a0.679.1738822385000000000000.lz4
-rw-r----- 1 root root 334K 2月 6 14:13 core.udevadm.0.574702895df74125a5c786cf0450d9a0.1062.1738822387000000000000.lz4
-rw-r----- 1 root root 148M 2月 6 14:24 core.observer.0.574702895df74125a5c786cf0450d9a0.1527.1738823060000000000000.lz4
-rw-r----- 1 root root 142M 2月 6 15:24 core.observer.0.574702895df74125a5c786cf0450d9a0.12383.1738826660000000000000.lz4
-rw-r----- 1 root root 334K 2月 6 15:31 core.udevadm.0.4e5f2e0faea44f4e8935fc8f4754c063.699.1738827097000000000000.lz4
-rw-r----- 1 root root 334K 2月 6 15:31 core.udevadm.0.4e5f2e0faea44f4e8935fc8f4754c063.1138.1738827098000000000000.lz4
-rw-r----- 1 root root 147M 2月 6 15:41 core.observer.0.4e5f2e0faea44f4e8935fc8f4754c063.3294.1738827668000000000000.lz4

淇铭 · 2025 年2 月 6 日 15:53

sysctl -a | grep pattern
你通过这个命令查一下你配置的core的目录位置如果没有配置就是没有
lscpu 指令集查看一下

AntTech_DIDWZM · 2025 年2 月 6 日 16:02

[root@i-lcygh0jd coredump]# sysctl -a | grep pattern
kernel.core_pattern = |/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %h

[root@i-lcygh0jd systemd]# lscpu
架构： x86_64
CPU 运行模式： 32-bit, 64-bit
字节序： Little Endian
Address sizes: 40 bits physical, 48 bits virtual
CPU: 4
在线 CPU 列表： 0-3
每个核的线程数： 1
每个座的核数： 4
座： 1
NUMA 节点： 1
厂商 ID： GenuineIntel
CPU 系列： 6
型号： 6
型号名称： QEMU Virtual CPU
步进： 3
CPU MHz： 2299.998
BogoMIPS： 4599.99
超管理器厂商： KVM
虚拟化类型：完全
L1d 缓存： 128 KiB
L1i 缓存： 128 KiB
L2 缓存： 16 MiB
L3 缓存： 16 MiB
NUMA 节点0 CPU： 0-3
Vulnerability Itlb multihit: KVM: Vulnerable
Vulnerability L1tf: Mitigation; PTE Inversion
Vulnerability Mds: Vulnerable: Clear CPU buffers attempted, no microcode; SMT Host state unknown
Vulnerability Meltdown: Mitigation; PTI
Vulnerability Mmio stale data: Not affected
Vulnerability Spec store bypass: Vulnerable
Vulnerability Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Vulnerability Spectre v2: Mitigation; Retpolines, STIBP disabled, RSB filling, PBRSB-eIBRS Not affected
Vulnerability Srbds: Not affected
Vulnerability Tsx async abort: Not affected
标记： fpu de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pse36 clflush mmx fxsr sse sse2 ht syscall nx lm rep_good nopl xtopology cpuid tsc_known_freq pni cx16 x2apic hypervisor lahf_lm cpuid_fault pti

皇甫侯 · 2025 年2 月 6 日 16:03

说错了，你这是进程都挂了。。应该用离线分析命令分析指定的日志文件
obdiag analyze log --files observer.log.20230831142211247

不过你都找到core文件了，可以从这些core文件分析下出问题的源头SQL，顺便在问下你这个集群是部署成功过没有？

https://www.oceanbase.com/knowledge-base/oceanbase-database-1000000000340650?back=kb

AntTech_DIDWZM · 2025 年2 月 6 日 16:03

systemd-coredump.zip (22.1 KB)

AntTech_DIDWZM · 2025 年2 月 6 日 16:04

部署成功了，就是启动一会（10分钟左右）就挂掉。

淇铭 · 2025 年2 月 6 日 16:05

这个信息提供一下

AntTech_DIDWZM · 2025 年2 月 6 日 16:06

[root@i-lcygh0jd log]# ls
alert election.log election.log.wf observer.log observer.log.20250206132741278 observer.log.20250206134300068 observer.log.20250206140308622 observer.log.20250206152024646 observer.log.wf rca rootservice.log rootservice.log.wf trace.log
[root@i-lcygh0jd log]# obdiag analyze log --files observer.log
-bash: obdiag：未找到命令
[root@i-lcygh0jd log]# obd obdiag analyze log --files observer.log
The tool oceanbase-diagnostic-tool is already installed the latest version 2.6.0
analyze_log_offline start …
analyze nodes’s log start. Please wait a moment…
analyze start ok
FileListInfo:
±----------±-------------------------------+
| Node | LogList |
+===========+================================+
| 127.0.0.1 | [’/data/obd/log/observer.log’] |
±----------±-------------------------------+
Analyze OceanBase Offline Log Summary:
±----------±---------±-----------±------------±----------±--------+
| Node | Status | FileName | ErrorCode | Message | Count |
+===========+==========+============+=============+===========+=========+
| 127.0.0.1 | PASS | | | | |
±----------±---------±-----------±------------±----------±--------+
For more details, please run cmd ’ cat /data/obd/log/obdiag_analyze_pack_20250206160512/result_details.txt ’
Trace ID: 170997d4-e461-11ef-a38d-52549b9cd8f8
If you want to view detailed obdiag logs, please run: /root/oceanbase-diagnostic-tool/obdiag display-trace 170997d4-e461-11ef-a38d-52549b9cd8f8

Trace ID: 1509faa0-e461-11ef-81a2-52549b9cd8f8
If you want to view detailed obd logs, please run: obd display-trace 1509faa0-e461-11ef-81a2-52549b9cd8f8
[root@i-lcygh0jd log]# obd obdiag analyze log --files observer.log.20250206132741278
The tool oceanbase-diagnostic-tool is already installed the latest version 2.6.0
analyze_log_offline start …
analyze nodes’s log start. Please wait a moment…
analyze start ok
FileListInfo:
±----------±-------------------------------------------------+
| Node | LogList |
+===========+==================================================+
| 127.0.0.1 | [’/data/obd/log/observer.log.20250206132741278’] |
±----------±-------------------------------------------------+
Analyze OceanBase Offline Log Summary:
±----------±---------±-----------±------------±----------±--------+
| Node | Status | FileName | ErrorCode | Message | Count |
+===========+==========+============+=============+===========+=========+
| 127.0.0.1 | PASS | | | | |
±----------±---------±-----------±------------±----------±--------+
For more details, please run cmd ’ cat /data/obd/log/obdiag_analyze_pack_20250206160543/result_details.txt ’
Trace ID: 29775c12-e461-11ef-84d7-52549b9cd8f8
If you want to view detailed obdiag logs, please run: /root/oceanbase-diagnostic-tool/obdiag display-trace 29775c12-e461-11ef-84d7-52549b9cd8f8

Trace ID: 27941d72-e461-11ef-9392-52549b9cd8f8
If you want to view detailed obd logs, please run: obd display-trace 27941d72-e461-11ef-9392-52549b9cd8f8
[root@i-lcygh0jd log]# cat /data/obd/log/obdiag_analyze_pack_20250206160512/result_details.txt

Details:

Node: 127.0.0.1
Status: PASS
FileName: None
ErrorCode: None
Message: None
Count: None
Cause: None
Solution: None
First Found Time: None
Last Found Time: None
Trace_IDS: None

[root@i-lcygh0jd log]# /root/oceanbase-diagnostic-tool/obdiag display-trace 170997d4-e461-11ef-a38d-52549b9cd8f8
[2025-02-06 16:05:12.130] [DEBUG] - cmd: /root/oceanbase-diagnostic-tool/obdiag analyze log
[2025-02-06 16:05:12.131] [DEBUG] - opts: {‘inner_config’: None, ‘from’: None, ‘to’: None, ‘scope’: ‘all’, ‘grep’: None, ‘log_level’: None, ‘files’: [’/data/obd/log/observer.log’], ‘store_dir’: ‘/data/obd/log’, ‘since’: ‘30m’, ‘temp_dir’: ‘/tmp’, ‘c’: ‘/root/.obdiag/config.yml’, ‘config’: None}
[2025-02-06 16:05:12.131] [DEBUG] - mkdir /root/oceanbase-diagnostic-tool/conf/inner_config.yml
[2025-02-06 16:05:12.137] [DEBUG] - mkdir /root/.obdiag/config.yml
[2025-02-06 16:05:12.140] [INFO] analyze_log_offline start …
[2025-02-06 16:05:12.140] [DEBUG] - Use /data/obd/log/obdiag_analyze_pack_20250206160512 as pack dir.
[2025-02-06 16:05:12.140] [INFO] analyze nodes’s log start. Please wait a moment…
[2025-02-06 16:05:12.141] [INFO] analyze start
[2025-02-06 16:05:12.142] [DEBUG] - Sending Collect Shell Command to node 127.0.0.1 …
[2025-02-06 16:05:12.142] [DEBUG] - mkdir /data/obd/log/obdiag_analyze_pack_20250206160512
[2025-02-06 16:05:12.143] [DEBUG] - mkdir /data/obd/log/obdiag_analyze_pack_20250206160512/local
[2025-02-06 16:05:12.145] [DEBUG] - [local host] run cmd = [mkdir -p /tmp/ob_log_local_20250206153512_20250206160612_477a4b] on localhost
[2025-02-06 16:05:12.152] [DEBUG] - get log list [’/data/obd/log/observer.log’]
[2025-02-06 16:05:12.154] [INFO]
[2025-02-06 16:05:12.154] [INFO] FileListInfo:
[2025-02-06 16:05:12.154] [INFO] ±----------±-------------------------------+
[2025-02-06 16:05:12.154] [INFO] | Node | LogList |
[2025-02-06 16:05:12.154] [INFO] +===========+================================+
[2025-02-06 16:05:12.154] [INFO] | 127.0.0.1 | [’/data/obd/log/observer.log’] |
[2025-02-06 16:05:12.154] [INFO] ±----------±-------------------------------+
[2025-02-06 16:05:12.330] [DEBUG] - start parse log /data/obd/log/obdiag_analyze_pack_20250206160512/local/_data_obd_log_observer.log
[2025-02-06 16:05:13.175] [DEBUG] - complete parse log /data/obd/log/obdiag_analyze_pack_20250206160512/local/_data_obd_log_observer.log
[2025-02-06 16:05:13.176] [INFO]
[2025-02-06 16:05:13.176] [INFO] FileListInfo:
[2025-02-06 16:05:13.176] [INFO] ±----------±-------------------------------+
[2025-02-06 16:05:13.176] [INFO] | Node | LogList |
[2025-02-06 16:05:13.176] [INFO] +===========+================================+
[2025-02-06 16:05:13.176] [INFO] | 127.0.0.1 | [’/data/obd/log/observer.log’] |
[2025-02-06 16:05:13.176] [INFO] ±----------±-------------------------------+
[2025-02-06 16:05:13.176] [INFO]
[2025-02-06 16:05:13.176] [DEBUG] - [local host] run cmd = [rm -rf /tmp/ob_log_local_20250206153512_20250206160612_477a4b] on localhost
[2025-02-06 16:05:13.184] [INFO]
[2025-02-06 16:05:13.184] [INFO] Analyze OceanBase Offline Log Summary:
[2025-02-06 16:05:13.185] [INFO]
[2025-02-06 16:05:13.185] [INFO] ±----------±---------±-----------±------------±----------±--------+
[2025-02-06 16:05:13.185] [INFO] | Node | Status | FileName | ErrorCode | Message | Count |
[2025-02-06 16:05:13.185] [INFO] +===========+==========+============+=============+===========+=========+
[2025-02-06 16:05:13.185] [INFO] | 127.0.0.1 | PASS | | | | |
[2025-02-06 16:05:13.185] [INFO] ±----------±---------±-----------±------------±----------±--------+
[2025-02-06 16:05:13.186] [INFO] For more details, please run cmd ’ cat /data/obd/log/obdiag_analyze_pack_20250206160512/result_details.txt ’
[2025-02-06 16:05:13.186] [INFO]
[2025-02-06 16:05:13.186] [INFO] Trace ID: 170997d4-e461-11ef-a38d-52549b9cd8f8
[2025-02-06 16:05:13.186] [INFO] If you want to view detailed obdiag logs, please run: /root/oceanbase-diagnostic-tool/obdiag display-trace 170997d4-e461-11ef-a38d-52549b9cd8f8

[root@i-lcygh0jd log]# cat /data/obd/log/obdiag_analyze_pack_20250206160512/result_details.txt

Details:

Node: 127.0.0.1
Status: PASS
FileName: None
ErrorCode: None
Message: None
Count: None
Cause: None
Solution: None
First Found Time: None
Last Found Time: None
Trace_IDS: None

AntTech_DIDWZM · 2025 年2 月 6 日 16:08

core文件和obdiag 的文件都上传了。还请看一下。

旭辉 · 2025 年2 月 6 日 16:09

原因：
当前使用的cpu不支持avx指令，OB内核用到了avx指令

解决方案:
更换支持AVX指令的CPU型号

可以看下这个帖子，表象差不多

皇甫侯 · 2025 年2 月 6 日 16:11

你上传的日志不对吧。。解压出来是个乱码文件
可以先按照旭辉老师说的检查下CPU指令集

AntTech_DIDWZM · 2025 年2 月 7 日 13:35

好了，就是avx指令集的问题。这种环境问题，以后在安装时，能不能先自检测一下，都让用户来排查很不友好啊。

淇铭 · 2025 年2 月 7 日 14:04

可以先用obdiag巡检检查一下环境不过后续也会从版本上拦截指令集不支持的问题后续可以看版本的发布说明

部署环境检查

obdiag check run --cases=build_before
https://www.oceanbase.com/docs/common-obdiag-cn-1000000002200479

AntTech_IUCDZ1 · 2025 年2 月 7 日 19:44