September 2015 - logback-user

Logback => TLS/SSL => Syslog ?
by Otis Gospodnetić 21 Feb '19

21 Feb '19

Hi, Does Logback support sending logs to Syslog servers via TLS/SSL? I have a feeling Logback doesn't have a SyslogAppender that can send data using TLS. I say that because I don't see a mention of "syslog" on http://logback.qos.ch/manual/usingSSL.html and I see http://jira.qos.ch/browse/LOGBACK-890 that mentions TLSSyslogAppender, but it looks like this never ended up in Logback. I've only found it committed here: https://github.com/balabit/logback/commit/e0d89de2536e0925a6c816a50793f6a74… Could anyone please clarify? Thanks, Otis -- Monitoring * Alerting * Anomaly Detection * Centralized Log Management Solr & Elasticsearch Support * http://sematext.com/

2 1

Logback extensions missing debug info
by Aleksandr Dubinsky 27 Nov '15

27 Nov '15

Please include debugging info when compiling source code (in particular, Logback Spring extension), so that stepping through logback source code is possible when debugging.

3 2

How to control logback-access.xml initialization log?
by coolnodje 18 Sep '15

18 Sep '15

Hi, I'm using both logback-access.xml and logback.xml in a Spring boot application. I have <logger name="ch.qos.logback" level="WARN" /> set in the logback-spring.xml but on application startup I get the following log: //application startup logback.xml formatted log ... 2015-09-17 13:31:49.056 INFO 22580 --- [ main] s.b.c.e.t.TomcatEmbeddedServletContainer : Tomcat initialized with port(s): 8080 (http) //logback-access init log starts with a different pattern 13:31:49,711 |-INFO in ch.qos.logback.access.joran.action.ConfigurationAction - debug attribute not set 13:31:49,714 |-INFO in ch.qos.logback.core.joran.action.StatusListenerAction - Added status listener of type [ch.qos.logback.core.status.OnConsoleStatusListener] 13:31:49,715 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.rolling.RollingFileAppender] 13:31:49,715 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [querydiff] 13:31:49,752 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.access.boolex.JaninoEventEvaluator] for [evaluator] property 13:31:49,774 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.core.boolex.Matcher] for [matcher] property 13:31:49,815 |-INFO in ch.qos.logback.access.boolex.JaninoEventEvaluator@4fa3ffe0 - Adding [return] prefix and a semicolon suffix. Expression becomes [return url.matches(event.getRequestURL().toString());] 13:31:49,815 |-INFO in ch.qos.logback.access.boolex.JaninoEventEvaluator@4fa3ffe0 - See also http://logback.qos.ch/codes.html#block 13:31:50,031 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy - Will use zip compression 13:31:50,032 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy - Will use the pattern logs/querydiff-access.%d{yyyy-MM-dd}.log for the active file 13:31:50,033 |-INFO in c.q.l.core.rolling.DefaultTimeBasedFileNamingAndTriggeringPolicy - The date pattern is 'yyyy-MM-dd' from file name pattern 'logs/querydiff-access.%d{yyyy-MM-dd}.log.zip'. 13:31:50,033 |-INFO in c.q.l.core.rolling.DefaultTimeBasedFileNamingAndTriggeringPolicy - Roll-over at midnight. 13:31:50,034 |-INFO in c.q.l.core.rolling.DefaultTimeBasedFileNamingAndTriggeringPolicy - Setting initial period to Thu Sep 17 12:44:43 CST 2015 13:31:50,034 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.access.PatternLayoutEncoder] for [encoder] property 13:31:50,069 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[querydiff] - Active log file name: logs/querydiff-access.log 13:31:50,069 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[querydiff] - File property is set to [logs/querydiff-access.log] 13:31:50,070 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [querydiff] to ch.qos.logback.access.tomcat.LogbackValve[] 13:31:50,070 |-INFO in ch.qos.logback.access.joran.action.ConfigurationAction - End of configuration. 13:31:50,070 |-INFO in ch.qos.logback.access.joran.JoranConfigurator@5814c52f - Registering current configuration as safe fallback point 13:31:49,711 |-INFO in ch.qos.logback.access.joran.action.ConfigurationAction - debug attribute not set 13:31:49,714 |-INFO in ch.qos.logback.core.joran.action.StatusListenerAction - Added status listener of type [ch.qos.logback.core.status.OnConsoleStatusListener] 13:31:49,715 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.rolling.RollingFileAppender] 13:31:49,715 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [querydiff] 13:31:49,752 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.access.boolex.JaninoEventEvaluator] for [evaluator] property 13:31:49,774 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.core.boolex.Matcher] for [matcher] property 13:31:49,815 |-INFO in ch.qos.logback.access.boolex.JaninoEventEvaluator@4fa3ffe0 - Adding [return] prefix and a semicolon suffix. Expression becomes [return url.matches(event.getRequestURL().toString());] 13:31:49,815 |-INFO in ch.qos.logback.access.boolex.JaninoEventEvaluator@4fa3ffe0 - See also http://logback.qos.ch/codes.html#block 13:31:50,031 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy - Will use zip compression 13:31:50,032 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy - Will use the pattern logs/querydiff-access.%d{yyyy-MM-dd}.log for the active file 13:31:50,033 |-INFO in c.q.l.core.rolling.DefaultTimeBasedFileNamingAndTriggeringPolicy - The date pattern is 'yyyy-MM-dd' from file name pattern 'logs/querydiff-access.%d{yyyy-MM-dd}.log.zip'. 13:31:50,033 |-INFO in c.q.l.core.rolling.DefaultTimeBasedFileNamingAndTriggeringPolicy - Roll-over at midnight. 13:31:50,034 |-INFO in c.q.l.core.rolling.DefaultTimeBasedFileNamingAndTriggeringPolicy - Setting initial period to Thu Sep 17 12:44:43 CST 2015 13:31:50,034 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.access.PatternLayoutEncoder] for [encoder] property 13:31:50,069 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[querydiff] - Active log file name: logs/querydiff-access.log 13:31:50,069 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[querydiff] - File property is set to [logs/querydiff-access.log] 13:31:50,070 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [querydiff] to ch.qos.logback.access.tomcat.LogbackValve[] 13:31:50,070 |-INFO in ch.qos.logback.access.joran.action.ConfigurationAction - End of configuration. 13:31:50,070 |-INFO in ch.qos.logback.access.joran.JoranConfigurator@5814c52f - Registering current configuration as safe fallback point //application startup logback.xml formatted log continues 2015-09-17 13:31:50.138 INFO 22580 --- [ost-startStop-1] com.ptmind.api.userinfo.Application : Running with Spring profile(s) : [dev] Logback-access init code doesn't seem to log through the configured logback instance. I hope the problem is clear. Best

