halo安装的时候报错

1Panel
1

1Panel-halo-dJR6 | JVMDUMP012E Error in System dump: /application/core.20260120.000006.7.0001.dmp
1Panel-halo-dJR6 | JVMDUMP032I JVM requested Java dump using ‘/application/javacore.20260120.000006.7.0002.txt’ in response to an event

1Panel-halo-dJR6 | JVMDUMP010I Java dump written to /application/javacore.20260120.000006.7.0002.txt
1Panel-halo-dJR6 | JVMDUMP032I JVM requested Snap dump using ‘/application/Snap.20260120.000006.7.0003.trc’ in response to an event

1Panel-halo-dJR6 | JVMDUMP010I Snap dump written to /application/Snap.20260120.000006.7.0003.trc
1Panel-halo-dJR6 | JVMDUMP032I JVM requested JIT dump using ‘/application/jitdump.20260120.000006.7.0004.dmp’ in response to an event

1Panel-halo-dJR6 | JVMDUMP051I JIT dump occurred in ‘main’ thread 0x0000000000017000

1Panel-halo-dJR6 | JVMDUMP053I JIT dump is recompiling java/util/zip/ZipFile$Source.checkAndAddEntry(II)I

1Panel-halo-dJR6 | JVMDUMP053I JIT dump is recompiling java/util/zip/ZipFile$Source.checkAndAddEntry(II)I

1Panel-halo-dJR6 | JVMDUMP010I JIT dump written to /application/jitdump.20260120.000006.7.0004.dmp

2

全新安装吗？

3

1Panel-halo-B4EO | ----------- Stack Backtrace -----------
1Panel-halo-B4EO | protectedBacktrace+0x12 (0x00007CC521376A02 [libj9prt29.so+0x26a02])
1Panel-halo-B4EO | omrsig_protect+0x239 (0x00007CC52137B049 [libj9prt29.so+0x2b049])
1Panel-halo-B4EO | omrintrospect_backtrace_thread_raw+0xbe (0x00007CC521376EDE [libj9prt29.so+0x26ede])
1Panel-halo-B4EO | omrsig_protect+0x239 (0x00007CC52137B049 [libj9prt29.so+0x2b049])
1Panel-halo-B4EO | omrintrospect_backtrace_thread+0x87 (0x00007CC521376887 [libj9prt29.so+0x26887])
1Panel-halo-B4EO | generateDiagnosticFiles+0x84 (0x00007CC521423AE4 [libj9vm29.so+0x3fae4])
1Panel-halo-B4EO | omrsig_protect+0x239 (0x00007CC52137B049 [libj9prt29.so+0x2b049])
1Panel-halo-B4EO | vmSignalHandler+0x17a (0x00007CC521423D4A [libj9vm29.so+0x3fd4a])
1Panel-halo-B4EO | (0x00007CC521547AB5 [libj9vm29.so+0x163ab5])
1Panel-halo-B4EO | ---------------------------------------
1Panel-halo-B4EO | JVMDUMP039I Processing dump event “gpf”, detail “” at 2026/01/20 13:00:41 - please wait.
1Panel-halo-B4EO | JVMDUMP032I JVM requested System dump using ‘/application/core.20260120.130041.7.0001.dmp’ in response to an event
1Panel-halo-B4EO | JVMPORT030W /proc/sys/kernel/core_pattern setting “|/usr/share/apport/apport -p%p -s%s -c%c -d%d -P%P -u%u -g%g -F%F – %E” specifies that the core dump is to be piped to an external program. Attempting to rename either core or core.31. Review the manual for the external program to find where the core dump is written and ensure the program does not truncate it.对是新服务器，新安装，好像是容器的默认java版本有点问题

4

JIT dump is recompiling java/util/zip/ZipFile$Source.checkAndAddEntry(II)I

可以得出一个比较明确的结论：

JVM（OpenJ9）在处理 jar/zip 文件时，在 ZipFile / ZipCoder 相关的 native/JIT 代码里崩溃了，触发了 GPF。

也就是说—— 不是你的业务代码抛了异常，而是 JVM 自己在加载 jar 包时挂了，属于 JVM/JIT/native 层面的崩溃。

可能的根源方向

综合这些信息，最可能的几类原因：

  1. OpenJ9 某个版本的 bug 在处理 zip/jar（尤其是 UTF-8 名称、哈希、CEN 表）时，JIT 或 native 代码有缺陷，导致非法内存访问 → GPF。
  2. jar/zip 文件本身有问题 比如：
  • 文件损坏、截断
  • 被某些工具错误修改
  • 非法/极端的 entry 名称或结构 这类情况会放大 JVM 在解析 CEN（Central Directory）时的 bug。
  1. JIT 优化触发了某个隐藏问题 日志里已经明确 JIT 在重新编译 checkAndAddEntry，这很像是： “某个特定优化 + 特定数据 + 特定版本的 OpenJ9” 组合触发了崩溃。