升级2512后不能打开web无法使用ssh，maca提示web_backend和redfish报错

bmc_core SIG
1

2503升级2512LTS-SP1后可以telnet，但不能打开web无法使用ssh，maca提示web_backend和redfish报错。

串口报错：

image
image1419×348 206 KB

以下是：framework.log中 grep web， 附件是单独复制导出的framework和app.log

~ ~ # cat /var/log/framework.log |grep web
1970-01-01 08:00:29.103819 unknown_service NOTICE: base.lua(86): component[web_backend] is detected in the environment
2026-07-27 08:29:26.725264 [:0000000c] interface: LAUNCH snlua hica/subsys/interface/service/web_backend
2026-07-27 08:29:26.926353 [:0000000f] interface: LAUNCH snlua web_backend/service/portal_agent
1970-01-01 08:00:24.552255 unknown_service NOTICE: base.lua(89): component[web_backend] is detected in the environment
2025-05-26 16:22:42.492759 [:0000000d] interface: LAUNCH snlua hica/subsys/interface/service/web_backend
2025-05-26 16:22:42.618911 [:0000000f] interface: LAUNCH snlua web_backend/service/portal_agent
2026-07-27 09:32:44.327983 maca NOTICE: base.lua(384): monitor component web_backend added, service: bmc.kepler.web_backend [repeated 15 times in 26s from 2025-05-26 16:22:26.130651 to 2025-05-26 16:22:52.767545][flush]
2025-05-26 16:23:04.643745 maca NOTICE: init.lua(163): web_backend rebooting … prepare successfully, takes 220 ms
2025-05-26 16:23:09.009307 maca NOTICE: init.lua(172): web_backend rebooting … closed successfully, takes 100 ms
1970-01-01 08:00:26.415460 unknown_service NOTICE: base.lua(86): component[web_backend] is detected in the environment
2025-05-26 16:23:37.355764 [:0000000c] interface: LAUNCH snlua hica/subsys/interface/service/web_backend
2025-05-26 16:23:37.627908 [:0000000f] interface: LAUNCH snlua web_backend/service/portal_agent
1970-01-01 08:00:26.096526 unknown_service NOTICE: base.lua(86): component[web_backend] is detected in the environment
2026-07-27 09:46:35.449871 [:0000000c] interface: LAUNCH snlua hica/subsys/interface/service/web_backend
2026-07-27 09:46:35.759545 [:0000000f] interface: LAUNCH snlua web_backend/service/portal_agent
1970-01-01 08:00:25.058892 unknown_service NOTICE: base.lua(89): component[web_backend] is detected in the environment
2026-07-27 10:08:58.236484 [:0000000d] interface: LAUNCH snlua hica/subsys/interface/service/web_backend
2026-07-27 10:08:58.386429 [:0000000f] interface: LAUNCH snlua web_backend/service/portal_agent
2026-07-27 10:15:37.853449 maca NOTICE: base.lua(384): monitor component web_backend added, service: bmc.kepler.web_backend [repeated 15 times in 28s from 2026-07-27 10:08:41.729969 to 2026-07-27 10:09:09.289395][flush]
2026-07-27 10:23:17.965045 maca NOTICE: init.lua(163): web_backend rebooting … prepare successfully, takes 200 ms
2026-07-27 10:23:22.303097 maca NOTICE: init.lua(172): web_backend rebooting … closed successfully, takes 100 ms
1970-01-01 08:00:26.726243 unknown_service NOTICE: base.lua(86): component[web_backend] is detected in the environment
2026-07-27 10:23:51.177208 [:0000000c] interface: LAUNCH snlua hica/subsys/interface/service/web_backend
2026-07-27 10:23:51.392866 [:0000000e] interface: LAUNCH snlua web_backend/service/portal_agent
2026-07-27 10:35:39.932372 maca NOTICE: init.lua(287): web_backend rebooting … prepare successfully, takes 200 ms
2026-07-27 10:35:41.222350 maca NOTICE: init.lua(304): web_backend rebooting … process successfully, takes 110 ms
2026-07-27 10:35:44.517350 maca NOTICE: init.lua(316): web_backend rebooting … closed successfully, takes 110 ms
1970-01-01 08:00:25.951636 unknown_service NOTICE: base.lua(89): component[web_backend] is detected in the environment
2026-07-27 10:42:59.444703 maca NOTICE: base.lua(384): monitor component web_backend added, service: bmc.kepler.web_backend [repeated 15 times in 25s from 2026-07-27 10:35:58.513156 to 2026-07-27 10:36:23.745775][flush]
1970-01-01 08:00:26.111516 unknown_service NOTICE: base.lua(86): component[web_backend] is detected in the environment
2026-07-27 10:54:06.856451 [:0000000c] interface: LAUNCH snlua hica/subsys/interface/service/web_backend
2026-07-27 10:54:06.969373 [:0000000f] interface: LAUNCH snlua web_backend/service/portal_agent
2026-07-27 10:54:10.099072 maca ERROR: init.lua(191): [web_backend]StartupCheck failed, error: initialization is not complete while checking the startup status, status: Starting, check count: 1
2026-07-27 14:58:01.469430 maca NOTICE: init.lua(287): web_backend rebooting … prepare successfully, takes 240 ms
2026-07-27 14:58:02.850634 maca NOTICE: init.lua(304): web_backend rebooting … process successfully, takes 170 ms
2026-07-27 14:58:06.114238 maca NOTICE: init.lua(316): web_backend rebooting … closed successfully, takes 110 ms
1970-01-01 08:00:24.630068 unknown_service NOTICE: base.lua(89): component[web_backend] is detected in the environment
2026-07-27 14:58:35.556727 [:0000000d] interface: LAUNCH snlua hica/subsys/interface/service/web_backend
2026-07-27 14:58:35.699683 [:0000000f] interface: LAUNCH snlua web_backend/service/portal_agent
2026-07-27 15:11:27.072188 maca NOTICE: init.lua(163): web_backend rebooting … prepare successfully, takes 200 ms
2026-07-27 15:11:31.437764 maca NOTICE: init.lua(172): web_backend rebooting … closed successfully, takes 90 ms
1970-01-01 08:00:23.474029 unknown_service NOTICE: base.lua(89): component[web_backend] is detected in the environment
2026-07-27 15:12:00.768192 [:0000000d] interface: LAUNCH snlua hica/subsys/interface/service/web_backend
2026-07-27 15:12:00.859249 [:0000000f] interface: LAUNCH snlua web_backend/service/portal_agent
1970-01-01 08:00:26.101231 unknown_service NOTICE: base.lua(86): component[web_backend] is detected in the environment
2026-07-27 15:17:00.748469 [:0000000c] interface: LAUNCH snlua hica/subsys/interface/service/web_backend
2026-07-27 15:17:00.960505 [:0000000e] interface: LAUNCH snlua web_backend/service/portal_agent
2026-07-27 15:30:14.434782 maca NOTICE: init.lua(287): web_backend rebooting … prepare successfully, takes 160 ms
2026-07-27 15:30:15.787848 maca NOTICE: init.lua(304): web_backend rebooting … process successfully, takes 110 ms
2026-07-27 15:30:19.074895 maca NOTICE: init.lua(316): web_backend rebooting … closed successfully, takes 130 ms
1970-01-01 08:00:23.708203 unknown_service NOTICE: base.lua(89): component[web_backend] is detected in the environment
2026-07-27 15:30:48.722853 [:0000000d] interface: LAUNCH snlua hica/subsys/interface/service/web_backend
2026-07-27 15:30:49.013179 [:0000000f] interface: LAUNCH snlua web_backend/service/portal_agent
2026-07-27 15:34:27.133171 maca NOTICE: init.lua(163): web_backend rebooting … prepare successfully, takes 220 ms
1970-01-01 08:00:26.520236 unknown_service NOTICE: base.lua(86): component[web_backend] is detected in the environment
2026-07-27 15:34:59.662684 [:0000000c] interface: LAUNCH snlua hica/subsys/interface/service/web_backend
2026-07-27 15:34:59.813832 [:0000000f] interface: LAUNCH snlua web_backend/service/portal_agent
1970-01-01 08:00:24.633327 unknown_service NOTICE: base.lua(89): component[web_backend] is detected in the environment
2026-07-27 15:50:21.835901 [:0000000d] interface: LAUNCH snlua hica/subsys/interface/service/web_backend
2026-07-27 15:50:22.027068 [:0000000f] interface: LAUNCH snlua web_backend/service/portal_agent
2026-07-27 16:00:10.382366 maca NOTICE: base.lua(384): monitor component web_backend added, service: bmc.kepler.web_backend [repeated 15 times in 14s from 2026-07-27 15:50:13.345106 to 2026-07-27 15:50:27.278318][flush]
2026-07-27 16:06:27.295957 maca NOTICE: init.lua(163): web_backend rebooting … prepare successfully, takes 210 ms
2026-07-27 16:06:31.677324 maca NOTICE: init.lua(172): web_backend rebooting … closed successfully, takes 90 ms
1970-01-01 08:00:26.388737 unknown_service NOTICE: base.lua(86): component[web_backend] is detected in the environment
2026-07-27 16:07:01.014828 [:0000000c] interface: LAUNCH snlua hica/subsys/interface/service/web_backend
2026-07-27 16:07:01.204226 [:0000000f] interface: LAUNCH snlua web_backend/service/portal_agent
2026-07-27 16:30:38.259763 maca NOTICE: init.lua(287): web_backend rebooting … prepare successfully, takes 200 ms
2026-07-27 16:30:39.676270 maca NOTICE: init.lua(304): web_backend rebooting … process successfully, takes 150 ms
2026-07-27 16:30:43.002366 maca NOTICE: init.lua(316): web_backend rebooting … closed successfully, takes 160 ms
1970-01-01 08:00:26.059671 unknown_service NOTICE: base.lua(86): component[web_backend] is detected in the environment
2026-07-27 16:31:13.087256 [:0000000c] interface: LAUNCH snlua hica/subsys/interface/service/web_backend
2026-07-27 16:31:13.284333 [:0000000f] interface: LAUNCH snlua web_backend/service/portal_agent
1970-01-01 08:00:26.276103 unknown_service NOTICE: base.lua(86): component[web_backend] is detected in the environment
2026-07-27 17:02:05.395353 [:0000000c] interface: LAUNCH snlua hica/subsys/interface/service/web_backend
2026-07-27 17:02:05.584174 [:0000000e] interface: LAUNCH snlua web_backend/service/portal_agent
2026-07-27 17:02:08.858061 maca ERROR: init.lua(191): [web_backend]StartupCheck failed, error: initialization is not complete while checking the startup status, status: Starting, check count: 1

