![]() ![]() If the status of the node is Unknown, perform the following steps to troubleshoot the issue:Ĭheck whether the status of the Elastic Compute Service (ECS) instance that hosts the node is Running.Ĭheck the network connectivity of the node. ![]() If the resource usage is abnormal, refer to Insufficient CPU resources and Insufficient memory resources - MemoryPressure. For more information, see Check the monitoring data of nodes. For more information, see Check the diagnostic logs of nodes.Ĭheck the monitoring data of the node, including the usage of CPU, memory, and network resources. If the NTP service experiences an exception, refer to NTP exceptions - NTPProblem.Ĭheck the diagnostic log of the node. For more information, see Check the key components of nodes. If containerd experiences an exception, refer to Containerd exceptions - RuntimeOffline.Ĭheck the status, log, and configuration of the NTP service. If dockerd experiences an exception, refer to Dockerd exceptions - RuntimeOffline.Ĭheck the status, log, and configuration of containerd. If the kubelet experiences an exception, refer to Kubelet exceptions.Ĭheck the status, log, and configuration of dockerd. For more information, see Dockerd exceptions - RuntimeOffline, Insufficient memory resources - MemoryPressure, and Insufficient inodes - InodesPressure.Ĭheck the key components and logs of nodes.Ĭheck the status, log, and configuration of the kubelet. If one of the node conditions is True, troubleshoot the issue based on the keyword of the node condition. If the status of a node is NotReady, perform the following steps to troubleshoot the issue:Ĭheck whether the values of the following node conditions are True: PIDPressure, DiskPressure, and MemoryPressure. For more information, see Check node status. How do I resolve the issue that the disk I/O utilization of the auditd process is high or the following error message appears in the system log: audit: backlog limit exceeded?Ĭheck whether the status of a node is abnormal. Insufficient IP addresses - InvalidVSwitchId.IpNotEnough Insufficient memory resources - MemoryPressure ![]() Insufficient node resources for scheduling ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |