Displaying 20 results from an estimated 30000 matches similar to: "High RAM consumption"
2024 Aug 28
1
High RAM consumption
On 22/08/24 19:26, Dinar Yulm via samba wrote:
> Hello,
>
> LDAP Samba processes consume a lot of memory. Each LDAP process loads the
> entire ldb database into memory and does not release it over time. For
> example, for a 4GB ldb database and 4 LDAP processes, Samba will use up
> more than 16 GB of RAM. If only 16GB of RAM is installed on the server,
> then Samba will
2024 Aug 22
1
High RAM consumption
On Thu, 22 Aug 2024 12:26:50 +0500
Dinar Yulm via samba <samba at lists.samba.org> wrote:
> Hello,
>
> LDAP Samba processes consume a lot of memory. Each LDAP process loads
> the entire ldb database into memory and does not release it over
> time. For example, for a 4GB ldb database and 4 LDAP processes, Samba
> will use up more than 16 GB of RAM. If only 16GB of RAM is
2024 Aug 22
1
High RAM consumption
> What do you mean by 'LDAP Samba processes' ?
LDAP server pre-forked workers.
> What are the actual commands that you are running ?
Some graphical utilities of Windows Server, for example: Active Directory
Users and computers, ADSI, EDIT and others (There are no problems
connecting these utilities to Windows servers with a similar database).
> What OS is this ?
Debian 9
2024 Aug 22
1
High RAM consumption
On Thu, 22 Aug 2024 13:49:24 +0500
Dinar Yulm via samba <samba at lists.samba.org> wrote:
> > What do you mean by 'LDAP Samba processes' ?
>
> LDAP server pre-forked workers.
>
> > What are the actual commands that you are running ?
>
> Some graphical utilities of Windows Server, for example: Active
> Directory Users and computers, ADSI, EDIT and
2024 Aug 22
1
High RAM consumption
We build samba from source code. This server has a build of one of the
latest versions installed.
Some servers use Ubuntu 22.04, there is a similar problem.
The domain uses Samba builds of the same version on all controllers.
??, 22 ???. 2024 ?., 14:31 Rowland Penny via samba <samba at lists.samba.org>:
> On Thu, 22 Aug 2024 13:49:24 +0500
> Dinar Yulm via samba <samba at
2024 Aug 22
1
High RAM consumption
On Thu, 22 Aug 2024 15:59:38 +0500
Dinar Yulm via samba <samba at lists.samba.org> wrote:
> We build samba from source code. This server has a build of one of the
> latest versions installed.
>
> Some servers use Ubuntu 22.04, there is a similar problem.
>
> The domain uses Samba builds of the same version on all controllers.
>
If you are building Samba on Stretch,
2019 Jan 28
5
Samba 4.9.4 - high RAM usage - OOM killer
Hi,
We upgraded a legacy (NT4) domain from 3.6 series to 4.8 and then 4.9.4
samba version (using sernet subscription packages / debian stable)
The setup is composed of 4 DCs with each 2 CPU/16GB RAM.
We currently have ~700 user accounts / ~600 computers / ~150 groups
Our mail setup, SSO, ... query the 4 DCs constantly.
Every 5 to 10 days the RAM consumption and CPU usage (due to kswapd)
2015 Jun 01
1
32 bits limit?
Thank you all for these detailed answers. This size happened on DC where
the import were done. Database with Samba 4 was always significantly bigger
on this host than on the replicated ones. According to that I'll try the
dump trick which would also teach me some things : )
I'll came back after tests...
For LMDB the start seems to be there:
https://jhrozek.fedorapeople.org/sambaxp
2015 Jun 01
5
32 bits limit?
Hi all,
Still playing with a big database (120k users, 150k computers) I tried to
split my users into a lot of OUs. This increased the database size and I
was not able to finish to add users into the DB because database file has
reached 4GB size which seems to be the limit.
First: am I right to say file
/var/lib/samba/private/sam.ldb.d/DC=example,DC=com.ldb has a maximum size
of 4GB?
Secondly:
2018 Jun 28
5
DRS and DNS sync are not working after update from 4.8.2 to 4.8.3
After update I have got this:
samba-tool drs kcc -Uadm2 -d 9
INFO: Current debug levels:
all: 9
tdb: 9
printdrivers: 9
lanman: 9
smb: 9
rpc_parse: 9
rpc_srv: 9
rpc_cli: 9
passdb: 9
sam: 9
auth: 9
winbind: 9
vfs: 9
idmap: 9
quota: 9
acls: 9
locking: 9
msdfs: 9
dmapi: 9
registry: 9
scavenger: 9
dns: 9
ldb: 9
tevent: 9
auth_audit: 9
2019 Apr 08
6
Debian Stretch, Samba 4.10.2, 4.9.6 and 4.8.11 Available (amd64/i386)
Hai guys,
I've updated the Debian Stretch package for Samba 4.10.2, 4.9.6 and 4.8.11.
Repo info : https://apt.van-belle.nl
Build logs: http://downloads.van-belle.nl/samba4/Buildlogs/stretch/
Quick repo setup:
Optional: apt-get install apt-transport-https
Import my public key:
wget -O - http://apt.van-belle.nl/louis-van-belle.gpg-key.asc | apt-key add -
# Example repo stretch samba
2018 Sep 13
2
lmdb requirement for AD DC
>> Did you specify --without-ldb-ldmb?
Nope. I didn't specify "–enable-selftest" either. The default for this option being "no", why does "configure" stop after complaining that "–enable-selftest" requires lmdb? Maybe I'm just being stupid... It happens.
2019 Jan 28
0
Samba 4.9.4 - high RAM usage - OOM killer
Hi Laurent,
>
> We upgraded a legacy (NT4) domain from 3.6 series to 4.8 and then 4.9.4
> samba version (using sernet subscription packages / debian stable)
>
> The setup is composed of 4 DCs with each 2 CPU/16GB RAM.
>
> We currently have ~700 user accounts / ~600 computers / ~150 groups
>
> Our mail setup, SSO, ... query the 4 DCs constantly.
>
>
> Every 5 to
2024 Jun 25
2
Error when raising Samba 4.19 Functional Level
Hi, I raised the functional level of my Samba 4.19 server with the commands
below, the Schema update took a long time but ended successfully, however
when raising the functional level with the second command the error below
occurred and I was unable to complete the complete process. Can anyone tell
me what could have happened or if they have experienced this?
1 - samba-tool domain schemaupgrade
2019 Jan 28
0
Samba 4.9.4 - high RAM usage - OOM killer
Hai,
How is the swappiness set?
cat /proc/sys/vm/swappiness
Its probely set to 60, i suggest, lower it to 10 or 20.
That wil help keeping the samba processes out of swap.
I've see more programs gettting OOM Killed due too out of swap.
echo 10 > /proc/sys/vm/swappiness
Stop and start samba
Greetz,
Louis
> -----Oorspronkelijk bericht-----
> Van: samba
2018 Sep 13
3
lmdb requirement for AD DC
On Thu, 2018-09-13 at 14:41 +0100, miguel medalha via samba wrote:
> Hello
>
> In one of my DCs, when I run ./configure for Samba 4.9.0, it fails
> with the following message:
>
> Checking for lmdb >= 0.9.16 via header check : not
> found
> Samba AD DC and --enable-selftest requires lmdb 0.9.16 or later
>
> My ./configure command line does not contain the
2018 Sep 13
2
lmdb requirement for AD DC
>> As per the release notes, it should work unless you say "--without-ldb-
>> lmdb". The message just got mucked up.
The "configure" stage actually failed. How can it be a message problem only?
2019 May 20
4
Upgrade from 4.9.8 to 4.10.3 on Centos using Sernet Packages
In addition to Rowland comment.
if you still able to test it. Remove 1 setting at a time, restart and test it.
Start with these, in this order.
logging = syslog only
prefork children = 8
I think if the logging line is removed your problem is solved.
man smb.conf /logging should explain more.
Because I cant/find the setting : logging = syslog only
Greetz,
Louis
2019 May 20
2
Upgrade from 4.9.8 to 4.10.3 on Centos using Sernet Packages
Hello Cristian,
Well, nothing to say about your steps, these looks good.
And lmdb could be disable in the sernet packages, cant say, i dont know.
And only one DC has these problems or all? If only one DC crashed.
Which DC crashes. Last added? Oldest?
Greetz,
Louis
> -----Oorspronkelijk bericht-----
> Van: samba [mailto:samba-bounces at lists.samba.org] Namens
> Christian
2023 Jul 27
1
High memory consumption for small AXFR
Hello!
I use NSD 4.7.0 self compiled:
Configure line: --build=x86_64-linux-gnu --prefix=/usr --includedir=${prefix}/include --mandir=${prefix}/share/man --infodir=${prefix}/share/info --sysconfdir=/etc --localstatedir=/var --disable-option-checking --disable-silent-rules --libdir=${prefix}/lib/x86_64-linux-gnu --runstatedir=/run --disable-maintainer-mode --disable-dependency-tracking