yexinru/doc-exports
1
0
Fork 0
forked from docs/doc-exports
Code Pull Requests Activity
Files
71d5c814e7cd147ecf1616dcdb847abdd12996f9
doc-exports/docs/cce/umn/cce_10_0495.html
qiujiandong1 71d5c814e7 CCE UMN 20250311 version 
Reviewed-by: Eotvos, Oliver <oliver.eotvos@t-systems.com>
Co-authored-by: qiujiandong1 <qiujiandong1@huawei.com>
Co-committed-by: qiujiandong1 <qiujiandong1@huawei.com>
2025-06-16 14:58:53 +00:00

2.1 KiB
Raw Blame History

Key Node Commands

Check Items

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

Solution

  • Scenario 1: Executing the package manager command failed.

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

    rpm -qa
    If the preceding command is unavailable, run the following command:
    rpm --rebuilddb
  • Scenario 2: The systemctl status command fails to be executed.

    If the systemctl status command on a node is unavailable, many check items will be affected. Log in to the node and check the availability of the following commands:

    systemctl status kubelet

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