frame and web.tar (4.1 MB)

2

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

:hammer_and_wrench: 解决方案（基于上下文资料）

根据上下文中的 [搜索结果 1]（BMC 无网络升级问题分析）和 [文档块 3]（topic 2059 中的解决方案），最有效的处理方式是通过 串口/telnet 进入 BMC，将系统切换到备用分区并重新启动。

操作步骤（请通过 telnet 登录后执行）

  1. 进入 debug 模式（如当前不是 debug 模式）：
    /opt/debug/busybox telnet localhost
  2. 切换 BMC 到备用分区启动：
    ipmcset -d rollback
    （该命令在 topic 2059 中被确认可解决类似问题）
  3. 等待 BMC 重启，备用分区生效后，web_backend、redfish 及 sshd 等服务应能正常初始化。

说明：

  • 如果串口最初被切到 OS 侧（如搜索结果 1 所述），可能需要先执行 ipmcset -d serialdir -v 1 将串口切换回 BMC 侧，但您已能 telnet，此步可能省略。
  • 备用分区通常包含稳定的固件配置，升级失败或主分区损坏时通过 rollback 可恢复基本网络功能。

:pushpin: 总结

您遇到的问题与社区中多起“升级后 Web/SSH 不可用，仅串口/telnet 可登录”案例高度一致，优先尝试通过 ipmcset -d rollback 切换至备用分区，这是上下文中最直接且被验证有效的解决方案。如果切换后仍存在问题，建议检查 redfish 组件的启动日志（您提到 maca 也提示 redfish 报错，但此处未提供相关日志），并可参考 [映射器接口定位指导]（搜索结果 2）进一步调试 web_backend 接口响应超时等问题。

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

