forked from docs/doc-exports
qiujiandong1
ab1e53a279
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>
19 lines
2.4 KiB
HTML
19 lines
2.4 KiB
HTML
<a name="cce_10_0484"></a><a name="cce_10_0484"></a>
|
|
|
|
<h1 class="topictitle1">Health of Worker Node Components</h1>
|
|
<div id="body0000001421064718"><div class="section" id="cce_10_0484__section28521495319"><h4 class="sectiontitle">Check Items</h4><p id="cce_10_0484__p112379577523">Check whether the container runtime and network components on the worker nodes are healthy.</p>
|
|
</div>
|
|
<div class="section" id="cce_10_0484__section13523191085314"><h4 class="sectiontitle">Solutions</h4><ul id="cce_10_0484__ul196721478317"><li id="cce_10_0484__li1767217471935">Scenario 1: CNI Agent is not active.<p id="cce_10_0484__p158895476381"><a name="cce_10_0484__li1767217471935"></a><a name="li1767217471935"></a>If your cluster version is earlier than v1.17.17, or you are using the tunnel network model and your cluster version is later than v1.17.17, log in to the node and run the <strong id="cce_10_0484__b988934783814">systemctl status canal</strong> command to check the status of canal. If you encounter an error, run the <strong id="cce_10_0484__b198895477385">systemctl restart canal</strong> command and check the status again.</p>
|
|
<p id="cce_10_0484__p185971114131016">If you are using the VPC or Cloud Native 2.0 network model and your cluster version is later than v1.17.17, log in to the node and run the <strong id="cce_10_0484__b1637241092119">systemctl status yangtse</strong> command to check the status of Yangtse. If you encounter an error, run the <strong id="cce_10_0484__b437215104210">systemctl restart yangtse</strong> command and check the status again.</p>
|
|
</li><li id="cce_10_0484__li61022071156">Scenario 2: kube-proxy is not active.<p id="cce_10_0484__p1759325902311"><a name="cce_10_0484__li61022071156"></a><a name="li61022071156"></a>Log in to the node and run the <strong id="cce_10_0484__b1959210599233">systemctl is-active kube-proxy</strong> command to check the status of kube-proxy. If you encounter an error, run the <strong id="cce_10_0484__b9593859102316">systemctl restart kube-proxy</strong> command and check the status again.</p>
|
|
<p id="cce_10_0484__p19943863248">If the fault persists, reset the node. For details, see <a href="cce_10_0003.html">Resetting a Node</a>.</p>
|
|
</li></ul>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="cce_10_0550.html">Troubleshooting for Pre-upgrade Check Exceptions</a></div>
|
|
</div>
|
|
</div>
|
|
|