Possible samba4 / winbind memory leak?
abartlet at samba.org
Tue Apr 2 00:41:54 MDT 2013
On Tue, 2013-04-02 at 13:45 +1300, Andrew Walters wrote:
> Hi all,
> I've got five samba4 deployments across three sites, all now on release 4.0.4.
> You can see from the amount of free mem vs swap used that it was
> heavily loaded before the killall (sorry forgot to get a snapshot of
> top before doing the killall). Interestingly this process is
> completely idle. Because it won't respond to a SIGTERM, I don't think
> I'm going to get a leak report from it.
There are still ways to debug this, if you still have the process
around. Ricky Nance (CC'ed) is the expert in this, so I've CC'ed him.
Essentially, what we need you to do is attach with gdb:
gdb -p <pid>
and then get me:
(because if it isn't responding to a sigkill, then it will be in an
infinite loop somewhere, and we want to know where that is).
Then you run:
p talloc_report_full(0, stderr)
You already have my GPG key, so encrypt the info to that key.
Andrew Bartlett http://samba.org/~abartlet/
Authentication Developer, Samba Team http://samba.org
More information about the samba-technical