[389-users] Automatically delete "linked" objects

Hi, I am looking for a way to automatically delete certain objects when I delete a user object. For example: * I have a user uid=user1,ou=users,dc=test,dc=tld * I have a role cn=xyz,ou=roles,dc=test,dc=tld * This role has the following atribute: roleOccupant:

[389-users] Re: Permission of log files

to do. Julian Am 15.04.24 um 09:50 schrieb Julian Kippels: Hi, I am looking for a way to configure the default permission of the log files in /var/log/dirsrv//* All the files there belong to dirsrv:dirsrv with the permission of 0600. I would like to have the default permission to be 0644 so

[389-users] Permission of log files

Hi, I am looking for a way to configure the default permission of the log files in /var/log/dirsrv//* All the files there belong to dirsrv:dirsrv with the permission of 0600. I would like to have the default permission to be 0644 so that my external log-monitoring can access the files.

[389-users] Re: 389-ds freezes with deadlock

repl search with no cookie or old cookie. The search is on a different backend than Thread 62, so there is no conflict between the sync_repl unindexed search and update on thread62. best regards thierry On 9/12/23 13:52, Julian Kippels wrote: Hi, there are two threads that are at 100% CPU utili

[389-users] Re: 389-ds freezes with deadlock

it occurred ? What version are you running ? best regards Thierry On 9/8/23 09:28, Julian Kippels wrote: Hi, it happened again and now I ran the gdb-command like Mark suggested. The Stacktrace is attached. Again I got this error message: [07/Sep/2023:15:22:43.410333038 +0200] - ERR - ldbm_back_seq

[389-users] 389-ds freezes with deadlock

error code After this the server keeps running, systemctl status says everything is fine, but new incoming connections are failing with timeouts. Any advice would be welcome. Thanks in advance Julian Kippels -- - | | Julian Kippels

[389-users] Use dsconf to set nsslapd-lookthroughlimit

Hi, I am looking for a way to set nsslapd-lookthroughlimit from cn=config,cn=ldbm database,cn=plugins,cn=config using dsconf. So far I have only found the way to stop the server and edit dse.ldif or maybe using ldapmodify. Is there a way to do this using dsconf? Thanks Julian

[389-users] Re: Wrong password hash algorithm returned

e the user password. Is PBKDF2_SHA256 the default password policy ? thierry On 11/24/22 11:48, Julian Kippels wrote: What exactly are the requirements for the hash upgrade to trigger? I have set up a test server, nsslapd-enable-upgrade-hash is set to "on" but I cannot get the hashes

[389-users] Re: Wrong password hash algorithm returned

e the SSHA-Hash. Ihen I bind as testuser and perform a search. Then I bind as directory manager again and search for testuser again. The hash still remains as SSHA. Julian Am 22.11.22 um 15:30 schrieb Thierry Bordaz: On 11/22/22 10:28, Julian Kippels wrote: Hi Thierry, that's a nasty catch…

[389-users] Re: Wrong password hash algorithm returned

n 1.4.4 default hash is PBKDF2, this ticket upgrade hash of user entries during the user bind (enabled with nsslapd-enable-upgrade-hash). best regards thierry On 11/22/22 09:25, Julian Kippels wrote: Hi, We have a radius server that reads the userPassword-attribute from ldap t

[389-users] Wrong password hash algorithm returned

Hi, We have a radius server that reads the userPassword-attribute from ldap to authenticate users. There is a strange phenomenon where sometimes the answer from the ldap-server gives the wrong password hash algorithm. Our global password policy storage scheme is set to SSHA. When I perform a

[389-users] Re: Upgrading from 1.2.2 to 1.4.4

Hi, Am Tue, 8 Nov 2022 16:39:20 -0500 schrieb Mark Reynolds : > How did you generate these ldifs?  Did you use db2ldif, or > ldapsearch? If you used ldapsearch, then stop.  Please use > db2ldif/db2ldif.pl I created the ldifs using the Java 389-console, loggin in as directory manager and using

[389-users] Upgrading from 1.2.2 to 1.4.4

