Displaying 4 results from an estimated 4 matches for "rjsgw".
2020 Feb 18
6
samba AD DC eats memory
Hello Andrew,
> On Mon, 2020-02-17 at 19:11 +0300, Alex via samba wrote:
>> I'm running Samba AD DC in a VM under Proxmox. And it's eaten all RAM (1.8GB) within 3
>> days of running:
> Exactly which version is this?
Sorry, forgot to mention it. Samba version is 4.11.6. Some more info (if needed):
[root at vm-dc3 ~]# wbinfo -u | wc -l
62
[root at vm-dc3 ~]# wbinfo -g |
2020 Feb 25
0
samba AD DC eats memory
...idually, and put them in distinct
> > files
> > for me?
>
> sorted by swap: https://paste.ee/p/w6TL5
>
> I tried to grab pool-usage for PIDs 1540, 1552 and 1555 and got "No
> replies
> received" for each of them.
>
> sorted by rss: https://paste.ee/p/Rjsgw
>
> pool-usage for the PID 1520 returns the same "no replies"
>
> Let me know if you need anything else.
It looks to me that the worst of the issue in the KDC.
You could run Samba under valgrind:
PYMALLOC=malloc valgrind --trace-children=yes bin/samba -i
You could also t...
2020 Feb 26
0
samba AD DC eats memory
...gt; sorted by swap: https://paste.ee/p/w6TL5
> > >
> > > I tried to grab pool-usage for PIDs 1540, 1552 and 1555 and got
> > > "No
> > > replies
> > > received" for each of them.
> > >
> > > sorted by rss: https://paste.ee/p/Rjsgw
> > >
> > > pool-usage for the PID 1520 returns the same "no replies"
> > >
> > > Let me know if you need anything else.
> > It looks to me that the worst of the issue in the KDC.
> > You could run Samba under valgrind:
> > PYMALLOC=...
2020 Feb 26
2
samba AD DC eats memory
...e/p/w6TL5
> > > >
> > > > I tried to grab pool-usage for PIDs 1540, 1552 and 1555 and got
> > > > "No
> > > > replies
> > > > received" for each of them.
> > > >
> > > > sorted by rss: https://paste.ee/p/Rjsgw
> > > >
> > > > pool-usage for the PID 1520 returns the same "no replies"
> > > >
> > > > Let me know if you need anything else.
> > >
> > > It looks to me that the worst of the issue in the KDC.
> > > You could...