Bug 49596
| Summary: | ldap_extension: validation failed for univention-app.schema | ||
|---|---|---|---|
| Product: | UCS | Reporter: | Felix Botner <botner> |
| Component: | LDAP | Assignee: | Felix Botner <botner> |
| Status: | CLOSED FIXED | QA Contact: | Arvid Requate <requate> |
| Severity: | normal | ||
| Priority: | P5 | CC: | best, damrose, hahn, requate |
| Version: | UCS 4.4 | ||
| Target Milestone: | UCS 4.4-0-errata | ||
| Hardware: | Other | ||
| OS: | Linux | ||
| What kind of report is it?: | Development Internal | What type of bug is this?: | --- |
| Who will be affected by this bug?: | --- | How will those affected feel about the bug?: | --- |
| User Pain: | Enterprise Customer affected?: | ||
| School Customer affected?: | ISV affected?: | ||
| Waiting Support: | Flags outvoted (downgraded) after PO Review: | ||
| Ticket number: | Bug group (optional): | Error handling, Troubleshooting | |
| Max CVSS v3 score: | |||
| Bug Depends on: | 49500 | ||
| Bug Blocks: | |||
|
Description
Felix Botner
That did not help, seen again in the jenkins tests updating 'cn=apps,cn=univention,dc=AutoTest091,dc=local' command a 05.06.19 01:01:47.297 LISTENER ( PROCESS ) : updating 'cn=univention-app,cn=ldapschema,cn=univention,dc=AutoTest091,dc=local' command a 05.06.19 01:01:49.771 LISTENER ( ERROR ) : ldap_extension: validation failed: . 05.06.19 01:01:49.771 LISTENER ( ERROR ) : ldap_extension: Removing new file /var/lib/univention-ldap/local-schema/univention-app.schema. 05.06.19 01:01:50.352 LISTENER ( PROCESS ) : updating 'cn=66univention-appcenter_app,cn=ldapacl,cn=univention,dc=AutoTest091,dc=local' command a 05.06.19 01:01:50.353 LISTENER ( PROCESS ) : ldap_extension: cn=66univention-appcenter_app,cn=ldapacl,cn=univention,dc=AutoTest091,dc=local active? ['FALSE'] 05.06.19 01:01:51.120 LISTENER ( ERROR ) : ldap_extension: slapd.conf validation failed: 5cf6f85f /etc/ldap/slapd.conf: line 249: unknown attr "@univentionApp" in to clause 5cf6f85f <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>]] No error message, next idea is to enable debug for the slapschema tool in univention-lib/python/ldap_extension.py. Or has anybody a better idea? We briefly discussed it. We could add -v (verbose) and/or -d <level> to increase the debuglevel. Some interesting points: The slapschema manpage states that errors are already logged to stdout, the previous fix to include stderr will not help add anything useful. In addition, the manpage states "LIMITATIONS For some backend types, your slapd(8) should not be running (at least, not in read-write mode) when you do this to ensure consistency of the database. It is always safe to run slapschema with the slapd-bdb(5), slapd-hdb(5), and slapd-null(5) backends." Can we log the temporary (broken) /etc/ldap/slapd.conf to see line what 249 is? Ist this this the exact error message?
> 5cddc2bc /var/lib/univention-ldap/local-schema/univention-app.schema: line 18: unknown directive <ttributetype> outside backend info and database definitions.
slapschema: bad configuration file!
That's what I get when I edit /var/lib/univention-ldap/local-schema/univention-app.schema and change the first occurance of "attributetype" to "ttributetype".
(In reply to Arvid Requate from comment #3) > Can we log the temporary (broken) /etc/ldap/slapd.conf to see line what 249 > is? The problem is not in line 249. This is the error from the failed ACL registration (because the schema registration failed). The problem is app,cn=ldapschema,cn=univention,dc=AutoTest091,dc=local' command a 05.06.19 01:01:49.771 LISTENER ( ERROR ) : ldap_extension: validation failed: . 05.06.19 01:01:49.771 LISTENER ( ERROR ) : ldap_extension: Removing new file /var/lib/univention-ldap/local-schema/univention-app.schema. and we need more information at this point. But logging the slapd.conf in this case is maybe a good idea anyway (In reply to Arvid Requate from comment #4) > Ist this this the exact error message? > > > 5cddc2bc /var/lib/univention-ldap/local-schema/univention-app.schema: line 18: unknown directive <ttributetype> outside backend info and database definitions. > slapschema: bad configuration file! > > That's what I get when I edit > /var/lib/univention-ldap/local-schema/univention-app.schema and change the > first occurance of "attributetype" to "ttributetype". We have no error message from the fails slapschema. (In reply to Felix Botner from comment #1) > That did not help, seen again in the jenkins tests > 5cf6f85f /etc/ldap/slapd.conf: line 249: unknown attr "@univentionApp" in to > clause > No error message, next idea is to enable debug for the slapschema tool in > univention-lib/python/ldap_extension.py. > > Or has anybody a better idea? Hm, isn't the error message that the attribute univentionApp is not known? (because the schema is not yet registered?) (In reply to Florian Best from comment #7) > (In reply to Felix Botner from comment #1) > > That did not help, seen again in the jenkins tests > > > 5cf6f85f /etc/ldap/slapd.conf: line 249: unknown attr "@univentionApp" in to > > clause > > > No error message, next idea is to enable debug for the slapschema tool in > > univention-lib/python/ldap_extension.py. > > > > Or has anybody a better idea? > > Hm, isn't the error message that the attribute univentionApp is not known? > (because the schema is not yet registered?) No, 1) register schema ldap_extension: validation failed: . 05.06.19 01:01:49.771 LISTENER ( ERROR ) : ldap_extension: Removing new file /var/lib/univention-ldap/local-schema/univention-app.schema. 2) this fails, no univention-app schema 3) register ACL this fails, with a proper error message because the schema is missing, but this is a consequence of first error 7e7a28a8337330242279f0d15bb1c65231574b91 - univention-lib (In reply to Felix Botner from comment #9) > 7e7a28a8337330242279f0d15bb1c65231574b91 - univention-lib There seems to be one case where "slapschema" exits with != 0 and no output: servers/slapd/slapschema.c 161 »···if ( slap_tool_destroy() ) 162 »···»···rc = EXIT_FAILURE; servers/slapd/slapcommon.c 939 »···»···»···if ( slap_shutdown( be )) 940 »···»···»···»···rc = EXIT_FAILURE; servers/slapd/init.c 235 »···return backend_shutdown( be );· servers/slapd/backend.c 363 »···»···»···rc = be->bd_info->bi_db_close( be, NULL ); 364 »···»···»···if ( rc ) return rc; ... 368 »···»···»···rc = be->bd_info->bi_close( be->bd_info ); 369 »···»···»···if ( rc ) return rc; The other case always returns 0: servers/slapd/slapcommon.c 942 »···»···if ( slap_destroy()) 943 »···»···»···rc = EXIT_FAILURE; servers/slapd/init.c 255 »···rc = backend_destroy(); servers/slapd/backend.c 529 »···return 0; If "slapschema" terminates by a signal, it would be logged with a negative return code: # python -c 'import subprocess,time,os,signal;p=subprocess.Popen(["sh","-c","sleep 10"]);time.sleep(1);os.kill(p.pid,signal.SIGSEGV);out,err=p.communicate();print(p.wait())' -11 we decided to use slaptest -u instead of slapschema for schema checking. slapschema also checks the actual database and this is not necessary (and error-prone) at this point. Successful build Package: univention-lib Version: 8.0.1-23A~4.4.0.201906241115 Branch: ucs_4.4-0 Scope: errata4.4-0 Verified: * Code review: Ok * Jenkins Test: Ok http://jenkins.knut.univention.de:8080/job/UCS-4.4/job/UCS-4.4-0/job/AutotestUpgrade/SambaVersion=s4,Systemrolle=master/lastCompletedBuild/testReport/10_ldap/ * Advisory: Ok |