samba_spnupdate invoked oom-killer ( samba BUG )

Chan Min Wai dcmwai at
Wed Oct 1 00:45:14 MDT 2014

Dear Volker,

Thank you for the effort.

However, I'm starting to wonder if this issue was caused by
non-active/unclear removed DC.

As during the testing phase, I've added an win2k8 AD DC but it was removed

So I was wondering if that was the cause...

The reason I've such a statement is that I've restart my samba yesterday on
2:xx am..

And when I check back this morning on 9am on the Samba AD memory usage. (no
one have login yet or make change to the DC as what I can see form the log)
We are a Buddhist society and office start at 10am...
I already found one process accumulating memory... (

So I was starting to suspect that...

Any suggestion?

I'll restart samba again and later increase debug log to 3 or 5...

Btw, just found that log.samba is not following the log files size stated
on smb.conf
I think we have an bugs :)

On Wed, Oct 1, 2014 at 12:44 PM, Volker Lendecke <Volker.Lendecke at>

> On Tue, Sep 30, 2014 at 11:46:24AM -0700, Richard Sharpe wrote:
> > On Tue, Sep 30, 2014 at 10:24 AM, Chan Min Wai <dcmwai at> wrote:
> > > Hi Richard,
> > >
> > > I think smbcontrol didn't work on samba daemon (the AD DC daemon)
> >
> > Ahhh, this is an AD DC problem. My experience is only with the file
> > server side of the code. I think you need other people to check in
> > here to figure this out.
> >
> > I seems like there is a leak. I would increase the log level to see if
> > I can see anything that is happening over and over again ...
> FYI: In the last weeks I've got smbcontrol working against the DC,
> so in the near future we'll have the infrastructure to do a debug or
> pool-usage message against the DC.
> Volker
> --
> SerNet GmbH, Bahnhofsallee 1b, 37081 Göttingen
> phone: +49-551-370000-0, fax: +49-551-370000-9
> AG Göttingen, HRB 2816, GF: Dr. Johannes Loxen
>, mailto:kontakt at

More information about the samba-technical mailing list