Hi, I am currently in the process of moving our LDAP-Servers from old CentOS 7 Servers to new Debian 11 Servers. In the process I am exporting all databases from the old server to ldif files and importing those files on the new server. When I import such a file I get a lot (basically for every

[389-users] Re: SizeLimit Exceeded although Limit should be much higher

Hi, Am Thu, 13 Feb 2020 08:05:04 -0500 schrieb Mark Reynolds : > On 2/13/20 5:37 AM, Julian Kippels wrote: > > Hi, > > > > I am having a small problem with a slightly larger lookup. The > > SizeLimit and LookthroughLimit are both set to 30, but when I > >

[389-users] SizeLimit Exceeded although Limit should be much higher

Hi, I am having a small problem with a slightly larger lookup. The SizeLimit and LookthroughLimit are both set to 30, but when I do a larger search, I still get: > # search result > search: 2 > result: 4 Size limit exceeded > > # numResponses: 50001 > # numEntries: 5 Where else could I

[389-users] Re: When 389ds will be available on CentOS 8

e 389-ds-stream. -- --------- | | Julian Kippels | | M.Sc. Informatik | | | | Zentrum für Informations- und Medientechnologie | | Heinrich-Heine-Universität Düsseldorf | | Universitätsstr. 1 | | Raum 25.41.O1.32 | | 40225 Düsseldorf / Germany | | | | Tel: +49-211-81-14920 | | mail:

[389-users] Re: Cannot login to admin server after last update

Am Thu, 15 Mar 2018 16:25:41 -0400 schrieb Mark Reynolds <mreyno...@redhat.com>: > On 03/15/2018 04:11 PM, Julian Kippels wrote: > > Am Thu, 15 Mar 2018 12:00:06 -0400 > > schrieb Mark Reynolds <mreyno...@redhat.com>: > > > >> On 03/15/2018

[389-users] Cannot login to admin server after last update

Hi, since the last update (using RHEL 7, updated from 389-ds-1.3.6.1-21 to 389-ds-1.3.6.1-28) I cannot login as user admin in the administration console anymore. Looking at the logs I see this error message popping up every time I try to log in since then: [Thu Mar 15 13:09:35.046721 2018]

[389-users] Re: Configuring single-master replication from the cli

Am Fri, 09 Mar 2018 17:23:39 +0100 schrieb Ludwig Krispenz : > did you look into chapter 15.2: Configuring Replication from the > Command Line ? > Somehow I feel incredibly stupid right now… ___ 389-users mailing list --

[389-users] Configuring single-master replication from the cli

Hi Is it possible to configure single master replication from the cli? In the documentation it is only described using the admin-server interface:

[389-users] Re: Possible bug? - Silent install behaves differently from interactive

/etc/dirsrv/admin-serv/adm.conf before the silent install > > it works. However we just went through a host domain name change > > (long story) and I’m having I think unrelated problems. I hope to > > resolve that shortly and then I might have a more definitive answer. > > &g

[389-users] Re: Possible bug? - Silent install behaves differently from interactive

velop/templates/adm.conf.j2 > > Here’s where they’re used if you are familiar with ansible: > https://github.com/morganllj/ansible-playbooks/blob/develop/install_389.yml > > -morgan > > > > On Sep 15, 2017, at 11:49 AM, Julian Kippels <kipp...@hhu.de> wrote: >

[389-users] Possible bug? - Silent install behaves differently from interactive

Hi, I was playing around with silent installs and found out that the final configuration differs from interactive installations. Here is what I did: I installed two servers on different machines ds-1.localdomain and ds-2.localdomain. ds-1 is used as a master and ds-2 is supposed to use it as its

[389-users] Generating Performance Metrics

Hi, does anyone have an idea what would be the best way to retroactivaley generate performance metrics using the logfiles? I would like to be able to check for example if in a certain time range there were binds or searches that took longer than usual. Thanks Julian

[389-users] Re: 389ds gets killed for memory usage

d you should see a significant improvement in > memory size and growth. > > Regards, > Mark > > > On 09/26/2016 04:02 AM, Julian Kippels wrote: > > Hi, > > > > I have a setup with 3 Servers running on rhel7, 1 master and 2 slaves, > > as described in the do

[389-users] 389ds gets killed for memory usage

Hi, I have a setup with 3 Servers running on rhel7, 1 master and 2 slaves, as described in the documentation chapter 11.2.1. Once or twice a week the master gets killed by the OS because the system is out of memory. I could just throw more ram at it, but the system already has 16GB of ram and i