[Samba] Samba 4.1.5 memory consumption - again

[Łukasz Tomaszewski]

Dear Chan,
We need to dump the output the result in accordance with the instructions.
Maybe someone from the Samba team resumes then you can send the result.


> Given the issues with the memory dumps being repeated in overwealming
> detail, here is a new instruction:
>
> Run samba as:
>
> gdb --args samba -M single --leak-report
>
> Then:
>
> run
>
> When it becomes large, run
>
> p talloc_report_full(0, stderr)
>
> and mail me *only* the output of that command, not the earlier or later output.
>
> The issue with the previous logs is that the same allocation (present in
> multiple forked children) was being logged multiple times, as each child
> exited.  This caused the massive log buildup, without giving me much
> more information.
>
> You may replace stderr with a file on disk with something like:
>
> p talloc_report_full(0, fopen("/tmp/leak.txt", "w")

Luk.



2014-03-18 14:35 GMT+01:00 Chan Min Wai <dcmwai at gmail.com>:

> Dear Luk,
>
> I do found the same issue.
> I've a AD member with 8G ram.
>
> And that system is always with filled all the shared memory.
>
> I also have doubt on this.
>
> If would be nice if someone can enlighten on this.
>
> Thank You.
>
>
>
>  On Tue, Mar 18, 2014 at 7:24 PM, Łukasz Tomaszewski <
> lukasz.tomaszewski at gmail.com> wrote:
>
>>  Hi all,
>> At the pre-big thanks to the SAMBA team for many years the great work.
>>
>> Sorry for my english.
>>
>> A week ago, have implemented productively Samba 4.1.5 on CentOS 6.5. I
>> installed samba by default dns server built-in (internal) with the
>> rfc2307.
>> Everything works great, but after a while I noticed that the memory on my
>> server is largely occupied.
>>
>> At this time there are about 10 users domain - that samba should be bored,
>> but it is not.
>> Installed clean system. No other processes devouring memory.
>> Is 12GB of RAM is not enough for samba?
>>
>> Very similar topic
>> https://lists.samba.org/archive/samba-technical/2012-August/085924.html
>>
>>
>> below the result of the command top and free -m.
>>
>>                    total       used       free     shared    buffers
>> cached
>> Mem:         12043       9261       2782          0        160       8191
>> -/+ buffers/cache:        909      11133
>> Swap:        25023         39      24984
>>
>> top - 11:10:41 up 14:17,  1 user,  load average: 0.10, 0.16, 0.18
>> Tasks: 196 total,   1 running, 195 sleeping,   0 stopped,   0 zombie
>> Cpu0  :  4.7%us,  2.3%sy,  0.0%ni, 92.7%id,  0.0%wa,  0.0%hi,  0.3%si,
>>  0.0%st
>> Cpu1  :  0.3%us,  1.3%sy,  0.0%ni, 98.3%id,  0.0%wa,  0.0%hi,  0.0%si,
>>  0.0%st
>> Cpu2  :  0.0%us,  0.0%sy,  0.0%ni,100.0%id,  0.0%wa,  0.0%hi,  0.0%si,
>>  0.0%st
>> Cpu3  :  0.0%us,  0.0%sy,  0.0%ni,100.0%id,  0.0%wa,  0.0%hi,  0.0%si,
>>  0.0%st
>> Mem:  12332632k total,  9498568k used,  2834064k free,   175476k buffers
>> Swap: 25624568k total,    40148k used, 25584420k free,  8393700k cached
>>
>>   PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
>>  1565 root      20   0  517m 115m  54m S  8.6  1.0   8:11.76 samba
>>  1553 root      20   0  472m  16m 6968 S  0.3  0.1   0:19.81 samba
>>
>> Does anybody know what can be done? Is this normal? How can I check what
>> these huge processes do?
>>
>> Thanks everyone.
>>
>> --
>> Luk Tomaszew
>> --
>> To unsubscribe from this list go to the following URL and read the
>> instructions:  https://lists.samba.org/mailman/options/samba
>>
>
>