vpruthi/doc-exports
1
0
Fork 0
forked from docs/doc-exports
Code Pull Requests Activity
doc-exports/docs/mrs/umn/ALM-25005.html
Yang, Tong 3b1f73dece MRS UMN 2.0.38.SP20 version 
Reviewed-by: Hasko, Vladimir <vladimir.hasko@t-systems.com>
Co-authored-by: Yang, Tong <yangtong2@huawei.com>
Co-committed-by: Yang, Tong <yangtong2@huawei.com>
2022-12-13 12:03:34 +00:00

103 lines
20 KiB
HTML
Raw Permalink Blame History

<a name="ALM-25005"></a><a name="ALM-25005"></a>
<h1 class="topictitle1">ALM-25005 nscd Service Exception</h1>
<div id="body7501435"><div class="section" id="ALM-25005__section50910190"><h4 class="sectiontitle">Description</h4><p id="ALM-25005__p4908212810189">The system checks the status of the nscd service every 60 seconds. This alarm is generated when the nscd process fails to be queried for four consecutive times (three minutes) or users in LdapServer cannot be obtained.</p>
<p id="ALM-25005__p3908597210189">This alarm is cleared when the process is restored and users in LdapServer can be obtained.</p>
</div>
<div class="section" id="ALM-25005__section55538530"><h4 class="sectiontitle">Attribute</h4>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="ALM-25005__table26122451" frame="border" border="1" rules="all"><thead align="left"><tr id="ALM-25005__row66613897"><th align="left" class="cellrowborder" valign="top" width="33.33333333333333%" id="mcps1.3.2.2.1.4.1.1"><p id="ALM-25005__p27016537">Alarm ID</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="33.33333333333333%" id="mcps1.3.2.2.1.4.1.2"><p id="ALM-25005__p40855861">Alarm Severity</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="33.33333333333333%" id="mcps1.3.2.2.1.4.1.3"><p id="ALM-25005__p20990470">Auto Clear</p>
</th>
</tr>
</thead>
<tbody><tr id="ALM-25005__row22506548"><td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.2.2.1.4.1.1 "><p id="ALM-25005__p11091110">25005</p>
</td>
<td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.2.2.1.4.1.2 "><p id="ALM-25005__p25964741">Major</p>
</td>
<td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.2.2.1.4.1.3 "><p id="ALM-25005__p22769272">Yes</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
<div class="section" id="ALM-25005__section30084722"><h4 class="sectiontitle">Parameters</h4>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="ALM-25005__table32371752" frame="border" border="1" rules="all"><thead align="left"><tr id="ALM-25005__row57825413"><th align="left" class="cellrowborder" valign="top" width="50%" id="mcps1.3.3.2.1.3.1.1"><p id="ALM-25005__p53346883">Name</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="50%" id="mcps1.3.3.2.1.3.1.2"><p id="ALM-25005__p26130306">Meaning</p>
</th>
</tr>
</thead>
<tbody><tr id="ALM-25005__row105875515147"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.3.2.1.3.1.1 "><p id="ALM-25005__p13858113752316">Source</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.3.2.1.3.1.2 "><p id="ALM-25005__p187931338134115">Specifies the cluster for which the alarm is generated.</p>
</td>
</tr>
<tr id="ALM-25005__row36180074"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.3.2.1.3.1.1 "><p id="ALM-25005__p39123317">ServiceName</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.3.2.1.3.1.2 "><p id="ALM-25005__p13415506">Specifies the service for which the alarm is generated.</p>
</td>
</tr>
<tr id="ALM-25005__row53630695"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.3.2.1.3.1.1 "><p id="ALM-25005__p66118565">HostName</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.3.2.1.3.1.2 "><p id="ALM-25005__p19219236">Host for which the alarm is generated.</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
<div class="section" id="ALM-25005__section2327049"><h4 class="sectiontitle">Impact on the System</h4><p id="ALM-25005__p13254269">The alarmed node may not be able to synchronize data from LdapServer. The <strong id="ALM-25005__b52579114308">id</strong> command may fail to obtain the LDAP data, affecting upper-layer services.</p>
</div>
<div class="section" id="ALM-25005__section20943447"><h4 class="sectiontitle">Possible Causes</h4><ul id="ALM-25005__ul65794892"><li id="ALM-25005__li55283117">The nscd service is not started.</li><li id="ALM-25005__li27786007">The network is faulty, and cannot access the LDAP server.</li><li id="ALM-25005__li48747475">NameService is abnormal.</li><li id="ALM-25005__li5548315594719">Users cannot be queried because the OS executes commands too slowly.</li></ul>
</div>
<div class="section" id="ALM-25005__section54273301"><h4 class="sectiontitle">Procedure</h4><p class="tableheading" id="ALM-25005__p56231439"><strong id="ALM-25005__b165019239313">Check whether the nscd service is started.</strong></p>
<ol id="ALM-25005__ol5789446085120"><li id="ALM-25005__li453743808513"><span>Log in to FusionInsight Manager and choose <strong id="ALM-25005__b12494182917313">O&amp;M</strong> &gt; <strong id="ALM-25005__b350092973118">Alarm</strong> &gt; <strong id="ALM-25005__b350011296310">Alarms</strong>. Record the IP address of <strong id="ALM-25005__b39546411845110">HostName</strong> in <strong id="ALM-25005__b183475807745110">Location</strong> of the alarm as <strong id="ALM-25005__b178528359045110">IP1</strong> (if multiple alarms exist, record the IP addresses as <strong id="ALM-25005__b213125357445110">IP1</strong>, <strong id="ALM-25005__b205430910045110">IP2</strong>, and <strong id="ALM-25005__b198598191245110">IP3</strong> respectively).</span></li><li id="ALM-25005__li261355368513"><span>Contact the <span id="ALM-25005__text1943317301937">O&amp;M personnel</span> to access the node using IP1 as user <strong id="ALM-25005__b3849621192311">root</strong>. <span id="ALM-25005__text887612912517"></span> Run the <strong id="ALM-25005__b391761010255">ps -ef | grep nscd</strong> command on the node and check whether the <strong id="ALM-25005__b9132162613412">/usr/sbin/nscd</strong> process is started.</span><p><ul class="subitemlist" id="ALM-25005__ul476431918513"><li id="ALM-25005__li603620708513">If yes, go to <a href="#ALM-25005__li423153448513">5</a>.</li><li id="ALM-25005__li574894718513">If no, go to <a href="#ALM-25005__li600689958513">3</a>.</li></ul>
</p></li><li id="ALM-25005__li600689958513"><a name="ALM-25005__li600689958513"></a><a name="li600689958513"></a><span>Run the <strong id="ALM-25005__b366036668513">service nscd restart</strong> command as user <strong id="ALM-25005__b338932358513">root</strong> to restart the nscd service. Then run the <strong id="ALM-25005__b16579132019310">ps -ef | grep nscd</strong> command to check whether the nscd service is started.</span><p><ul class="subitemlist" id="ALM-25005__ul439570358513"><li id="ALM-25005__li418537468513">If yes, go to <a href="#ALM-25005__li67767558513">4</a>.</li><li id="ALM-25005__li347102768513">If no, go to <a href="#ALM-25005__li265529978513">15</a>.</li></ul>
</p></li><li id="ALM-25005__li67767558513"><a name="ALM-25005__li67767558513"></a><a name="li67767558513"></a><span>Wait for 5 minutes and run the ps -ef | grep nscd command again as user root. Check whether the service exists.</span><p><ul class="subitemlist" id="ALM-25005__ul638785098513"><li id="ALM-25005__li494296708513">If yes, go to <a href="#ALM-25005__li551461168513">11</a>.</li><li id="ALM-25005__li443803148513">If no, go to <a href="#ALM-25005__li265529978513">15</a>.</li></ul>
</p></li></ol>
<p class="tableheading" id="ALM-25005__p1052205885123"><strong id="ALM-25005__b162316302457">Check whether the network is faulty, and whether the LDAP server can be accessed.</strong></p>
<ol start="5" id="ALM-25005__ol1488617285145"><li id="ALM-25005__li423153448513"><a name="ALM-25005__li423153448513"></a><a name="li423153448513"></a><span>Log in to the alarmed node as user <strong id="ALM-25005__b609908008513">root</strong> and run the <strong id="ALM-25005__b120462898513">ping</strong> command to check whether the network connectivity between this node and the LdapServer node. is normal.</span><p><ul class="subitemlist" id="ALM-25005__ul485756728513"><li id="ALM-25005__li362253928513">If yes, go to <a href="#ALM-25005__li297764118513">6</a>.</li><li id="ALM-25005__li575930808513">If no, contact network administrators to troubleshoot the fault.</li></ul>
</p></li></ol>
<p class="tableheading" id="ALM-25005__p345278668513"><strong id="ALM-25005__b126372178487">Check whether the NameService is normal.</strong></p>
<ol start="6" id="ALM-25005__ol626802878524"><li id="ALM-25005__li297764118513"><a name="ALM-25005__li297764118513"></a><a name="li297764118513"></a><span>Log in to the alarmed node as user <strong id="ALM-25005__b452937778513">root</strong>. Run the <strong id="ALM-25005__b44461154332">cat /etc/nsswitch.conf</strong> command to check whether the <strong id="ALM-25005__b455051915491">passwd</strong>, <strong id="ALM-25005__b2509821164913">group</strong>, <strong id="ALM-25005__b133122634913">services</strong>, <strong id="ALM-25005__b49041281491">netgroup</strong>, and <strong id="ALM-25005__b8903631134917">aliases</strong> of NameService are correctly configured.</span><p><p class="litext" id="ALM-25005__p680118483528">The correct parameter configurations are as follows:</p>
<p class="litext" id="ALM-25005__p449173498513"><strong id="ALM-25005__b48911634115317">passwd</strong>: <strong id="ALM-25005__b16151237125317">compat ldap</strong>; <strong id="ALM-25005__b11691133813537">group</strong>: <strong id="ALM-25005__b1856344005317">compat ldap</strong>; <strong id="ALM-25005__b95657422531">services</strong>: <strong id="ALM-25005__b934064415535">files ldap</strong>; <strong id="ALM-25005__b0285124612531">netgroup</strong>: <strong id="ALM-25005__b195033480538">files ldap</strong>; <strong id="ALM-25005__b737212505533">aliases</strong>: <strong id="ALM-25005__b49563519535">files ldap</strong></p>
<ul class="subitemlist" id="ALM-25005__ul480477328513"><li id="ALM-25005__li144266538513">If yes, go to <a href="#ALM-25005__li11806553308">7</a>.</li><li id="ALM-25005__li277082588513">If no, go to <a href="#ALM-25005__li195824098513">9</a>.</li></ul>
</p></li><li class="subitemlist" id="ALM-25005__li11806553308"><a name="ALM-25005__li11806553308"></a><a name="li11806553308"></a><span>Log in to the alarmed node as user <strong id="ALM-25005__b2018125513301">root</strong>. Run the <strong id="ALM-25005__b17986746143316">cat /etc/nscd.conf</strong> command to check whether the <strong id="ALM-25005__b10446551105">enable-cache passwd</strong>, <strong id="ALM-25005__b18570297015">positive-time-to-live passwd</strong>, <strong id="ALM-25005__b12218412706">enable-cache group</strong>, and <strong id="ALM-25005__b382921717014">positive-time-to-live group</strong> in the configuration file are correctly configured.</span><p><p class="litext" id="ALM-25005__p519552316220">The correct parameter configurations are as follows:</p>
<p class="litext" id="ALM-25005__p4493185312444"><strong id="ALM-25005__b69201934621">enable-cache passwd</strong>: <strong id="ALM-25005__b2433125011312">yes</strong>; <strong id="ALM-25005__b7167139633">positive-time-to-live passwd</strong>:<strong id="ALM-25005__b1758474630"> </strong><strong id="ALM-25005__b1085917521239">600</strong>; <strong id="ALM-25005__b4731185517316">enable-cache group</strong>: <strong id="ALM-25005__b112981059038">yes</strong>; <strong id="ALM-25005__b136182031741">positive-time-to-live group</strong>: <strong id="ALM-25005__b2040619512417">3600</strong></p>
<ul class="subitemlist" id="ALM-25005__ul18596164343316"><li id="ALM-25005__li759684383317">If yes, go to <a href="#ALM-25005__li389947948513">8</a>.</li><li id="ALM-25005__li12596144312334">If no, go to <a href="#ALM-25005__li1648032715218">10</a>.</li></ul>
</p></li><li id="ALM-25005__li389947948513"><a name="ALM-25005__li389947948513"></a><a name="li389947948513"></a><span>Run the <strong id="ALM-25005__b630790898513">/usr/sbin/nscd -i group</strong> and <strong id="ALM-25005__b308408908513">/usr/sbin/nscd -i passwd</strong> commands as user <strong id="ALM-25005__b666611118513">root</strong>. Wait for 2 minutes and run the <strong id="ALM-25005__b91325558513">id admin</strong> and <strong id="ALM-25005__b150841338513">id backup/manager</strong> commands to check whether results can be queried.</span><p><ul class="subitemlist" id="ALM-25005__ul341589168513"><li id="ALM-25005__li138552658513">If yes, go to <a href="#ALM-25005__li551461168513">11</a>.</li><li id="ALM-25005__li485346778513">If no, go to <a href="#ALM-25005__li265529978513">15</a>.</li></ul>
</p></li><li id="ALM-25005__li195824098513"><a name="ALM-25005__li195824098513"></a><a name="li195824098513"></a><span>Run the <strong id="ALM-25005__b154088328513">vi /etc/nsswitch.conf</strong> command as user <strong id="ALM-25005__b13182816133016">root</strong>. Correct the configurations in <a href="#ALM-25005__li297764118513">6</a> and save the file. Run the <strong id="ALM-25005__b401559138513">service nscd restart</strong> command to restart the nscd service. Wait for 2 minutes and run the <strong id="ALM-25005__b258589028513">id admin</strong> and <strong id="ALM-25005__b314035268513">id backup/manager</strong> commands to check whether results can be queried.</span><p><ul class="subitemlist" id="ALM-25005__ul618281468513"><li id="ALM-25005__li606576968513">If yes, go to <a href="#ALM-25005__li551461168513">11</a>.</li><li id="ALM-25005__li143263348513">If no, go to <a href="#ALM-25005__li265529978513">15</a>.</li></ul>
</p></li><li class="subitemlist" id="ALM-25005__li1648032715218"><a name="ALM-25005__li1648032715218"></a><a name="li1648032715218"></a><span>Run the <strong id="ALM-25005__b0998165672114">vi /etc/<strong id="ALM-25005__b1992011817228">nscd</strong>.conf</strong> command as user <strong id="ALM-25005__b1322023213309">root</strong>. Correct the configurations in <a href="#ALM-25005__li11806553308">7</a> and save the file. Run the <strong id="ALM-25005__b17999456142117">service nscd restart</strong> command to restart the nscd service. Wait for 2 minutes and run the <strong id="ALM-25005__b12010577215">id admin</strong> and <strong id="ALM-25005__b6135712119">id backup/manager</strong> commands to check whether results can be queried.</span><p><ul class="subitemlist" id="ALM-25005__ul17670172719234"><li id="ALM-25005__li167182702318">If yes, go to <a href="#ALM-25005__li551461168513">11</a>.</li><li id="ALM-25005__li2673427122312">If no, go to <a href="#ALM-25005__li265529978513">15</a>.</li></ul>
</p></li><li id="ALM-25005__li551461168513"><a name="ALM-25005__li551461168513"></a><a name="li551461168513"></a><span>Log in to the FusionInsight Manager portal. Wait for 5 minutes and check whether the <strong id="ALM-25005__b139171328161013">nscd Service Exception</strong> alarm is cleared.</span><p><ul class="subitemlist" id="ALM-25005__ul338209968513"><li id="ALM-25005__li420239548513">If yes, no further action is required.</li><li id="ALM-25005__li484971318513">If no, go to <a href="#ALM-25005__li1693832195142">12</a>.</li></ul>
</p></li></ol>
<p id="ALM-25005__p5952995695130"><strong id="ALM-25005__b1665813015129">Check whether frame freezing occurs when running a command in the operating system.</strong></p>
<ol start="12" id="ALM-25005__ol6332748195146"><li id="ALM-25005__li1693832195142"><a name="ALM-25005__li1693832195142"></a><a name="li1693832195142"></a><span>Log in to the faulty node as user <strong id="ALM-25005__b11121947111212">root</strong>, run the <strong id="ALM-25005__b13740145013123">id admin</strong> command, and check whether the command execution takes a long time. If the command execution takes more than 3 seconds, the command execution is deemed to be slow.</span><p><ul id="ALM-25005__ul5786251201614"><li id="ALM-25005__li1978645111167">If yes, go to <a href="#ALM-25005__li97084049527">13</a>.</li><li id="ALM-25005__li184201857151619">If no, go to <a href="#ALM-25005__li265529978513">15</a>.</li></ul>
</p></li><li id="ALM-25005__li97084049527"><a name="ALM-25005__li97084049527"></a><a name="li97084049527"></a><span>Run the <strong id="ALM-25005__b146463243139">cat /var/log/messages</strong> command to check whether the nscd frequently restarts or the error information "Can't contact LDAP server" exists.</span><p><p id="ALM-25005__p11707118192216">nscd exception example:</p>
<pre class="screen" id="ALM-25005__screen44522890192216">Feb 11 11:44:42 10-120-205-33 nscd: nss_ldap: failed to bind to LDAP server ldaps://10.120.205.55:21780: Can't contact LDAP server
Feb 11 11:44:43 10-120-205-33 ntpq: nss_ldap: failed to bind to LDAP server ldaps://10.120.205.55:21780: Can't contact LDAP server
Feb 11 11:44:44 10-120-205-33 ntpq: nss_ldap: failed to bind to LDAP server ldaps://10.120.205.92:21780: Can't contact LDAP server</pre>
<ul id="ALM-25005__ul19513155917426"><li id="ALM-25005__li2051325914425">If yes, go to <a href="#ALM-25005__li3335145595227">14</a>.</li><li id="ALM-25005__li183279218430">If no, go to <a href="#ALM-25005__li265529978513">15</a>.</li></ul>
</p></li><li id="ALM-25005__li3335145595227"><a name="ALM-25005__li3335145595227"></a><a name="li3335145595227"></a><span>Run the <strong id="ALM-25005__b649133011141">vi$BIGDATA_HOME/tmp/random_ldap_ip_order</strong> command to modify the number at the end. If the original number is an odd number, change it to an even number. If the number is an even number, change it to an odd number.</span><p><p id="ALM-25005__p141391942154312">Run the <strong id="ALM-25005__b333422699598">vi /etc/ldap.conf</strong> command to enter the editing mode, press <strong id="ALM-25005__b9226171119164">Insert</strong> to start editing, and then change the first two IP addresses of the URI configuration item.</p>
<p id="ALM-25005__p16428195735419">After the modification is complete, press <strong id="ALM-25005__b891972711616">Esc</strong> to exit the editing mode and enter <strong id="ALM-25005__b7927627131617">:wq!</strong> to save the settings and exit.</p>
<p id="ALM-25005__p5844123595130">Run the <strong id="ALM-25005__b1125212171">service nscd restart</strong> command to restart the nscd service. Wait 5 minutes and run the <strong id="ALM-25005__b472813891714">id admin</strong> command again. Check whether the command execution is slow.</p>
<ul id="ALM-25005__ul456516233175"><li id="ALM-25005__li105651423171716">If yes, go to <a href="#ALM-25005__li265529978513">15</a>.</li><li id="ALM-25005__li9911133361717">If no, log in to other faulty nodes and repeat <a href="#ALM-25005__li1693832195142">12</a> to <a href="#ALM-25005__li3335145595227">14</a> to check whether the first LdapServer node in the URI before modifying <strong id="ALM-25005__b1999374061818">/etc/ldap.conf</strong> is faulty. For example, check whether the service IP address is unreachable, the network delay is too long, or other abnormal software is deployed.</li></ul>
</p></li></ol>
<p class="tableheading" id="ALM-25005__p359535088513"><strong id="ALM-25005__b6450918385158">Collect the fault information.</strong></p>
<ol start="15" id="ALM-25005__ol1809837885210"><li id="ALM-25005__li265529978513"><a name="ALM-25005__li265529978513"></a><a name="li265529978513"></a><span>On FusionInsight Manager, choose <strong id="ALM-25005__b196113421692">O&amp;M</strong>. In the navigation pane on the left, choose <strong id="ALM-25005__b89621942798">Log</strong> &gt; <strong id="ALM-25005__b16962194211914">Download</strong>.</span></li><li id="ALM-25005__li376503848513"><span>Expand the drop-down list next to the <strong id="ALM-25005__b7845185121912">Service</strong> field. In the <strong id="ALM-25005__b1685425118194">Services</strong> dialog box that is displayed, select <strong id="ALM-25005__b15854195131911">LdapClient</strong> for the target cluster.</span></li><li id="ALM-25005__li33091438513"><span>Click <span><img id="ALM-25005__image03035992019" src="en-us_image_0263895532.png"></span> in the upper right corner, and set <strong id="ALM-25005__b5303894203">Start Date</strong> and <strong id="ALM-25005__b1530320913200">End Date</strong> for log collection to 1 hour ahead of and after the alarm generation time, respectively. Then, click <strong id="ALM-25005__b43040920205">Download</strong>.</span></li><li id="ALM-25005__li667140178513"><span>Contact <span id="ALM-25005__text0796181118205">O&amp;M personnel</span> and provide the collected logs.</span></li></ol>
</div>
<div class="section" id="ALM-25005__section169311343318"><h4 class="sectiontitle">Alarm Clearing</h4><p id="ALM-25005__p754913417333">This alarm is automatically cleared after the fault is rectified.</p>
</div>
<div class="section" id="ALM-25005__section18697669"><h4 class="sectiontitle">Related Information</h4><p id="ALM-25005__p41271913">None</p>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="mrs_01_1298.html">Alarm Reference (Applicable to MRS 3.x)</a></div>
</div>
</div>
View Git Blame Copy Permalink