Bug 43829 - slapd fails to start during update to 4.2 due to unknown attr univentionPortalEntry
slapd fails to start during update to 4.2 due to unknown attr univentionPorta...
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: LDAP
UCS 4.1
Other Linux
: P5 normal (vote)
: ---
Assigned To: UCS maintainers
UCS maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2017-03-13 14:41 CET by Felix Botner
Modified: 2019-01-03 07:18 CET (History)
3 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 1: Cosmetic issue or missing function but workaround exists
Who will be affected by this bug?: 3: Will affect average number of installed domains
How will those affected feel about the bug?: 2: A Pain – users won’t like this once they notice it
User Pain: 0.034
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2017040621000198
Bug group (optional): Troubleshooting
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Felix Botner univentionstaff 2017-03-13 14:41:48 CET
[FAIL] Starting ldap server(s): slapd ...failed.
[info] 58c6a0bf OVER: Loading Translog Overlay 58c6a0bf OVER: db_init 58c6a0bf OVER: Configuring Translog Overlay 58c6a0bf OVER: Configured Translog Overlay to use file "/var/lib/univention-ldap/listener/listener" 58c6a0bf /etc/ldap/slapd.conf: line 175: unknown attr "@univentionPortalEntry" in to clause 58c6a0bf <access clause> ::= access to <what> [ by <who> [ <access> ] [ <control> ] ]+ <what> ::= * | dn[.<dnstyle>=<DN>] [filter=<filter>] [attrs=<attrspec>] <attrspec> ::= <attrname> [val[/<matchingRule>][.<attrstyle>]=<value>] | <attrlist> <attrlist> ::= <attr> [ , <attrlist> ] <attr> ::= <attrname> | @<objectClass> | !<objectClass> | entry | children <who> ::= [ * | anonymous | users | self | dn[.<dnstyle>]=<DN> ] [ realanonymous | realusers | realself | realdn[.<dnstyle>]=<DN> ] [dnattr=<attrname>] [realdnattr=<attrname>] [group[/<objectclass>[/<attrname>]][.<style>]=<group>] [peername[.<peernamestyle>]=<peer>] [sockname[.<style>]=<name>] [domain[.<domainstyle>]=<domain>] [sockurl[.<style>]=<url>] [dynacl/<name>[/<options>][.<dynstyle>][=<pattern>]] [ssf=<n>] [transport_ssf=<n>] [tls_ssf=<n>] [sasl_ssf=<n>] <style> ::= exact | regex | base(Object) <dnstyle> ::= base(Object) | one(level) | sub(tree) | children | exact | regex <attrstyle> ::= exact | regex | base(Object) | one(level) | sub(tree) | children <peernamestyle> ::= exact | regex | ip | ipv6 | path <domainstyle> ::= exact | regex | base(Object) | sub(tree) <access> ::= [[real]self]{<level>|<priv>} <level> ::= none|disclose|auth|compare|search|read|{write|add|delete}|manage <priv> ::= {=|+|-}{0|d|x|c|s|r|{w|a|z}|m}+ <control> ::= [ stop | continue | break ] dynacl: <name>=ACI <pattern>=<attrname> slapschema: bad configuration file!.

