doc-exports/docs/ces/umn/ces_faq_0025.html
gtema f6f2ca6fa5 Update CES UMN
Reviewed-by: Hasko, Vladimir <vladimir.hasko@t-systems.com>
Co-authored-by: gtema <artem.goncharov@gmail.com>
Co-committed-by: gtema <artem.goncharov@gmail.com>
2022-12-07 15:46:48 +00:00

16 lines
1.7 KiB
HTML

<a name="ces_faq_0025"></a><a name="ces_faq_0025"></a>
<h1 class="topictitle1">What Should I Do If the Agent Status Is Faulty?</h1>
<div id="body8662426"><p id="ces_faq_0025__en-us_topic_0079656481_p41172973201744">The OS monitoring Agent sends a heartbeat message to Cloud Eye every minute. If Cloud Eye does not receive any heartbeat messages for 3 minutes, <strong id="ces_faq_0025__en-us_topic_0079656481_b84235270615649">Agent Status</strong> is displayed as <strong id="ces_faq_0025__en-us_topic_0079656481_b84235270615657">Faulty</strong>.</p>
<p id="ces_faq_0025__en-us_topic_0079656481_p35012440201744">It may because:</p>
<ul id="ces_faq_0025__ul18394154618393"><li id="ces_faq_0025__li684205315395">The account is in arrears.</li><li id="ces_faq_0025__li48746815406">If the Agent process is faulty, restart it by following the instructions provided in <a href="ces_01_0035.html">Managing the Agent</a>. If the restart fails, related files have been deleted by mistake. In this case, reinstall the Agent.</li></ul>
<p id="ces_faq_0025__p1297596134116">It may be that the Agent is incorrectly configured. Check whether the DNS server address is correct. If it is, check the Agent configurations by referring to <a href="en-us_topic_0150354069.html">Modifying the DNS Server Address and Adding Security Group Rules (Linux)</a> and <a href="ces_01_0031.html">(Optional) Manually Configuring the Agent (Linux)</a>.</p>
<p id="ces_faq_0025__p197061950131817">Locate the cause in log <strong id="ces_faq_0025__b644264116388">/usr/local/telescope/log/common.log</strong>. </p>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="ces_faq_0059.html">Server Monitoring</a></div>
</div>
</div>