1 1

How to control logback-access.xml initialization log?
by coolnodje 17 Sep '15

17 Sep '15

Sorry for the bad formatting, a better looking stacktrace is available at : https://gist.github.com/nodje/415da719810bcaecc02d

1 0

catch hazelcast logs when you start service as a daemon
by Ulku Kondoz 17 Sep '15

17 Sep '15

Hi guys, I am using hazelcast in my service and when I start my service from idea or run the start-up script (./script.sh), I can see hazelcast node discovery logs in both console and log file. Members [1] { Member [X.X.X.X]:5500 this } However, when I start my service "sudo service service-name start", which calls the same start-up script but runs it with start-stop-deamon, I cannot see hazelcast node discovery logs in the log file. hazelcast logback settings ..... <logger name="com.hazelcast" level="INFO" additivity="false"> <appender-ref ref="file"/> <appender-ref ref="console" /> </logger> Which configuration do I need to do in order to see the node discovery in the log file? Thanks, Ulku

1 0

NoClassDefFoundError when activating LogbackValve(hogback-access) in tomcat
by John Lawrence Dowson 10 Sep '15

10 Sep '15

Hi, I am trying to use the LogbackValve but am getting the following error (and tomcat fails to start) when adding the valve to the CATALINA_BASE/conf/server.xml file: ERROR main org.apache.tomcat.util.digester.Digester - Begin event threw error java.lang.NoClassDefFoundError: org/apache/catalina/Lifecycle at java.lang.ClassLoader.defineClass1(Native Method) ~[na:1.7.0_04] … Caused by: java.lang.ClassNotFoundException: org.apache.catalina.Lifecycle at java.net.URLClassLoader$1.run(URLClassLoader.java:366) ~[na:1.7.0_04] … Environment is as follows: Tomcat 7.0.57 (with APR) logback 1.1.3 with the tomcat environment being set with the following CATALINA_BASE/bin/setenv.sh file: #!/bin/sh CLASSPATH=$CLASSPATH:$CATALINA_BASE/bin/jul-to-slf4j-1.7.12.jar:\ $CATALINA_BASE/bin/jcl-over-slf4j-1.7.12.jar:\ $CATALINA_BASE/bin/slf4j-api-1.7.12.jar:\ $CATALINA_BASE/bin/logback-core-1.1.3.jar:\ $CATALINA_BASE/bin/logback-classic-1.1.3.jar:\ $CATALINA_BASE/bin/logback-access-1.1.3.jar:\ $CATALINA_BASE/bin/logback-config/ This seems strange to me as the Lifecycle interface should be available in the catalina.jar file, which must be on the class path….. Any ideas? Thanks in advance, John

1 0