[Samba] winbind causes Linux to lockup when connectivity to AD is lost (subject line edited for clarity)
Jeremy Allison
jra at samba.org
Fri Oct 23 18:45:30 MDT 2009
On Fri, Oct 23, 2009 at 02:34:45PM -0600, Robert LeBlanc wrote:
> 3.4.2
>
> Robert LeBlanc
> Life Sciences & Undergraduate Education Computer Support
> Brigham Young University
>
>
> On Fri, Oct 23, 2009 at 1:23 PM, Jeremy Allison <jra at samba.org> wrote:
>
> On Fri, Oct 23, 2009 at 01:19:46PM -0600, Robert LeBlanc wrote:
> > Here is a capture of top at the time:
> >
> > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
> > 5842 root 20 0 873m 6912 4612 S 0.0 0.4 0:01.20 winbindd
> > 5848 root 20 0 872m 3260 2272 S 0.0 0.2 0:00.08 winbindd
> > 5849 root 20 0 872m 3640 2652 S 0.0 0.2 0:00.06 winbindd
> > 5850 root 20 0 872m 3320 2200 S 0.0 0.2 0:00.06 winbindd
> > 5859 root 20 0 874m 2684 1448 S 0.0 0.2 0:00.00 winbindd
> > 5954 root 20 0 872m 3740 2284 S 0.0 0.2 0:00.02 winbindd
> > 5955 root 20 0 872m 3804 2348 S 0.0 0.2 0:00.04 winbindd
> > 6025 root 20 0 873m 1544 4 S 0.0 0.1 0:00.00 winbindd
> > 6026 root 20 0 873m 1548 4 S 0.0 0.1 0:00.00 winbindd
> > 6518 root 20 0 873m 5048 3476 S 0.0 0.3 0:00.00 winbindd
> > 6576 root 20 0 873m 6228 4232 S 0.0 0.4 0:00.00 winbindd
> > 5 root RT -5 0 0 0 S 0.0 0.0 0:00.00 watchdog/0
> > 529 root 16 -4 21076 632 0 S 0.0 0.0 0:00.16 udevd
> > 6574 root 20 0 18824 1264 940 R 0.0 0.1 0:00.10 top
> > 1761 root 20 0 5904 320 184 S 0.0 0.0 0:00.06 syslogd
> > 1805 root 20 0 48868 720 216 S 0.0 0.0 0:00.00 sshd
> > 5768 root 20 0 78572 916 200 S 0.0 0.1 0:00.14 sshd
>
> Well 873m is a little excessive, even for virtual memory :-).
> That's a memory leak I'd guess. What winbindd version is this ?
Ok, can you get a message pool usage dump by doing:
smbcontrol <pid> pool-usage
on one of the monstrous winbindd processes please ?
Thanks,
Jeremy.
More information about the samba
mailing list