openldap-bugs

openldap-bugs@openldap.org

1 participants
20960 discussions

(ITS#8498) slapadd complains about missing attrs
by quanah＠openldap.org 09 Sep '16

09 Sep '16

Full_Name: Quanah Gibson-Mount Version: 2.4.44+ITS8432 OS: Linux 3.13 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (75.111.52.177) When slapadding a database rooted at "" on a replica, it outputs the following warning: zimbra@zre-ldap014:~$ time ./libexec/zmslapadd /home/build/ldap.bak.20160909144406 57d32561 slapadd: warning, missing attrs entryUUID,entryCSN from entry dn="" -######## 42.58% eta 01m39s elapsed 01m13s spd 292.8 k/s Interestingly enough, when slapadded to a master with cn=accesslog in play, it doesn't output anything: zimbra@zre-ldap008:~$ ./libexec/zmslapadd /home/build/ldap.bak.20160909144406 *#################### 100.00% eta none elapsed 02m45s spd 3.1 M/s Closing DB... I'd generally expect the warning to be consistently shown (or not). I don't think it's valid in the case of "".

1 0

Re: (ITS#8490) changes not written to accesslog, causing replicas to loop syncing
by quanah＠zimbra.com 09 Sep '16

09 Sep '16

--On Thursday, September 01, 2016 9:50 AM +0000 quanah(a)zimbra.com wrote: I finally was able to reproduce this in a new lab of servers I set up. The easiest way to reproduce this problem is to have 2 masters, and 6 replicas. 3 replicas pointing to each master. In my case, I have ldap07 through ldap014. 07/08 are the masters. Odd number replicas (9,11,13) point to 07, even number replicas point to 08 (10, 12, 14). What we find based on the logs is two MODRDNs coming in at approximately the same time: Sep 9 15:29:40 zre-ldap007 slapd[13794]: conn=1389 op=3179 MODRDN dn="uid=user.345,ou=people,dc=zre-ldap007,dc=eng,dc=zimbra,dc=com" Sep 9 15:29:40 zre-ldap007 slapd[13794]: conn=1120 op=2919 MODRDN dn="uid=user.250404,ou=people,dc=zre-ldap007,dc=eng,dc=zimbra,dc=com" Sep 9 15:29:40 zre-ldap007 slapd[13794]: slap_queue_csn: queueing 0xa046e80 20160909192940.809794Z#000000#001#000000 Sep 9 15:29:40 zre-ldap007 slapd[13794]: slap_queue_csn: queueing 0xa046a40 20160909192940.809794Z#000000#001#000000 Sep 9 15:29:40 zre-ldap007 slapd[13794]: slap_queue_csn: queueing 0xa07b740 20160909192940.810205Z#000000#001#000000 Sep 9 15:29:40 zre-ldap007 slapd[13794]: slap_graduate_commit_csn: removing 0xa046a40 20160909192940.809794Z#000000#001#000000 Sep 9 15:29:40 zre-ldap007 slapd[13794]: slap_queue_csn: queueing 0xa07bdc0 20160909192940.810205Z#000000#001#000000 Sep 9 15:29:40 zre-ldap007 slapd[13794]: conn=1389 op=3179 RESULT tag=109 err=0 etime=0.001278 text= Sep 9 15:29:40 zre-ldap007 slapd[13794]: slap_graduate_commit_csn: removing 0xa046e80 20160909192940.809794Z#000000#001#000000 Sep 9 15:29:40 zre-ldap007 slapd[13794]: slap_graduate_commit_csn: removing 0xa07bdc0 20160909192940.810205Z#000000#001#000000 Sep 9 15:29:40 zre-ldap007 slapd[13794]: conn=1120 op=2919 RESULT tag=109 err=0 etime=0.001597 text= Sep 9 15:29:40 zre-ldap007 slapd[13794]: slap_graduate_commit_csn: removing 0xa07b740 20160909192940.810205Z#000000#001#000000 But in the accesslog, we only find the one MODRDN logged: dn: reqStart=20160909192940.809465Z,cn=accesslog objectClass: auditModRDN structuralObjectClass: auditModRDN reqStart: 20160909192940.809465Z reqEnd: 20160909192940.810148Z reqType: modrdn reqSession: 1389 reqAuthzID: uid=zimbra,cn=admins,cn=zimbra reqDN: uid=user.345,ou=people,dc=zre-ldap007,dc=eng,dc=zimbra,dc=com reqResult: 0 reqMod: entryCSN:= 20160909192940.809794Z#000000#001#000000 reqMod: modifiersName:= uid=zimbra,cn=admins,cn=zimbra reqMod: modifyTimestamp:= 20160909192940Z reqNewRDN: uid=renamed-user.345 reqDeleteOldRDN: TRUE reqEntryUUID: c63b246a-0a20-1036-82cb-a772509d7f53 entryUUID: 7f740e6c-0b0f-1036-8c00-b1b4f08a59fc creatorsName: cn=config createTimestamp: 20160909192940Z entryCSN: 20160909192940.809794Z#000000#001#000000 modifiersName: cn=config modifyTimestamp: 20160909192940Z Possibly a DN collision in writing the entry to the accesslog DB that causes the second OP to get lost. Likely the same root issue as ITS#8493. --Quanah -- Quanah Gibson-Mount

1 0

Re: (ITS#8497) userPassword attribute in password policy
by quanah＠zimbra.com 09 Sep '16

09 Sep '16

--On Friday, September 09, 2016 3:38 PM +0000 sagar437(a)gmail.com wrote: > Full_Name: Sagar Bhattarai > Version: 2.4.40-9 > OS: CentOS Linux release 7.2.1511 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (71.174.102.218) The ITS system is for reporting bugs, not asking usage questions. Questions should be sent to the openldap-technical(a)openldap.org email list. This ITS will be closed. --Quanah -- Quanah Gibson-Mount

1 0

(ITS#8497) userPassword attribute in password policy
by sagar437＠gmail.com 09 Sep '16

09 Sep '16

Full_Name: Sagar Bhattarai Version: 2.4.40-9 OS: CentOS Linux release 7.2.1511 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (71.174.102.218) I am trying to push the password policy with the following content of ldif file. dn: cn=passwordDefault4,ou=policy,dc=vivox,dc=com objectClass: pwdPolicy objectclass: device objectClass: top cn: passwordDefault4 pwdAttribu%3: userPassword pwdCheckQuality: 0 pwdMinAge: 0 pwdMaxAge: 0 pwdMinLength: 5 pwdInHistory: 5 pwdMaxFailure: 3 pwdFailureCountInterval: 0 pwdLockout: TRUE pwdLockoutDuration: 0 pwdAllowUserChange: TRUE pwdExpireWarning: 0 pwdGraceAuthNLimit: 0 pwdMustChange: TRUE pwdSafeModify: TRUE I keep getting the following error when trying to add the above policy. ldap_add: Invalid syntax (21) additional info: pwdAttribute: value #0 invalid per syntax However id i change the pwdattribute vae frfrom "userPassword" to OID number i am able to add this policy but none of these policies work on my systems.

1 0

Re: (ITS#8495) slaped service unable to restart
by quanah＠zimbra.com 09 Sep '16

09 Sep '16

--On Friday, September 09, 2016 8:34 AM +0000 ritesh.s(a)litmusit.com wrote: > Full_Name: Ritesh Supatkar > Version: Openldap-2.4.40 > OS: Rhel 7.2 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (103.14.160.193) This looks like an issue with systemd and Redhat. I advise contacting Redhat support. --Quanah -- Quanah Gibson-Mount

1 0

Re: (ITS#8496) Error while launching LDAP
by quanah＠zimbra.com 09 Sep '16

09 Sep '16

--On Friday, September 09, 2016 8:56 AM +0000 kshtijdasture(a)gmail.com wrote: > Full_Name: Kshitij Dasture > Version: 2.4.41 > OS: Windos > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (203.99.214.118) > > > I am starting the LAP by the below command.Below is the show stopper for > the execution of Start command. > > > -bash-4.3$ ./slapd -f slapd.conf -d 1 > ldap.log The ITS system is for reporting bugs, not usage questions. If you have questions on how to use OpenLDAP correctly, please use the openldap-technical list. This ITS will be closed. --Quanah -- Quanah Gibson-Mount

1 0

(ITS#8496) Error while launching LDAP
by kshtijdasture＠gmail.com 09 Sep '16

09 Sep '16

Full_Name: Kshitij Dasture Version: 2.4.41 OS: Windos URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (203.99.214.118) I am starting the LAP by the below command.Below is the show stopper for the execution of Start command. -bash-4.3$ ./slapd -f slapd.conf -d 1 > ldap.log . . . 57d25b6b backend_startup_one: starting "dc=gnf,dc=telekom,dc=m%m" 57d25b6b bdb_db_open: database "dc=gnf,dc=telekom,dc=com": database already in use. 57d25b6b backend_startup_one (type=bdb, suffix="dc=gnf,dc=telekom,dc=com"): bi_db_open failed! (-1) 57d25b6b slapd shutdown: initiated 57d25b6b ====> bdb_cache_release_all 57d25b6b slapd destroy: freeing system resources. 57d25b6b slapd stopped. -bash-4.3$

1 0

(ITS#8495) slaped service unable to restart
by ritesh.s＠litmusit.com 09 Sep '16

09 Sep '16

Full_Name: Ritesh Supatkar Version: Openldap-2.4.40 OS: Rhel 7.2 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (103.14.160.193) [bbpsadm@hydbbpsldp01 ~]$ sudo systemctl status slapd ● slapd.service - OpenLDAP Server Daemon Loaded: loaded (/usr/lib/systemd/system/slapd.service; enabled; vendor preset: disabled) Active: active (running) since Thu 20169-9-08 18:18:20 IST; 18h ago Docs: man:slapd man:slapd-config man:slapd-hdb man:slapd-mdb file:///usr/share/doc/openldap-servers/guide.html Process: 44574 ExecStart=/usr/sbin/slapd -u ldap -h ${SLAPD_URLS} $SLAPD_OPTIONS (code=exited, status=0/SUCCESS) Process: 44531 ExecStartPre=/usr/libexec/openldap/check-config.sh (code=exited, status=0/SUCCESS) Main PID: 44575 (slapd) CGroup: /system.slice/slapd.service └6%6#9472;44575 /usr/sbin/slapd -u ldap -h ldapi:/// ldap:/// Sep 09 12:34:45 hydbbpsldp01 slapd[44575]: <= bdb_equality_candidates: (uid) not indexed Sep 09 12:34:45 hydbbpsldp01 slapd[44575]: conn=1020 op=1 SEARCH RESULT tag=101 err=0 nentries=1 text= Sep 09 12:34:45 hydbbpsl0101 slapd[47575]: conn=1020 op=2 SRCH base="dc=npci,dc=co,dc=in" scope=2 deref=0 filter="(&(memberUid=bbpsadm)(objectClass=posixGr...ber=0))))" Sep 09 12:34:45 hydbbpsldp01 slapd[44575]: conn=1020 op=2 SRCH attr=objectClass cn userPassword gidNumber modifyTimestamp modifyTimestamp Sep 09 12:34:45 hydbbpsldp01 slapd[44575]: <= bdb_equality_candidates: (memberUid) not indexed Sep 09 12:34:45 hydbbpsldp01 slapd[44575]: conn=1020 op=2 SEARCH RESULT tag=101 err=0 nentries=0 text= Sep 09 12:34:45 hydbbpsldp01 slapd[44575]: conn=1020 op=3 SRCH base="dc=npci,dc=co,dc=in" scope=2 deref=0 filter="(&(gidNumber=1001)(objectClass=posixGroup...ber=0))))" Sep 09 12:34:45 hydbbpsldp01 slapd[44575]: conn=1020 op=3 SRCH attr=objectClass cn userPassword gidNumber memberuid modifyTimestamp modifyTimestamp Sep 09 12:34:45 hydbbpsldp01 slapd[44575]: <= bdb_equality_candidates: (gidNumber) not indexed Sep 09 12:34:45 hydbbpsldp01 slapd[44575]: conn=1020 op=3 SEARCH RESULT tag=101 err=0 nentries=2 text= Hint: Some lines were ellipsized, use -l to show in full. [bbpsadm@hydbbpsldp01 ~]$ [bbpsadm@hydbbpsldp01 ~]$ sudo systemctl restart slapd Error getting authority: Error initializing authority: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: An SELinux policy prevents thisesender from sending this message to this recipient, 0 matched rules; type="method_call", sender="(null)" (inactive) interface="org.freedesktop.DBus" member="Hello" error name="(unset)" requested_reply="0" destination="org.freedesktop.DBus" (bus) (g-dbus-error-quark, 9) [bbpsadm@hydbbpsldp01 ~]$

1 0

(ITS#8494) doc: Rename 'TLSEphemeralDHParamFile' to 'TLSDHParamFile'
by georg＠riseup.net 08 Sep '16

08 Sep '16

Full_Name: Georg Faerber Version: 2.4 OS: Debian URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (91.64.110.191) http://www.openldap.org/doc/admin24/tls.html mentions directive 'TLSEphemeralDHParamFile' whereas slapd.conf(5) mentions 'TLSDHParamFile'. (See [1] as well). [1] http://www.openldap.org/lists/openldap-technical/201309/msg00094.html

1 0

RE: (ITS#8374) LDAP_OPT_X_TLS_REQUIRE_CERT handling differences between ldaps:// and STARTTLS
by dog＠pavlov.com 07 Sep '16

07 Sep '16

Actually, ignore me this is still connecting when it should fail. Don't close. ;)

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs