With higher debug level I see that sssd sudo trying to resolve local account (for nagios monitoring)
Vasek On Tue, May 26, 2015 at 6:39 AM, Vaclav Adamec <[email protected]> wrote: > ps -eo pid,cmd,size,rss | grep sssd_sudo > 1533 /usr/libexec/sssd/sssd_sudo 4245972 4247700 > > and huge amount of this (trying again and again): > > (Tue May 26 06:35:47 2015) [sssd[sudo]] > [sudosrv_check_user_dp_callback] (0x0040): Could not look up the user > [2]: No such file or directory > (Tue May 26 06:35:47 2015) [sssd[sudo]] [sudosrv_get_user] (0x0080): > No results for getpwnam call > > but other servers in same datacenter looks ok in the same time, but > later this error was visible also on others, it's just question of > time. > > > On Mon, May 25, 2015 at 7:41 AM, Lukas Slebodnik <[email protected]> wrote: >> On (25/05/15 07:30), Vaclav Adamec wrote: >>>Hi, >>> after last update I see this: >>> >>> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND >>> 5918 root 20 0 4413m 4.1g 1596 S 2.8 35.4 31:12.72 sssd_sudo >>> >>>sssd-common-1.11.6-30.el6_6.4.x86_64 on CentOS release 6.6 final (up2date) >>> >>>restart, sync + swap cleanup and in less then 24h I get same memory usage. >>> >> Could you draw a graph of sssd_sudo memory usage? >> or at least gather data >> (ps -eo pid,cmd,size,rss | grep sssd_sudo) >> >> Can you see any errors in sssd_sudo log after enabling verbose logging? >> https://fedorahosted.org/sssd/wiki/Troubleshooting#SSSDdebuglogs >> >> LS > > > > -- > -- May the fox be with you ... > /\ > (~( > ) ) /\_/\ > (_=---_(@ @) > ( \ / > /|/----\|\ V > " " " " -- -- May the fox be with you ... /\ (~( ) ) /\_/\ (_=---_(@ @) ( \ / /|/----\|\ V " " " " -- Manage your subscription for the Freeipa-users mailing list: https://www.redhat.com/mailman/listinfo/freeipa-users Go to http://freeipa.org for more info on the project
