openubmc升级成功之后一直报错

Nath3y1r · 2026 年8 月 11 日 05:15

问题描述

升级到26.6版本后各种服务一直报错，网络不通

1970-01-01 00:05:48.510600 maca ERROR: init.lua(194): [account]StartupCheck failed, error: initialization is not complete while checking the startup status, status: Starting, check count: 7
1970-01-01 00:05:48.622176 maca ERROR: init.lua(194): [bios]StartupCheck failed, error: initialization is not complete while checking the startup status, status: Starting, check count: 7
1970-01-01 00:05:48.692995 maca ERROR: init.lua(194): [bmc_health]StartupCheck failed, error: initialization is not complete while checking the startup status, status: Starting, check count: 7
1970-01-01 00:05:48.814354 maca ERROR: init.lua(194): [bmc_network]StartupCheck failed, error: initialization is not complete while checking the startup status, status: Starting, check count: 7
1970-01-01 00:05:48.936590 maca ERROR: init.lua(194): [bmc_soc]StartupCheck failed, error: initialization is not complete while checking the startup status, status: Starting, check count: 7
1970-01-01 00:05:49.017273 maca ERROR: init.lua(194): [bmc_time]StartupCheck failed, error: initialization is not complete while checking the startup status, status: Starting, check count: 7
1970-01-01 00:05:49.118716 maca ERROR: init.lua(194): [bmc_upgrade]StartupCheck failed, error: initialization is not complete while checking the startup status, status: Starting, check count: 7
1970-01-01 00:05:49.209723 maca ERROR: init.lua(194): [capability_proxy]StartupCheck failed, error: initialization is not complete while checking the startup status, status: Starting, check count: 7
1970-01-01 00:05:49.300774 maca ERROR: init.lua(194): [certificate]StartupCheck failed, error: initialization is not complete while checking the startup status, status: Starting, check count: 7
1970-01-01 00:05:49.422157 maca ERROR: init.lua(194): [chassis]StartupCheck failed, error: initialization is not complete while checking the startup status, status: Starting, check count: 7
1970-01-01 00:05:49.523415 maca ERROR: init.lua(194): [compute]StartupCheck failed, error: initialization is not complete while checking the startup status, status: Starting, check count: 7
1970-01-01 00:05:49.614482 maca ERROR: init.lua(194): [dcmid]StartupCheck failed, error: initialization is not complete while checking the startup status, status: Starting, check count: 7
1970-01-01 00:05:49.725774 maca ERROR: init.lua(194): [ddns]StartupCheck failed, error: initialization is not complete while checking the startup status, status: Starting, check count: 7
1970-01-01 00:05:49.816840 maca ERROR: init.lua(194): [event]StartupCheck failed, error: initialization is not complete while checking the startup status, status: Starting, check count: 7
1970-01-01 00:05:49.918078 maca ERROR: init.lua(194): [event_policy]StartupCheck failed, error: initialization is not complete while checking the startup status, status: Starting, check count: 7
1970-01-01 00:05:50.120406 maca ERROR: init.lua(194): [firmware_mgmt]StartupCheck failed, error: initialization is not complete while checking the startup status, status: Starting, check count: 7
1970-01-01 00:05:50.232131 maca ERROR: init.lua(194): [fructrl]StartupCheck failed, error: initialization is not complete while checking the startup status, status: Starting, check count: 7
1970-01-01 00:05:50.322857 maca ERROR: init.lua(194): [frudata]StartupCheck failed, error: initialization is not complete while checking the startup status, status: Starting, check count: 7
1970-01-01 00:05:50.415403 maca ERROR: init.lua(194): [general_hardware]StartupCheck failed, error: initialization is not complete while checking the startup status, status: Starting, check count: 7
1970-01-01 00:05:50.505247 maca ERROR: init.lua(194): [host_agent]StartupCheck failed, error: initialization is not complete while checking the startup status, status: Starting, check count: 7
1970-01-01 00:05:50.616978 maca ERROR: init.lua(194): [hwdiscovery]StartupCheck failed, error: initialization is not complete while checking the startup status, status: Starting, check count: 7
1970-01-01 00:05:50.717685 maca ERROR: init.lua(194): [hwproxy]StartupCheck failed, error: initialization is not complete while checking the startup status, status: Starting, check count: 7
1970-01-01 00:05:50.828702 maca ERROR: init.lua(194): [iam]StartupCheck failed, error: initialization is not complete while checking the startup status, status: Starting, check count: 7
1970-01-01 00:05:50.910196 maca ERROR: init.lua(194): [ipmi_core]StartupCheck failed, error: initialization is not complete while checking the startup status, status: Starting, check count: 7
1970-01-01 00:05:51.000927 maca ERROR: init.lua(194): [key_mgmt]StartupCheck failed, error: initialization is not complete while checking the startup status, status: Starting, check count: 7
1970-01-01 00:05:51.112378 maca ERROR: init.lua(194): [lsw]StartupCheck failed, error: initialization is not complete while checking the startup status, status: Starting, check count: 7
1970-01-01 00:05:51.193507 maca ERROR: init.lua(194): [manufacture]StartupCheck failed, error: initialization is not complete while checking the startup status, status: Starting, check count: 7
1970-01-01 00:05:51.294129 maca ERROR: init.lua(194): [mctpd]StartupCheck failed, error: initialization is not complete while checking the startup status, status: Starting, check count: 7
1970-01-01 00:05:51.395527 maca ERROR: init.lua(194): [network_adapter]StartupCheck failed, error: initialization is not complete while checking the startup status, status: Starting, check count: 7
1970-01-01 00:05:51.496759 maca ERROR: init.lua(194): [nsm]StartupCheck failed, error: initialization is not complete while checking the startup status, status: Starting, check count: 7
1970-01-01 00:05:51.618365 maca ERROR: init.lua(194): [observability]StartupCheck failed, error: initialization is not complete while checking the startup status, status: Starting, check count: 7
1970-01-01 00:05:51.719312 maca ERROR: init.lua(194): [oms]StartupCheck failed, error: initialization is not complete while checking the startup status, status: Starting, check count: 7
1970-01-01 00:05:51.820741 maca ERROR: init.lua(194): [pcie_device]StartupCheck failed, error: initialization is not complete while checking the startup status, status: Starting, check count: 7
1970-01-01 00:05:51.921476 maca ERROR: init.lua(194): [persistence]StartupCheck failed, error: initialization is not complete while checking the startup status, status: Starting, check count: 7
1970-01-01 00:05:52.002394 maca ERROR: init.lua(194): [power_mgmt]StartupCheck failed, error: initialization is not complete while checking the startup status, status: Starting, check count: 7
1970-01-01 00:05:52.114133 maca ERROR: init.lua(194): [product_mgmt]StartupCheck failed, error: initialization is not complete while checking the startup status, status: Starting, check count: 7
1970-01-01 00:05:52.235779 maca ERROR: init.lua(194): [redfish]StartupCheck failed, error: initialization is not complete while checking the startup status, status: Starting, check count: 7
1970-01-01 00:05:52.380796 maca ERROR: init.lua(185): [remote_console]StartupCheck failed, error: org.freedesktop.DBus.Error.ServiceUnknown: The name bmc.kepler.remote_console was not provided by any .service files, check count: 7
1970-01-01 00:05:52.439319 maca ERROR: init.lua(194): [rmcpd]StartupCheck failed, error: initialization is not complete while checking the startup status, status: Starting, check count: 7
1970-01-01 00:05:52.540645 maca ERROR: init.lua(194): [sensor]StartupCheck failed, error: initialization is not complete while checking the startup status, status: Starting, check count: 7
1970-01-01 00:05:52.651826 maca ERROR: init.lua(194): [soctrl]StartupCheck failed, error: initialization is not complete while checking the startup status, status: Starting, check count: 7
1970-01-01 00:05:52.702526 maca ERROR: init.lua(194): [spdm]StartupCheck failed, error: initialization is not complete while checking the startup status, status: Starting, check count: 7
1970-01-01 00:05:52.914723 maca ERROR: init.lua(194): [storage]StartupCheck failed, error: initialization is not complete while checking the startup status, status: Starting, check count: 7
1970-01-01 00:05:53.005849 maca ERROR: init.lua(194): [thermal_mgmt]StartupCheck failed, error: initialization is not complete while checking the startup status, status: Starting, check count: 7
1970-01-01 00:05:53.117007 maca ERROR: init.lua(194): [ums]StartupCheck failed, error: initialization is not complete while checking the startup status, status: Starting, check count: 7
1970-01-01 00:05:53.218021 maca ERROR: init.lua(194): [usb_entry]StartupCheck failed, error: initialization is not complete while checking the startup status, status: Starting, check count: 7
1970-01-01 00:05:53.319471 maca ERROR: init.lua(194): [vnc_proxy]StartupCheck failed, error: initialization is not complete while checking the startup status, status: Starting, check count: 7
1970-01-01 00:05:53.410487 maca ERROR: init.lua(194): [web_backend]StartupCheck failed, error: initialization is not complete while checking the startup status, status: Starting, check count: 7

