Logback configuration problem (SizeAndTimeBasedRollingPolicy)

Paul B. Henson henson at acm.org
Sun Sep 15 03:16:29 UTC 2024


On Fri, Sep 13, 2024 at 12:01:55PM +0200, spf via users wrote:

>     looking for :-)   Seems this configuration file is preventing
>     Logback from working, or is ignored because some problem, but I
>     have not seen any error or warning in the output.   I am a bit
> [...]
>    <maxFileSize>1MB<maxFileSize>                                              

Add '-Dlogback.debug=true' to your jetty java arguments. Find errors in
your jetty console log:

20:07:28,455 |-ERROR in
ch.qos.logback.core.joran.event.SaxEventRecorder at f8fe81e - XML_PARSING -
Parsing fatal error on line 89 and column 6

20:07:28,456 |-ERROR in
ch.qos.logback.core.joran.event.SaxEventRecorder at f8fe81e -
org.xml.sax.SAXParseException; lineNumber: 89; columnNumber: 6; The
element type "maxFileSize" must be terminated by the matching end-tag
"</maxFileSize>".

20:07:28,549 |-ERROR in
net.shibboleth.shared.service.impl.LogbackLoggingService at 67e21ea2 -
Error loading logg ing configuration file: file
[/opt/shibboleth-idp/conf/logback.xml]
net.shibboleth.shared.service.ServiceExcep tion:
ch.qos.logback.core.joran.spi.JoranException: Problem parsing XML
document. See previously reported errors.

When I fix the syntax error it works fine. Seems less than ideal that
you only see fatal logback config errors if you turn on debugging but
<shrug>.



More information about the users mailing list