[389-users] Re: Using dsctl and .dscrc: How to properly connect to a remote instance?

2023-04-18 Thread Johannes Kastl
Hi William, thanks for the help. On 19.04.23 at 01:52 William Brown wrote: dsctl requires root/dirsrv because it assumes you are on the same host as the dirsrv instance. There are three commands: Sorry, but then the documenation is... having need for improvement. I have misunderstood the

[389-users] Re: 389ds container images and tags

2023-04-18 Thread Johannes Kastl
Hi William, On 19.04.23 at 01:19 William Brown wrote: The docker.com images are maintained by myself at SUSE. Because of how we build them from https://build.opensuse.org/ and via https://registry.opensuse.org/ we can't actually "patch" 2.2 and 2.1, so we really only have latest. Hindsight is

[389-users] A more profound replication monitoring of 389-ds instance

2023-04-18 Thread dweller dweller
Hello everyone, I have a request for advice on how to approach monitoring of replication in an environment with approximately 30 FreeIPA servers, all in a master-master replication agreement, using 389-ds (389-ds-base-1.4.3.28-6). I am currently looking for ways to reduce the number of

[389-users] Re: Using dsctl and .dscrc: How to properly connect to a remote instance?

2023-04-18 Thread Simon Pichugin
Hi folks, Just to add a bit more details about dsconf-dsidm and .dsrc interactions: - If a user tries to use URL in dsconf-dsidm call, then we consider it a remote connection, and we check /etc/openldap/ldap.conf and system-wide settings regarding TLS, etc.; - If a user provides an instance name

[389-users] Re: Using dsctl and .dscrc: How to properly connect to a remote instance?

2023-04-18 Thread William Brown
> On 18 Apr 2023, at 16:37, Johannes Kastl wrote: > > Hi all, > > sorry if this is a dumb one, but I am not getting dsctl working with a remote > instance running in Kubernetes. In fact, I am not getting it to read the > .dscrc file at all, it seems. > > In my user's home directory I have

[389-users] Re: 389ds container images and tags

2023-04-18 Thread William Brown
> On 18 Apr 2023, at 16:15, Johannes Kastl wrote: > > Hi all, > > I am in the process of rewriting my helm chart for 389ds (stay tuned, I'll > send another mail once it is ready), and noticed the lack of recent tags for > the container images: > > https://hub.docker.com/r/389ds/dirsrv only

[389-users] Re: 389 DS memory growth

2023-04-18 Thread Nazarenko, Alexander
This does not contradict to what we see, as noticeable growth starts around the first couple of 100 000 results, and worsens with more. Thanks, - Alex From: Thierry Bordaz Date: Tuesday, April 18, 2023 at 12:37 PM To: "Nazarenko, Alexander" , "General discussion list for the 389 Directory

[389-users] Re: 389 DS memory growth

2023-04-18 Thread Thierry Bordaz
Thanks for the update. I failed to reproduced any significant growth with groups(100)/members(1000) provisioning. The same with searches on person returning 1000 person entries (bound as DM). We will wait for your profiling info. regards Theirry On 4/18/23 18:12, Nazarenko, Alexander

[389-users] Re: 389 DS memory growth

2023-04-18 Thread Nazarenko, Alexander
This is our experience too with 1.3.11* From: Casey Feskens Reply-To: "General discussion list for the 389 Directory server project." <389-users@lists.fedoraproject.org> Date: Tuesday, April 18, 2023 at 12:06 PM To: "General discussion list for the 389 Directory server project."

[389-users] Re: 389 DS memory growth

2023-04-18 Thread Nazarenko, Alexander
This is understood, thank you. It is not a big concern for us, as our servers are at least 16Gb. We are not using pbkdf2 either. This is the heap growth above 20Gb (and up) that is the concern, due to queries like (objectclass=person) hiting the server. At some point in the near future we plan

[389-users] Re: 389 DS memory growth

2023-04-18 Thread Casey Feskens
Yes, I haven't gotten to debugging yet, but we are not using PBKDF2-SHA512 and aren't routinely using memberof in our own queries as we aren't currently maintaining much in the way of group memberships in this instance. I do believe that memory growth has happened in line with batch jobs doing

[389-users] Re: 389 DS memory growth

2023-04-18 Thread Thierry Bordaz
Hi, Note that the initial memory footprint of an instance 1.3.11 is larger that an 1.3.10 one. On RHEL 7.9 2Gb VM, an instance 1.3.11 is 1Gb while 1.3.10 is 0.5Gb. Instances have the same DS tuning. The difference comes from extra chunks of anonymous memory (heap) that are possibly related

[389-users] Helm chart for 389ds

2023-04-18 Thread Johannes Kastl
Hi all, I finally had some time to rework my helm chart for 389ds. It seems to be in a working state, so if anyone is interested I would be glad to have some testers. Please be aware that this is the first version, use at your own risk and proceed with caution. Here be dragons... That

[389-users] Re: 389ds container images and tags

2023-04-18 Thread Viktor Ashirov
On Tue, Apr 18, 2023 at 9:13 AM Johannes Kastl wrote: > Hi Viktor, > > On 18.04.23 at 09:02 Viktor Ashirov wrote: > > > On Tue, Apr 18, 2023 at 8:15 AM Johannes Kastl > wrote: > > >> https://hub.docker.com/r/389ds/dirsrv only has 2.1, 2.2 and latest. 2.2 > >> and > >> latest are 8 months old. >

[389-users] Re: 389ds container images and tags

2023-04-18 Thread Johannes Kastl
Hi Viktor, On 18.04.23 at 09:02 Viktor Ashirov wrote: On Tue, Apr 18, 2023 at 8:15 AM Johannes Kastl wrote: https://hub.docker.com/r/389ds/dirsrv only has 2.1, 2.2 and latest. 2.2 and latest are 8 months old. https://quay.io/repository/389ds/dirsrv?tab=tags only has latest and c9s without

[389-users] Re: 389ds container images and tags

2023-04-18 Thread Viktor Ashirov
Hi Johannes, On Tue, Apr 18, 2023 at 8:15 AM Johannes Kastl wrote: > Hi all, > > I am in the process of rewriting my helm chart for 389ds (stay tuned, I'll > send > another mail once it is ready), and noticed the lack of recent tags for > the > container images: > Oh, nice! Looking forward to

[389-users] Using dsctl and .dscrc: How to properly connect to a remote instance?

2023-04-18 Thread Johannes Kastl
Hi all, sorry if this is a dumb one, but I am not getting dsctl working with a remote instance running in Kubernetes. In fact, I am not getting it to read the .dscrc file at all, it seems. In my user's home directory I have this ~/.dsrc (copied and adapted from the Getting started guide):

[389-users] 389ds container images and tags

2023-04-18 Thread Johannes Kastl
Hi all, I am in the process of rewriting my helm chart for 389ds (stay tuned, I'll send another mail once it is ready), and noticed the lack of recent tags for the container images: https://hub.docker.com/r/389ds/dirsrv only has 2.1, 2.2 and latest. 2.2 and latest are 8 months old.