Nath3y1r · 2026 年8 月 11 日 05:18

补充：10分后重启了，就没有上述错误，网络能够正常通信了

ubmc_assistant · 2026 年8 月 11 日 05:18

答案内容由AI生成，仅供参考：

总结

根据 Context 中的已知信息，您遇到的情况极有可能是组件依赖不一致或配置数据库损坏导致的服务初始化失败和网络不通。建议首先使用 ipmcset -d rollback 回滚到升级前版本确认业务恢复，再逐步排查新版本的组件依赖完整性。

若需进一步定位，请提供更详细的系统日志（如 app.log、init.lua 启动顺序日志）以便对照 Context 中的案例进行精确分析。

点击此处查看详细分析解答

根据您提供的日志，升级到 26.6 版本 后系统出现大量服务启动检查失败（StartupCheck failed）并且网络不通。结合所给 Context 中的信息，以下是对该问题的分析与建议。

可能原因分析

1. 组件依赖问题

您日志中绝大多数服务报错为：

initialization is not complete while checking the startup status, status: Starting

这表明服务初始化尚未完成，检查超时（check count: 7）。Context 中有一个完全类似的案例：用户 zhaower 在 [升级后起不来] 的问题中贴出大量 StartupCheck failed 日志（错误为 ServiceUnknown），其最终定位是 “bmc各个包组件依赖有问题”（参见文档块3）。
升级后各组件版本不一致或依赖关系未正确解决，可能导致某些关键服务（如 persistence、bmc_core）无法就绪，进而使依赖它们的服务一直处于 Starting 状态。

