On 2017/05/25 14:05, Allan Streib wrote:
> >Synopsis:    ldapd(8) assertion fails on amd64 Dell PowerEdge R710
> >Category:    system
> >Environment:
>       System      : OpenBSD 6.1
>       Details     : OpenBSD 6.1 (GENERIC.MP) #20: Sat Apr  1 13:45:56 MDT 2017
>                        
> [email protected]:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> 
>       Architecture: OpenBSD.amd64
>       Machine     : amd64
> >Description:
>       Upon adding the first entry to a new directory using ldapadd(1), an
>       assertion fails with the following message...
>       
>       assertion "p->upper >= p->lower" failed: file 
> "/usr/src/usr.sbin/ldapd/btree.c", line 1949, function "btree_add_node"
>       
>       ...and ldapd(8) exits.
> 
> >How-To-Repeat:
>       1. Newly-installed 6.1-release on Dell PowerEdge R710, with
>          openldap-client from packages.
>       
>       2. Create /etc/ldapd.conf, owner root, group wheel, mode 0600
>          containing: 
>       
>          listen on "/var/run/ldapd.sock"
>          rootdn "cn=admin,dc=example,dc=org"
>          rootpw "test1234"
>          schema "/etc/ldap/core.schema"
>          namespace "dc=example,dc=org" {
>                  index objectClass
>          }
>       
>       3. As root, start ldapd(8) in debug mode
>       
>          ldapd -d -v
>       
>       4. As a normal user in another login session, create init.ldif
>          containing:
>       
>          dn: dc=example,dc=org
>          objectClass: top
>          objectClass: domain
>          dc: example
>          description: test
>       
>       5. As normal user, run:
>       
>          cat init.ldif | ldapadd -H ldapi://%2Fvar%2Frun%2Fldapd.sock -D 
> "cn=admin,dc=example,dc=org" -W
>       
>          Enter password test1234 when prompted. Note the results:
>        
>          adding new entry "dc=example,dc=org"
>          ldap_result: Can't contact LDAP server (-1)

I get different results,

adding new entry "dc=example,dc=org"
ldap_add: Invalid syntax (21)

...
May 25 19:50:46.852 [65476] adding entry dc=example,dc=org
May 25 19:50:46.853 [65476] createTimestamp: invalid syntax
May 25 19:50:46.853 [65476] syntax = Generalized Time
May 25 19:50:46.853 [65476] value: [20170525185046Z]
May 25 19:50:46.853 [65476] sending response 9 with result 21
May 25 19:50:46.854 [65476] consumed 7 bytes
...

>          In the root session running ldapd, note the results similar to:
>       
>          May 24 14:08:09.938 [42637] accepted local connection by uid 1001
>          May 24 14:08:09.947 [42637] consumed 48 bytes
>          May 24 14:08:09.948 [42637] got request type 0, id 1
>          May 24 14:08:09.948 [42637] bind dn = cn=admin,dc=example,dc=org
>          May 24 14:08:09.948 [42637] successfully authenticated as 
> cn=admin,dc=example,dc=org
>          May 24 14:08:09.948 [42637] sending response 1 with result 0
>          May 24 14:08:09.957 [42637] consumed 106 bytes
>          May 24 14:08:09.957 [42637] got request type 8, id 2
>          May 24 14:08:09.957 [42637] adding entry dc=example,dc=org
>          assertion "p->upper >= p->lower" failed: file 
> "/usr/src/usr.sbin/ldapd/btree.c", line 1949, function "btree_add_node"
>          May 24 14:08:09.997 [28992] ldapd: removing unix socket 
> /var/run/ldapd.sock
>          May 24 14:08:10.008 [28992] ldapd: exiting

>       
> >Fix:
>       Have not found fix or workaround. Running the same steps on my
>       desktop machine (ASUS w/AMI BIOS) or another available desktop (Dell
>       Optiplex 960 w/Dell "A05" BIOS) does not generate the assertion
>       failure. It happens on two different but identical Dell PowerEdge
>       R710 servers that I have tried. I have tried with all syspatches as
>       of this date and without any patches and the problem is the same.

Are the working machines running the same code? (amd64 MP 6.1-release)?

Reply via email to