根据您提供的日志信息（framework.log 中关于 web_backend 的记录）以及上下文中的相关资料，您在将 BMC 从 2503 升级到 2512 LTS-SP1 版本后遇到 Web 无法打开、SSH 无法使用，但 telnet 可以正常登录。同时 maca 提示 web_backend 和 redfish 报错，日志中反复出现 web_backend 启动检查失败（状态始终为 Starting），表明相关服务未完成初始化。

:magnifying_glass_tilted_left: 问题分析

  • 核心现象：升级后主分区异常，导致 web_backend、redfish、sshd 等网络服务无法正常加载或配置失效。
  • 日志证据：
    • maca NOTICE 多次添加 monitor component web_backend added，但后续 StartupCheck failed, error: initialization is not complete while checking the startup status, status: Starting，说明服务进程未能完成启动流程。
    • web_backend 反复被 LAUNCH 但始终未就绪，符合“主分区异常”的特征。
  • 类似案例：上下文中的文档和搜索结果多次记录升级后 Web 与 SSH 不可用、仅串口/telnet 可登录的场景，并指出根本原因是 主分区文件系统或网络配置损坏。

:hammer_and_wrench: 解决方案（基于上下文资料）

根据上下文中的 [搜索结果 1]（BMC 无网络升级问题分析）和 [文档块 3]（topic 2059 中的解决方案），最有效的处理方式是通过 串口/telnet 进入 BMC，将系统切换到备用分区并重新启动。