2. 配置数据库丢失或损坏

Context 中的搜索案例 [BMC升级固件后网络ping不通] 指出：固件升级后配置数据库可能丢失或损坏，导致网络IP未加载，同时影响其他服务的配置。其根本原因是：

bmc_network 服务未正常启动或读取网络配置失败；
用户配置未保留或未生效。
您的日志中 bmc_network 正是报错的服务之一，这与网络不通的症状吻合。

3. 签名/验证问题

知识图谱 提到 Invalid Upgrade Package 是系统校验签名失败导致的。如果升级包签名不匹配（例如用 HW 签名包升级 openUBMC），可能触发该错误，但您描述“升级成功”，故概率较低。不排除升级包本身兼容性问题。

4. 特定组件缺失

日志中 remote_console 报错与其他不同：

ServiceUnknown: The name bmc.kepler.remote_console was not provided by any .service files

这直接表明该组件的 .service 文件缺失或未正确注册，属于组件依赖或打包完整性问题。

建议解决方向

优先尝试：回滚到升级前版本

根据 Context 中同类问题的处理经验，回滚是快速恢复网络和服务的最直接方法。
在 BMC 串口或 SSH 下执行：

ipmcset -d rollback

将 BMC 切回备用分区启动，网络通常可恢复正常（参见搜索案例1）。

检查组件依赖

若需保留新版本，建议查看完整日志，确认哪个服务最先进入 Starting 状态且始终未完成。可参考 Context 中通用定位思路（文档块5）：

确定版本和构建时间；
结合日志定位异常点；
在异常点附近增加日志复现。

重点检查 persistence、bmc_core、firmware_mgmt 等基础服务是否正常启动。

其他排查点

不保留配置升级：如果升级时未保留配置，需确认网络配置是否重新生效。
签名与证书：自签名版本升级后可能因证书路径变更导致解密失败（搜索案例7），但该场景主要影响 Web 登录，与您大量服务报启动不完全相符。
NCSI 初始化：对于 PCIe 网口，若系统未正确触发 NCSI 初始化也可能导致网络不通（搜索案例10），但您的日志未涉及网口具体信息。

总结