samba_spnupdate invoked oom-killer ( samba BUG )

[Richard Sharpe]

On Tue, Sep 30, 2014 at 10:24 AM, Chan Min Wai <dcmwai at gmail.com> 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 ...

> I can see the smbd info but it wasn't what I'm looking for as it have a
> different PID and the memory look fine.
>
> It seem that something lockup, odd enough...
>
>
> root      3408  0.0  0.5 548476 46596 ?        Ss   Sep29   0:00
> /usr/sbin/samba
> root      3412  0.0  0.4 548476 33168 ?        S    Sep29   0:00
> /usr/sbin/samba
> root      3413  0.8  0.4 553048 39368 ?        S    Sep29  22:49
> /usr/sbin/samba
> root      3414  0.0  0.7 489980 59824 ?        Ss   Sep29   0:15
> /usr/sbin/smbd -D --option=server role check:inhibit=yes --foreground
> root      3415  0.0  0.4 552608 35860 ?        S    Sep29   0:02
> /usr/sbin/samba
> root      3416  0.0  0.4 548476 33044 ?        S    Sep29   0:00
> /usr/sbin/samba
> root      3417  0.0  0.5 548876 41636 ?        S    Sep29   0:39
> /usr/sbin/samba
> root      3418  0.0  0.4 548456 34880 ?        S    Sep29   0:04
> /usr/sbin/samba
> root      3419  0.0  0.4 552628 38192 ?        S    Sep29   0:07
> /usr/sbin/samba
> root      3420  3.9 19.2 2101544 1576456 ?     S    Sep29 108:51
> /usr/sbin/samba
> root      3421  0.0  0.4 551856 35532 ?        S    Sep29   0:51
> /usr/sbin/samba
> root      3422  0.0  0.4 548476 33224 ?        S    Sep29   0:00
> /usr/sbin/samba
> root      3423  0.0  0.5 552608 47292 ?        S    Sep29   0:53
> /usr/sbin/samba
>
>
> Let me restart the process again and together monitor the samba log to see
> if I've missed anything again :)
>
> Will be back :)
>
>
> On Tue, Sep 30, 2014 at 9:35 AM, Richard Sharpe
> <realrichardsharpe at gmail.com> wrote:
>>
>> On Mon, Sep 29, 2014 at 6:23 PM, Chan Min Wai <dcmwai at gmail.com> wrote:
>> > Memory usage after upgrade to 4.1.12 since yesterday.
>> >
>> > free -h
>> >              total       used       free     shared    buffers
>> > cached
>> > Mem:          7.8G       3.0G       4.8G       1.2M       352M
>> > 1.1G
>> > -/+ buffers/cache:       1.6G       6.2G
>> > Swap:         1.9G         0B       1.9G
>> >
>> >
>> > root      3408  0.0  0.5 548476 46596 ?        Ss   Sep29   0:00
>> > /usr/sbin/samba
>> > root      3412  0.0  0.4 548476 33168 ?        S    Sep29   0:00
>> > /usr/sbin/samba
>> > root      3413  0.7  0.4 553048 39160 ?        S    Sep29  13:28
>> > /usr/sbin/samba
>> > root      3414  0.0  0.5 474940 47340 ?        Ss   Sep29   0:09
>> > /usr/sbin/smbd -D --option=server role check:inhibit=yes --foreground
>> > root      3415  0.0  0.4 552628 35856 ?        S    Sep29   0:01
>> > /usr/sbin/samba
>> > root      3416  0.0  0.4 548476 33044 ?        S    Sep29   0:00
>> > /usr/sbin/samba
>> > root      3417  0.0  0.5 548876 41552 ?        S    Sep29   0:32
>> > /usr/sbin/samba
>> > root      3418  0.0  0.4 548456 34880 ?        S    Sep29   0:02
>> > /usr/sbin/samba
>> > root      3419  0.0  0.4 552628 38192 ?        S    Sep29   0:04
>> > /usr/sbin/samba
>> > root      3420  2.9 12.8 1574492 1049440 ?     S    Sep29  55:11
>> > /usr/sbin/samba  <--- eating memory...
>>
>> I don't think this is a tdb issue.
>>
>> Perhaps there is a talloc problem.
>>
>> You should be able to use smbcontrol <PID> pool-usage (or something
>> like that) to get the smbd that is consuming memory to dump its talloc
>> usage.
>>
>> Also, there might be something in the log file for that smbd that
>> shows you why it is consuming lots of memory.
>>
>> --
>> Regards,
>> Richard Sharpe
>> (何以解憂？唯有杜康。--曹操)
>
>



-- 
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)