Often Linux systems are connected to LDAP via sssd. A high CPU consuming sssd can be seen in top, like below ( e.g. 89.4 % CPU usage):<\/p>\n
One reason could be default configuration of \/etc\/nsswitch.conf:<\/p>\n This configuration causes sssd_nss contacted by every user \/ group lookup if in local databases nothing is found, which may result in looping sssd_nss.<\/p>\n This \/etc\/nsswitch.conf configuration may help:<\/p>\n Now first the local files are queried before sssd is contacted.<\/p>\n What also may help is to clear sssd cache after change of \/etc\/nsswitch.conf:<\/p>\n Often Linux systems are connected to LDAP via sssd. A high CPU consuming sssd can be seen in top, like below ( e.g. 89.4 % CPU usage): 9020 root 20 0 1296344 466780 333364 R 89.4 0.8 41:20.17 sssd_nss 27227 oracle 20 0 2371676 48320 29732 S 4.3 0.1 27:00.70 oracle One reason could be […]<\/p>\n","protected":false},"author":27,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[229],"tags":[],"type_dbi":[],"class_list":["post-12214","post","type-post","status-publish","format-standard","hentry","category-database-administration-monitoring"],"acf":[],"yoast_head":"\n
\n 9020 root 20 0 1296344 466780 333364 R 89.4 0.8 41:20.17 sssd_nss
\n27227 oracle 20 0 2371676 48320 29732 S 4.3 0.1 27:00.70 oracle
\n<\/code><\/p>\n
\npasswd: db sss files
\nshadow: db sss files
\ngroup: db sss files
\n<\/code><\/p>\n
\npasswd: db files sss
\nshadow: db files sss
\ngroup: db files sss
\n<\/code><\/p>\n
\nsystemctl stop sssd
\nrm -rf \/var\/lib\/sss\/db\/*
\nsystemctl start sssd
\n<\/code><\/p>\n","protected":false},"excerpt":{"rendered":"