Red Hat Bugzilla – Bug 788749
Log not clear enough on schema errors
Last modified: 2013-07-22 00:59:43 EDT
This bug is created as a clone of upstream ticket: https://fedorahosted.org/389/ticket/35 https://bugzilla.redhat.com/show_bug.cgi?id=733349 {{{ When a schema file has an error, the log file is not clear enough and may give the impression the error is in dse.ldif Example: [25/Aug/2011:09:53:47 -0400] dse - parsing dse entry [attributeTypes] [25/Aug/2011:09:53:47 -0400] dse - Please edit the file to correct the reported problems and then restart the server. Expected behaviour: The server specifies in which file (and possible line number) the error was encountered. }}}
See upstream ticket for steps to reproduce
Adding a test case to tet.
Done. Added a test case bug788749 to schema/runschema.sh. -- -- M runschema.sh
Test is passed. quickinstall startup 100% (2/2) Schema startup 100% (1/1) Schema run 100% (1/1) Schema cleanup 100% (1/1) QuickUninstall cleanup 100% (1/1) Hence marking bug as VERIFIED.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Cause: When schema or configuration file had an error, the error was cryptic. Fix: Replaced the cryptic error logs with human readable ones.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2012-0813.html
As per comment - https://bugzilla.redhat.com/show_bug.cgi?id=788749#c4, Adding qe_test_coverage+ tag.