操作步骤（请通过 telnet 登录后执行）

  1. 进入 debug 模式（如当前不是 debug 模式）：
    /opt/debug/busybox telnet localhost
  2. 切换 BMC 到备用分区启动：
    ipmcset -d rollback
    （该命令在 topic 2059 中被确认可解决类似问题）
  3. 等待 BMC 重启，备用分区生效后，web_backend、redfish 及 sshd 等服务应能正常初始化。

说明：

  • 如果串口最初被切到 OS 侧（如搜索结果 1 所述），可能需要先执行 ipmcset -d serialdir -v 1 将串口切换回 BMC 侧，但您已能 telnet，此步可能省略。
  • 备用分区通常包含稳定的固件配置，升级失败或主分区损坏时通过 rollback 可恢复基本网络功能。

:warning: 其他可能因素（参考上下文）

  • SSL 证书失效（搜索结果 8、9）：通常表现为 Web 无法登录但 SSH 正常，您的情况中 SSH 也失败，故可能性较低。
  • 服务依赖缺失：日志中未出现 DBus.Error.ServiceUnknown 类错误，但反复初始化失败仍可随分区切换解决。
  • Boot Policy 问题：实体 25.12 LTS_SP1 描述该版本存在 boot policy 执行问题，切换分区可绕过损坏的启动策略。

:pushpin: 总结

您遇到的问题与社区中多起“升级后 Web/SSH 不可用，仅串口/telnet 可登录”案例高度一致，优先尝试通过 ipmcset -d rollback 切换至备用分区，这是上下文中最直接且被验证有效的解决方案。如果切换后仍存在问题，建议检查 redfish 组件的启动日志（您提到 maca 也提示 redfish 报错，但此处未提供相关日志），并可参考 [映射器接口定位指导]（搜索结果 2）进一步调试 web_backend 接口响应超时等问题。

3

根据提供的日志，bmc在2026-07-27 17:01:40的时候重启，问题中提及的redfish组件和web_backend组件报错是在17:02:08左右在framework日志中打印，此时redfish组件和web_backend组件尚未初始化完成。
redfish组件是在17:02:34时初始化完成，web_backend组件是在17:02:15时初始化完成，可以查看app.log中start redfish service successfully和start web_backend service successfully日志确认，初始化完成后应当redfish和web功能正常