Bug 1052436 - LDAP server broken after update, reconfiguration fails with str2ad(olcDbCheckpoint): attribute type undefined
Summary: LDAP server broken after update, reconfiguration fails with str2ad(olcDbChec...
Status: RESOLVED WONTFIX
Alias: None
Product: openSUSE Distribution
Classification: openSUSE
Component: Other (show other bugs)
Version: Leap 42.3
Hardware: x86-64 Linux
: P5 - None : Major (vote)
Target Milestone: ---
Assignee: Howard Guo
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on: 964924
Blocks:
  Show dependency treegraph
 
Reported: 2017-08-06 22:29 UTC by Aaron Williams
Modified: 2019-07-11 11:15 UTC (History)
10 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Aaron Williams 2017-08-06 22:29:44 UTC
+++ This bug was initially created as a clone of Bug #964924 +++

I just got hit by this bug when upgrading from 13.2 to Leap 42.3 on my server, rendering it unusable.

Previous information:
=============================================

I've been running an authentication server in my home network for half a year now, without problems. After a zypper dup on 2016-02-02, clients could no longer authenticate their users (both other computers on the net and the server itself).

Below I've quoted slapd-related error messages from the system journal during the update.

Stopped slapd and re-ran the Yast2 Authentication server module, opted for clean re-install (without reading current configuration). Selected starting of LDAP and Kerberos. Default hdb backend. On clicking "Finish", there is an error message 

    56b1f578 <= str2entry: str2ad(olcDbCheckpoint): attribute type undefined
    slapadd: could not parse entry (line=920)

Searched for a schema file containing the database-specific attributes (a web search hinted at a confighdb.ldif file, which appears not to be present on my system.

I'd be happy to run tests or provide further data, and of course I would also welcome a workaround.

*.*

Feb 02 18:47:22 spunk slapd[2408]: slapd shutdown: waiting for 0 operations/tasks to finish
Feb 02 18:47:23 spunk slapd[2408]: DIGEST-MD5 common mech free
Feb 02 18:47:23 spunk slapd[2408]: slapd stopped.
Feb 02 18:47:23 spunk systemd[1]: Stopped OpenLDAP Server Daemon.
Feb 02 18:47:23 spunk audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=slapd comm="systemd" exe="/
Feb 02 18:47:23 spunk audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=slapd comm="systemd" exe="/u
Feb 02 18:47:23 spunk systemd[1]: Starting OpenLDAP Server Daemon...
Feb 02 18:47:23 spunk slapd[7266]: @(#) $OpenLDAP: slapd 2.4.43 $
                                           opensuse-buildservice@opensuse.org
Feb 02 18:47:23 spunk slapd[7266]: UNKNOWN attributeDescription "OLCDBCACHESIZE" inserted.
Feb 02 18:47:23 spunk slapd[7266]: UNKNOWN attributeDescription "OLCDBCHECKPOINT" inserted.
Feb 02 18:47:23 spunk slapd[7266]: UNKNOWN attributeDescription "OLCDBCONFIG" inserted.
Feb 02 18:47:23 spunk slapd[7266]: UNKNOWN attributeDescription "OLCDBIDLCACHESIZE" inserted.
Feb 02 18:47:23 spunk slapd[7266]: UNKNOWN attributeDescription "OLCDBINDEX" inserted.
Feb 02 18:47:23 spunk slapd[7266]: config error processing olcDatabase={1}hdb,cn=config:
Feb 02 18:47:23 spunk slapd[7266]: DIGEST-MD5 common mech free
Feb 02 18:47:23 spunk slapd[7266]: slapd stopped.
Feb 02 18:47:23 spunk slapd[7266]: connections_destroy: nothing to destroy.
Feb 02 18:47:23 spunk systemd[1]: slapd.service: Control process exited, code=exited status=1
Feb 02 18:47:23 spunk systemd[1]: Failed to start OpenLDAP Server Daemon.
Feb 02 18:47:23 spunk audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=slapd comm="systemd" exe="/
Feb 02 18:47:23 spunk systemd[1]: slapd.service: Unit entered failed state.
Feb 02 18:47:23 spunk systemd[1]: slapd.service: Failed with result 'exit-code'.
Feb 02 18:47:23 spunk start[7266]: Starting ldap-server
Feb 02 18:47:23 spunk [RPM][7214]: erase openldap2-2.4.42-18.1.x86_64: success
Feb 02 18:47:23 spunk [RPM][7214]: Transaction ID 56b0eba8 finished: 0
Feb 02 18:47:23 spunk [RPM][7290]: Transaction ID 56b0ebab started
Comment 1 Andreas Stieger 2017-08-07 07:51:56 UTC
We still have this one to process for Leap 42.3 maintenance:
https://build.opensuse.org/request/show/514193
Not sure if any fixes for that are in there.
Comment 2 Howard Guo 2017-08-07 08:49:52 UTC
Hi Michael: looks like the move to separate database drivers from openldap executable continues to cause breakage during upgrades, and none of us could come up with a good way to unbreak this. Do you think we can bring those drivers back into openldap executable?
Comment 3 Tomáš Chvátal 2019-07-11 11:15:42 UTC
This is automated batch bugzilla cleanup.

The openSUSE 42.3 changed to end-of-life (EOL [1]) status. As such
it is no longer maintained, which means that it will not receive any
further security or bug fix updates.
As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
openSUSE (At this moment openSUSE Leap 15.1, 15.0 and Tumbleweed) please
feel free to reopen this bug against that version (!you must update the
"Version" component in the bug fields, do not just reopen please), or
alternatively create a new ticket.

Thank you for reporting this bug and we are sorry it could not be fixed
during the lifetime of the release.

[1] https://en.opensuse.org/Lifetime