The update works though, maybe this is just cosmetic
Comment 1 Florian Best univentionstaff 2017-03-13 14:53:10 CET
It is the same as Bug #41782
Comment 2 Nico Stöckigt univentionstaff 2017-07-13 10:00:26 CEST
(In reply to Florian Best from comment #1)
> It is the same as Bug #41782

so it's the same but not a duplicate?
Why this only is a cosmetic issue, it prevents slapd from starting?
Comment 3 Florian Best univentionstaff 2017-07-13 10:37:37 CEST
(In reply to Nico Stöckigt from comment #2)
> (In reply to Florian Best from comment #1)
> > It is the same as Bug #41782
> 
> so it's the same but not a duplicate?
> Why this only is a cosmetic issue, it prevents slapd from starting?
Yes, it prevents slapd from starting but only temporary.
The problem is that at this time the attribute is not yet part of the schema but a little bit later the schema is registered and slapd can start again.
So it only produces an error in the logfiles but after the upgrade anything works fine!?!
Comment 4 Christina Scheinig univentionstaff 2017-07-13 10:50:25 CEST
A snippet of the Logfile from a customer. Slapd does not start after the upgrade at all.

root@ucs:~# systemctl status slapd.service -l
? slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory Access Protocol)
   Loaded: loaded (/etc/init.d/slapd)
   Active: failed (Result: exit-code) since Do 2017-04-06 07:40:33 CEST; 29s ago
  Process: 3135 ExecStart=/etc/init.d/slapd start (code=exited, status=1/FAILURE)

Apr 06 07:40:33 ucs slapd[3169]: @(#) $OpenLDAP: slapd  (Mar  8 2017 17:32:20) $
                                          pbuser@ladda:/var/build/temp/tmp.gwUsk6kDX6/pbuilder/openldap-2.4.42+dfsg/debian/build/servers/slapd
Apr 06 07:40:33 ucs slapd[3169]: Loaded metadata from "/usr/share/univention-management-console/saml/idp/ucs-sso.chang.ed.xml"
Apr 06 07:40:33 ucs slapd[3169]: DIGEST-MD5 common mech free
Apr 06 07:40:33 ucs slapd[3135]: Starting ldap server(s): slapd ...failed.
Apr 06 07:40:33 ucs slapschema[3172]: Loaded metadata from "/usr/share/univention-management-console/saml/idp/ucs-sso.chang.ed.xml"
Apr 06 07:40:33 ucs slapd[3135]: 58e5d4d1 OVER: Loading Translog Overlay 58e5d4d1 OVER: db_init 58e5d4d1 OVER: Configuring Translog Overlay 58e5d4d1 OVER: Configured Translog Overlay to use file "/var/lib/univention-ldap/listener/listener" 58e5d4d1 /etc/ldap/slapd.conf: line 188: unknown attr "@univentionPortalEntry" in to clause 58e5d4d1 <access clause> ::= access to <what> [ by <who> [ <access> ] [ <control> ] ]+ <what> ::= bin boot cdrom dev etc floppy home initrd.img initrd.img.install initrd.img.old lib lib32 lib64 lost+found media mnt opt proc root run sbin srv sys tmp usr var vmlinuz vmlinuz.install vmlinuz.old | dn[.<dnstyle>=<DN>] [filter=<filter>] [attrs=<attrspec>] <attrspec> ::= <attrname> [val[/<matchingRule>][.<attrstyle>]=<value>] | <attrlist> <attrlist> ::= <attr> [ , <attrlist> ] <attr> ::= <attrname> | @<objectClass> | !<objectClass> | entry | children <who> ::= [ bin boot cdrom dev etc floppy home initrd.img initrd.img.install initrd.img.old lib lib32 lib64 lost+found media mnt opt proc root run sbin srv sys tmp usr var vmlinuz vmlinuz.install vmlinuz.old | anonymous | users | self | dn[.<dnstyle>]=<DN> ] [ realanonymous | realusers | realself | realdn[.<dnstyle>]=<DN> ] [dnattr=<attrname>] [realdnattr=<attrname>] [group[/<objectclass>[/<attrname>]][.<style>]=<group>] [peername[.<peernamestyle>]=<peer>] [sockname[.<style>]=<name>] [domain[.<domainstyle>]=<domain>] [sockurl[.<style>]=<url>] [dynacl/<name>[/<options>][.<dynstyle>][=<pattern>]] [ssf=<n>] [transport_ssf=<n>] [tls_ssf=<n>] [sasl_ssf=<n>] <style> ::= exact | regex | base(Object) <dnstyle> ::= base(Object) | one(level) | sub(tree) | children | exact | regex <attrstyle> ::= exact | regex | base(Object) | one(level) | sub(tree) | children <peernamestyle> ::= exact | regex | ip | ipv6 | path <domainstyle> ::= exact | regex | base(Object) | sub(tree) <access> ::= [[real]self]{<level>|<priv>} <level> ::= none|disclose|auth|compare|search|read|{write|add|delete}|manage <priv> ::= {=|+|-}{0|d|x|c|s|r|{w|a|z}|m}+ <control> ::= [ stop | continue | break ] dynacl: <name>=ACI <
Apr 06 07:40:33 ucs systemd[1]: slapd.service: control process exited, code=exited status=1
Apr 06 07:40:33 ucs systemd[1]: Failed to start LSB: OpenLDAP standalone server (Lightweight Directory Access Protocol).
Apr 06 07:40:33 ucs systemd[1]: Unit slapd.service entered failed state.
Apr 06 07:40:33 ucs slapd[3135]: pattern>=<attrname> slapschema: bad configuration file!.
Comment 5 Christina Scheinig univentionstaff 2017-07-14 10:07:29 CEST
The customer tried to upgrade to 4.2 again. We have now some more information at the ticket. Please have a look at comment 14 and 15.
Comment 6 Stefan Gohmann univentionstaff 2019-01-03 07:18:49 CET
This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018.

Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.