- logback-user - mailman3.qos.ch

Re: [logback-user] No logfile when starting application from a remote host
by Ceki Gülcü 13 May '19

13 May '19

access right issue? -------- Original message --------From: Michael.Fankanowsky(a)t-systems.com Date: 5/13/19 11:32 (GMT+01:00) To: logback-user(a)qos.ch Subject: [logback-user] No logfile when starting application from a remote host Hi, we are using logback v1.2.3 in a Springboot application which is running on Linux. When starting the application locally on the Linux host, logfile is created and application logs to it. When starting the application from a remote host via ssh then no logfile is created. When restarting the application (logfile is present and application has been logging to it) from a remote host, then no log messages will be logged to the existing logfile. It is working when restarting the application locally on the Linux host. Does anyone have an idea concerning this behavior? Best regards, Michael Fankanowsky

3 7

DBAppender
by haobo liu 29 Apr '19

29 Apr '19

Hi guys,does logback ch.qos.logback.classic.db.DBAppender will support mongo?

2 2

reduce threads in Logback 1.x
by Newcomb, Michael P 03 Apr '19

03 Apr '19

Can you release an update that reduces the number of core threads in the thread pool used by Logback? Logback 2.x has this fix, but I can't go to the latest version. Thanks, Michael

1 0

Problem with logback-access and logback-classic within Tomcat
by Simon Schabel 26 Mar '19

26 Mar '19

