yexinru/doc-exports
1
0
Fork 0
forked from docs/doc-exports
Code Pull Requests Activity
Files
a41a4e0331fbc0beff63bb28fa59228cc9a751df
doc-exports/docs/cce/umn/cce_10_0495.html
qiujiandong1 ab1e53a279 CCE UMN 20251031 version 
Reviewed-by: Gergo-Bence Lorincz <a200452876@noreply.gitea.eco.tsi-dev.otc-service.com>
Co-authored-by: qiujiandong1 <qiujiandong1@huawei.com>
Co-committed-by: qiujiandong1 <qiujiandong1@huawei.com>
2026-01-15 10:25:22 +00:00

2.8 KiB
Raw Blame History

Key Node Commands

Check Items

Whether some key commands that the node upgrade depends on are working

Solutions

  • Scenario 1: Executing the RPM package manager command failed.

    Executing rpm failed. In this case, log in to the affected node and check whether the following command is available:

    rpm -qa
    If the command cannot be used, run the following command:
    rpm --rebuilddb

    If the fault persists, reset the node. For details, see Resetting a Node.

  • Scenario 2: Executing the dpkg package manager command failed.
    Executing dpkg failed. In this case, log in to the affected node and check whether the following command is available:
    dpkg -l

    If the command cannot be used, reset the node. For details, see Resetting a Node.

  • Scenario 2: Executing systemctl status failed.

    If systemctl status cannot be used on a node, many check items will fail. In this case, log in to the affected node and check whether the following command is available:

    systemctl status kubelet

    If systemctl cannot be used, reset the node. For details, see Resetting a Node.