repeating nscd monitoring messages after update to 11.52.0.14

[kernow]

Thanks for the update
We estimate that NSCD is adding around 3 to 4,000 lines an hour to /var/log/messages so we have disabled the NSCD daemon until you have a fix for it.

 

[blalow]

indeed!

Here is how to turn it off

/etc/init.d/nscd stop
chkconfig --levels 2345 nscd off

Not sure if this service is "monitored". I will see if my phone gets a hundred texts

 

[kernow]

By default it is monitored, it can be disabled in >>>WHM>>>Service Manager>>>Name Service Cache Daemon

 

[feanorknd]

Having this stats, I preffer to disable nscd service, sincerely...

In previous answer from me, I did tell how to configure nscd.conf to disable logging to messages by sending logs to /dev/null... but I also have seen nscd frequently at top, using considerable resources, so this is useless at all.

nscd -g
configuración nscd:

1 nivel de depuración del servidor
4d 13h 7m 0s tiempo de funcionamiento del servidor
17 current number of threads
32 maximum number of threads
13 number of times clients had to wait
no paranoia mode enabled
3600 restart internal
5 reload count

passwd cache:

yes cache is enabled
yes cache is persistent
yes cache is shared
211 suggested size
216064 total data pool size
1368 used data pool size
600 seconds time to live for positive entries
20 seconds time to live for negative entries
1464371 cache hits on positive entries
437746 cache hits on negative entries
7259857 cache misses on positive entries
59600 cache misses on negative entries
20% cache hit rate
14 current number of cached values
471 maximum number of cached values
10 maximum chain length searched
21 number of delays on rdlock
27 number of delays on wrlock
0 memory allocations failed
yes check /etc/passwd for changes

group cache:

yes cache is enabled
yes cache is persistent
yes cache is shared
211 suggested size
1264347 total data pool size
1133120 used data pool size
3600 seconds time to live for positive entries
60 seconds time to live for negative entries
7959 cache hits on positive entries
9107 cache hits on negative entries
4267214 cache misses on positive entries
670086 cache misses on negative entries
0% cache hit rate
7 current number of cached values
486 maximum number of cached values
10 maximum chain length searched
10 number of delays on rdlock
12 number of delays on wrlock
0 memory allocations failed
yes check /etc/group for changes

hosts cache:

yes cache is enabled
yes cache is persistent
yes cache is shared
211 suggested size
216064 total data pool size
31064 used data pool size
7200 seconds time to live for positive entries
60 seconds time to live for negative entries
13380 cache hits on positive entries
1891 cache hits on negative entries
142242 cache misses on positive entries
617074 cache misses on negative entries
1% cache hit rate
234 current number of cached values
479 maximum number of cached values
15 maximum chain length searched
12 number of delays on rdlock
0 number of delays on wrlock
0 memory allocations failed
yes check /etc/hosts for changes

services cache:

yes cache is enabled
yes cache is persistent
yes cache is shared
211 suggested size
216064 total data pool size
544 used data pool size
28800 seconds time to live for positive entries
20 seconds time to live for negative entries
0 cache hits on positive entries
0 cache hits on negative entries
68 cache misses on positive entries
26 cache misses on negative entries
0% cache hit rate
5 current number of cached values
15 maximum number of cached values
1 maximum chain length searched
0 number of delays on rdlock
0 number of delays on wrlock
0 memory allocations failed
yes check /etc/services for changes

netgroup cache:

no cache is enabled
no cache is persistent
no cache is shared
0 suggested size
0 total data pool size
0 used data pool size
28800 seconds time to live for positive entries
20 seconds time to live for negative entries
0 cache hits on positive entries
0 cache hits on negative entries
0 cache misses on positive entries
0 cache misses on negative entries
0% cache hit rate
0 current number of cached values
0 maximum number of cached values
0 maximum chain length searched
0 number of delays on rdlock
0 number of delays on wrlock
0 memory allocations failed
yes check /etc/netgroup for changes

 

[gryzli]

We too have struggled with the "nscd madness".
========
Guys(cPanel ones), enabling those kind of services "by default" while they weren't running is a really "crap deployment behaviour".

This service almost killed multiple hypervisors with bunch of cPanel-based VPS's.
========


Given the fact that the service is "monitored" by default and /etc/init.d/nscd stop is ineffective, please provide solution for:
- Disabling NSCD and disabling it from tailwatchd, with command line only tools

If anybody else needs to "fast disable" nscd on a hundred/thousands of servers, here is what I've done (until cPanel provide "good way of disabling it"):

mv /usr/sbin/nscd{,.bak}
pkill -9 -f nscd

Update: The right way to disable NSCD (suggested by cPanel support)

# This disables nscd in Tailwatchd
touch /etc/nscddisable ; /scripts/restartsrv nscd

# This disables nscd in init.d
chkconfig off nscd

 

[cPanelMichael]

Hello

To update, a resolution associated with internal case CPANEL-2581 is included in cPanel version 54:

Fixed case CPANEL-2581: Suppressed log noise from NSCD by sending it to /dev/null.

cPanel version 54 is currently available in the "Current" and "Edge" build tiers:

cPanel & WHM Versions and the Release Process - cPanel Knowledge Base - cPanel Documentation

Thank you.