Hello, I tried to centralize logging in our docker environment by using logback as default logging framework. The idea is to use logback in our core application which compiles to a *.war file which is deployed in an Apache Tomcat v8.5. We now use Docker and I want to get a logging setup in our swarm like that: Our own *.war file is already successfully logging to STDOUT with logback and the logstash-logback-encoder. After I deployed the war to Tomcat running within a Docker container I realized that more information coming from Tomcat is logged via STDOUT and this is not in JSON format. I also read about logback-access and how to use it in Tomcat so I first added logback-access to the classpath of Tomcat and added a logback-access.xml config file as well. In the server.xml I added <Valve className="ch.qos.logback.access.tomcat.LogbackValve"/>. The server.xml looks like: <?xml version="1.0" encoding="UTF-8"?> <Server port="8005" shutdown="SHUTDOWN">  <Listener className="org.apache.catalina.core.AprLifecycleListener" SSLEngine="on"/> <Listener className="org.apache.catalina.core.JreMemoryLeakPreventionListener"/> <Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener"/> <Listener className="org.apache.catalina.core.ThreadLocalLeakPreventionListener"/> <GlobalNamingResources> <Resource name="UserDatabase" auth="Container" type="org.apache.catalina.UserDatabase" description="User database that can be updated and saved" factory="org.apache.catalina.users.MemoryUserDatabaseFactory" pathname="conf/tomcat-users.xml"/> </GlobalNamingResources> <Service name="Catalina"> <Connector port="8080" protocol="HTTP/1.1" connectionTimeout="20000" redirectPort="8443"/> <Connector port="8009" protocol="AJP/1.3" redirectPort="8443"/> <Engine name="Catalina" defaultHost="localhost"> <Realm className="org.apache.catalina.realm.LockOutRealm"> <Realm className="org.apache.catalina.realm.UserDatabaseRealm" resourceName="UserDatabase"/> </Realm> <Host name="localhost" appBase="webapps" unpackWARs="true" autoDeploy="true"> <Valve className="ch.qos.logback.access.tomcat.LogbackValve" /> </Host> </Engine> </Service> </Server> Running our war like this works. Now I wanted to make Tomcat to use logback as default logging framework as well and integrated ADD logback-core-1.2.3.jar /usr/local/tomcat/lib/ ADD logback-classic-1.2.3.jar /usr/local/tomcat/lib/ ADD logstash-logback-encoder-5.3.jar /usr/local/tomcat/lib/ ADD jackson-databind-2.9.8.jar /usr/local/tomcat/lib/ ADD jul-to-slf4j-1.7.26.jar /usr/local/tomcat/lib/ ADD slf4j-api-1.7.26.jar /usr/local/tomcat/lib/ ADD jackson-core-2.9.8.jar /usr/local/tomcat/lib/ ADD jackson-annotations-2.9.8.jar /usr/local/tomcat/lib/ to the lib folder as well as to the classpath via setenv.sh: export CLASSPATH="$CATALINA_HOME/lib/jul-to-slf4j-1.7.26.jar:$CATALINA_HOME/lib/slf4j-api-1.7.26.jar:$CATALINA_HOME/lib/logback-classic-1.2.3.jar:$CATALINA_HOME/lib/logstash-logback-encoder-5.3.jar:$CATALINA_HOME/lib/jackson-databind-2.9.8.jar:$CATALINA_HOME/lib/jackson-core-2.9.8.jar:$CATALINA_HOME/lib/jackson-annotations-2.9.8.jar:$CATALINA_HOME/lib/logback-access-1.2.3.jar:$CATALINA_HOME/lib/logback-core-1.2.3.jar:$CATALINA_HOME/conf/logback/" I also added a proper logback.xml for Tomcat. Unfortunately in this situation the Tomcat server process is not starting up correctly as the following error occurs: java.lang.NoClassDefFoundError: org/apache/catalina/Lifecycle at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:763) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) at java.net.URLClassLoader.defineClass(URLClassLoader.java:468) at java.net.URLClassLoader.access$100(URLClassLoader.java:74) at java.net.URLClassLoader$1.run(URLClassLoader.java:369) at java.net.URLClassLoader$1.run(URLClassLoader.java:363) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:362) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349) at java.lang.ClassLoader.loadClass(ClassLoader.java:411) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at org.apache.tomcat.util.digester.ObjectCreateRule.begin(ObjectCreateRule.java:116) at org.apache.tomcat.util.digester.Digester.startElement(Digester.java:1250) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:509) at com.sun.org.apache.xerces.internal.parsers.AbstractXMLDocumentParser.emptyElement(AbstractXMLDocumentParser.java:182) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:1339) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2784) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:602) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:505) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:842) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:771) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:141) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1213) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:643) at org.apache.tomcat.util.digester.Digester.parse(Digester.java:1518) at org.apache.catalina.startup.Catalina.load(Catalina.java:611) at org.apache.catalina.startup.Catalina.load(Catalina.java:662) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:309) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:492) Caused by: java.lang.ClassNotFoundException: org.apache.catalina.Lifecycle at java.net.URLClassLoader.findClass(URLClassLoader.java:382) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) ... 35 common frames omitted java.lang.NoClassDefFoundError: org/apache/catalina/Lifecycle at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:763) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) at java.net.URLClassLoader.defineClass(URLClassLoader.java:468) at java.net.URLClassLoader.access$100(URLClassLoader.java:74) at java.net.URLClassLoader$1.run(URLClassLoader.java:369) at java.net.URLClassLoader$1.run(URLClassLoader.java:363) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:362) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349) at java.lang.ClassLoader.loadClass(ClassLoader.java:411) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at org.apache.tomcat.util.digester.ObjectCreateRule.begin(ObjectCreateRule.java:116) at org.apache.tomcat.util.digester.Digester.startElement(Digester.java:1250) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:509) at com.sun.org.apache.xerces.internal.parsers.AbstractXMLDocumentParser.emptyElement(AbstractXMLDocumentParser.java:182) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:1339) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2784) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:602) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:505) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:842) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:771) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:141) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1213) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:643) at org.apache.tomcat.util.digester.Digester.parse(Digester.java:1518) at org.apache.catalina.startup.Catalina.load(Catalina.java:611) at org.apache.catalina.startup.Catalina.load(Catalina.java:662) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:309) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:492) Caused by: java.lang.ClassNotFoundException: org.apache.catalina.Lifecycle at java.net.URLClassLoader.findClass(URLClassLoader.java:382) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) ... 35 more Now if I commend out the line <Valve className="ch.qos.logback.access.tomcat.LogbackValve" /> from the server.xml the startup is running fine and Tomcat logs via logback-classic - but logback-access is not used. I found a question on stackoverflow.com where people seem to have the same problem but no solution is provided: https://stackoverflow.com/questions/32134974/added-logback-to-tomcat-got-ja… Does anyone has a hint for me what is going wrong? Best Simon

1 0

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-136
by Mahesh Kanote 11 Dec '18

11 Dec '18

Hi, I am also facing this issue https://jira.qos.ch/browse/LOGBACK-1361. As mentioned in jira this is fixed as part of 1.3.0-alpha1. I updated version from 1.2.3 to 1.3.0-alpha1 but started facing issue java.lang.NoClassDefFoundError: org/slf4j/impl/StaticLoggerBinder. When I compared 1.2.3 to 1.3.0-alpha1, package org.slf4j is empty in alpha version https://github.com/qos-ch/logback/tree/master/logback-classic/src/main/java… . Please help. Am I missing something? Thanks, Mahesh

1 1

logger configuration
by Joud Kassem 29 Nov '18

29 Nov '18

