Updated on 2025-09-15 GMT+08:00

Key Node Commands

Check Items

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

Solution

  • 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.