Hi guys, I'm upgrading my grails 2.5 app to grails 3.3.8 and started using logback, am new to it. My question is: I have long package hierarchy, for example: -----com ----------company ----------------controllers --------------------client -----------------------class1.groovy -----------------------class2.groovy -----------------------class3.groovy -----------------------class4.groovy -----------------------class5.groovy --------------------auth -----------------------class1.groovy -----------------------class2.groovy -----------------------class3.groovy -----------------------class4.groovy -----------------------class5.groovy --------------------security -----------------------class1.groovy -----------------------class2.groovy -----------------------class3.groovy -----------------------class4.groovy -----------------------class5.groovy I want to define logger for all the controllers (all the included classes), is it possible to do something like: logger("com.company.controllers.*", INFO, ['STDOUT'],false) ? or I have to do like this: logger("com.company.controllers.client", INFO, ['STDOUT'],false) logger("com.company.controllers.auth", INFO, ['STDOUT'],false) logger("com.company.controllers.security", INFO, ['STDOUT'],false) What is the best solution to not repeat a lot since I have a lot of child packages.s. Thanks in advance, Joud

2 1

Anyone has intelligent guesses on what these strange numbers are in the logs
by Tanin Na Nakorn 22 Nov '18

22 Nov '18

Hi Logback, Since a few days ago, we start seeing strange numbers showing up in our logs. Here are the logs: ``` Nov 19 11:06:42 [redacted] app/web.7: 10111111166611[error] 19:06:42 c.TransactionController - [redacted]. Nov 19 10:50:02 [redacted] app/web.3: 110111001111111111111111016111[warn] 18:50:02 c.BrowseController - [redacted] Nov 19 06:13:58 [redacted] app/web.2: 1101111111110[warn] 14:13:57 c.TransactionController - [redacted] Nov 19 05:33:26 [redacted] app/web.4: 111111111111111111001011[error] 13:33:26 c.TransactionController -[redacted] Nov 19 05:11:32 [redacted] app/web.3: 1111111111111111011[warn] 13:11:32 c.TransactionController - [redacted] Nov 19 04:42:30 [redacted] app/web.8: 01111111110111111110110[error] 12:42:30 c.TransactionController - [redacted] Nov 19 03:26:09 [redacted] app/web.4: 11011111006660000[error] 11:26:09 c.TransactionController - [redacted] ``` The numbers consists of 0, 1, and 6s. I have no idea what they are. My app is a Playframework 2.6 deployed on Heroku. The logs are sent to Papertrails. It seems these numbers show up since Heroku, so we can rule out Papertrails. Heroku also have no idea what they are. Running the app locally doesn't have this strange number issue. Here's my question on Stackoverflow: https://stackoverflow.com/questions/53381274/what-are-these-numbers-in-the-… (there's my log config in the post, but I don't think it's related). Thank you, Tanin

1 0

Extending logback configuration
by Rahul Narula 16 Oct '18

16 Oct '18

Hi I have a default logback config. similar to the one below <appender name="JSON_CONSOLE_APPENDER" class="ch.qos.logback.core.ConsoleAppender"> <encoder class="a.b.c.logging.CustomLogbackEncoder"> <providers> <timestamp/> <version/> <loggerName/> <threadName/> <logLevel/> <provider class="a.b.c.logging.LogMaskingProvider"> <rules> <rule> <name>cc</name> <pattern>\d{13,18}</pattern> </rule> <rule> <name>SSN</name> <pattern>\s+\d{3}-?\d{3}-?\d{4}\s+</pattern> </rule> </rules> <userRules>  </userRules> </provider> <stackTrace/> </providers> </encoder> The above config is read and configured using the ImplicitAction without any issue and binds to a POJO public class Rules { private final Set<Rule> rules = new LinkedHashSet<>(); public void addRule(Rule definition) { rules.add(definition.createRule()); } ... } acts as a default configuration. This default configuration is not directly available to the clients, so they can't directly make changes to it. I am looking for ways to extend this default configuration where in the different users can specify additional rules in <userRules>. This configuration is provided in separate file outside of logback.xml in a file called custom.xml something like <userRules> <rule> <name>email</name> <pattern>([a-zA-Z0-9_\-\.]+)(a)[a-zA-Z0-9_\-\.]+\.[a-zA-Z]{2,5}</pattern> </rule> <rule> ... </userRules> I am looking for help to implement this so as that the logback config is configured with the set of default + custom rules Any pointers around how to implement this will be helpful

1 0

How to configure HTTP-Proxies for appenders?
by Thorsten Schöning 05 Oct '18

05 Oct '18

Hi all, some of my customers sit behind HTTP-Proxies and I'm wondering what is needed to configure e.g. SMTPAppender to send mails through such proxies? Is there some API so I can change those settings on runtime? Or are only Java system proeprties for proxies supported? Are some appenders known to not work with HTTP-Proxies at all and is that documented somewhere? Are things like realms, authentication etc. supported? I couldn't find much on that topic myself. Thanks! Mit freundlichen Grüßen, Thorsten Schöning -- Thorsten Schöning E-Mail: Thorsten.Schoening(a)AM-SoFT.de AM-SoFT IT-Systeme http://www.AM-SoFT.de/ Telefon...........05151- 9468- 55 Fax...............05151- 9468- 88 Mobil..............0178-8 9468- 04 AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow

1 0