- logback-user - mailman3.qos.ch

Re: [logback-user] logback autoscan is not working intermittently in k8s pod
by Kedar Sirshikar 20 Aug '21

20 Aug '21

yes we tried but the issue was not observed on a stand alone machine without k8s (on logback version 1.2.3) so there is definitely some role of k8s like ConfigMap. Currently, I am facing challenges in order to downgrade dependency to 1.1.3 in the product but I'll keep you posted in case I would be able to verify with 1.1.3 In addition, we suggested our client to restart all k8s pods showing this anomaly however client disagreed saying it may have an adverse impact and is asking for root cause analysis. Let me know if you need any additional information, I can share that as issue is getting consistently reproduced after updating log-level 7-8 times. Thanks, Kedar. On Fri, Aug 20, 2021 at 3:00 AM <logback-user-request(a)qos.ch> wrote: > Send logback-user mailing list submissions to > logback-user(a)qos.ch > > To subscribe or unsubscribe via the World Wide Web, visit > http://mailman.qos.ch/mailman/listinfo/logback-user > or, via email, send a message with subject or body 'help' to > logback-user-request(a)qos.ch > > You can reach the person managing the list at > logback-user-owner(a)qos.ch > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of logback-user digest..." > > > Today's Topics: > > 1. Re: logback autoscan is not working intermittently in k8s pod > (Ceki Gülcü) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 20 Aug 2021 11:35:19 +0200 > From: Ceki Gülcü <ceki(a)qos.ch> > To: logback-user(a)qos.ch > Subject: Re: [logback-user] logback autoscan is not working > intermittently in k8s pod > Message-ID: <571ae229-e3ea-93b8-1ad7-b949db706741(a)qos.ch> > Content-Type: text/plain; charset=utf-8; format=flowed > > Hello Kedar, > > Have you tried to reproduce the problem on a stand alone machine without > k8? > > > > On 20/08/2021 00:41, Kedar Sirshikar wrote: > > Hello Ceki, > > I tried debugging by reproducing the issue and observed that after 7th > > attempt of log change, autoScan stops working. > > > > Have you came across similar issue in 1.2.3 version where autoScan does > > not pick changes from config xml if it gets changed after a certain > count ? > > In the meantime, I am trying to see if same issue occurs on 1.1.3 > > version because setMainWatchURL method inConfigurationWatchListUtil is > > different on both versions. > > > > > > Thanks, > > Kedar. > > > > > > On Sat, Aug 14, 2021 at 3:00 AM <logback-user-request(a)qos.ch > > <mailto:logback-user-request@qos.ch>> wrote: > > > > Send logback-user mailing list submissions to > > logback-user(a)qos.ch <mailto:logback-user@qos.ch> > > > > To subscribe or unsubscribe via the World Wide Web, visit > > http://mailman.qos.ch/mailman/listinfo/logback-user > > <http://mailman.qos.ch/mailman/listinfo/logback-user> > > or, via email, send a message with subject or body 'help' to > > logback-user-request(a)qos.ch <mailto:logback-user-request@qos.ch> > > > > You can reach the person managing the list at > > logback-user-owner(a)qos.ch <mailto:logback-user-owner@qos.ch> > > > > When replying, please edit your Subject line so it is more specific > > than "Re: Contents of logback-user digest..." > > > > > > Today's Topics: > > > > 1. Re: logback autoscan is not working intermittently in k8s pod > > (Ceki Gülcü) > > > > > > > ---------------------------------------------------------------------- > > > > Message: 1 > > Date: Fri, 13 Aug 2021 14:51:09 +0200 > > From: Ceki Gülcü <ceki(a)qos.ch <mailto:ceki@qos.ch>> > > To: logback-user(a)qos.ch <mailto:logback-user@qos.ch> > > Subject: Re: [logback-user] logback autoscan is not working > > intermittently in k8s pod > > Message-ID: <f39cbede-6e95-7e60-d01e-ca27599bf453(a)qos.ch > > <mailto:f39cbede-6e95-7e60-d01e-ca27599bf453@qos.ch>> > > Content-Type: text/plain; charset=utf-8; format=flowed > > > > Hello Kedar, > > > > > > I see that changes to the logback config file are picked up. There > are > > some errors reported when processing the configuration file but these > > are unrelated to the issue at hand, i.e. auto scan not working. > > > > I don't have further suggestions. > > > > --Ceki > > > > > > On 13/08/2021 09:59, Kedar Sirshikar wrote: > > > Hello team, > > > Just trying to check if anyone got a chance to look at this case? > > > Appreciate if any clue/hint is provided to resolve this issue. > > > > > > Thanks, > > > Kedar. > > > > > > > > > On Wed, Aug 11, 2021 at 12:57 PM Kedar Sirshikar > > > <kedargsirshikar(a)gmail.com <mailto:kedargsirshikar@gmail.com> > > <mailto:kedargsirshikar@gmail.com > > <mailto:kedargsirshikar@gmail.com>>> wrote: > > > > > > Resending the attachment by updating the subject. Please let > > me know > > > if any additional details are required from my side. > > > > > > Thanks, > > > Kedar. > > > > > > > > > ---------- Forwarded message --------- > > > From: *Kedar Sirshikar* <kedargsirshikar(a)gmail.com > > <mailto:kedargsirshikar@gmail.com> > > > <mailto:kedargsirshikar@gmail.com > > <mailto:kedargsirshikar@gmail.com>>> > > > Date: Wed, Aug 11, 2021 at 7:58 AM > > > Subject: Re: logback-user Digest, Vol 115, Issue 2 > > > To: <logback-user(a)qos.ch <mailto:logback-user@qos.ch> > > <mailto:logback-user@qos.ch <mailto:logback-user@qos.ch>>> > > > > > > > > > Hi Ceki, Thank you for the reply. Forgot to send the logs > > earlier so > > > please refer attachment. > > > I have also added Notes at lines 1 and 91 to describe the > test. > > > > > > > > > Thanks, > > > Kedar. > > > > > > > > > On Wed, Aug 11, 2021 at 3:00 AM <logback-user-request(a)qos.ch > > <mailto:logback-user-request@qos.ch> > > > <mailto:logback-user-request@qos.ch > > <mailto:logback-user-request@qos.ch>>> wrote: > > > > > > Send logback-user mailing list submissions to > > > logback-user(a)qos.ch <mailto:logback-user@qos.ch> > > <mailto:logback-user@qos.ch <mailto:logback-user@qos.ch>> > > > > > > To subscribe or unsubscribe via the World Wide Web, visit > > > http://mailman.qos.ch/mailman/listinfo/logback-user > > <http://mailman.qos.ch/mailman/listinfo/logback-user> > > > <http://mailman.qos.ch/mailman/listinfo/logback-user > > <http://mailman.qos.ch/mailman/listinfo/logback-user>> > > > or, via email, send a message with subject or body 'help' > to > > > logback-user-request(a)qos.ch <mailto:logback-user-request@qos.ch> > > <mailto:logback-user-request@qos.ch > > <mailto:logback-user-request@qos.ch>> > > > > > > You can reach the person managing the list at > > > logback-user-owner(a)qos.ch <mailto:logback-user-owner@qos.ch> > > <mailto:logback-user-owner@qos.ch <mailto:logback-user-owner@qos.ch > >> > > > > > > When replying, please edit your Subject line so it is > > more specific > > > than "Re: Contents of logback-user digest..." > > > > > > > > > Today's Topics: > > > > > > 1. logback autoscan is not working intermittently in > > k8s pod > > > (Kedar Sirshikar) > > > 2. Re: logback autoscan is not working intermittently > > in k8s pod > > > (Ceki Gülcü) > > > > > > > > > > > > ---------------------------------------------------------------------- > > > > > > Message: 1 > > > Date: Tue, 10 Aug 2021 23:07:51 -0700 > > > From: Kedar Sirshikar <kedargsirshikar(a)gmail.com > > <mailto:kedargsirshikar@gmail.com> > > > <mailto:kedargsirshikar@gmail.com > > <mailto:kedargsirshikar@gmail.com>>> > > > To: logback-user(a)qos.ch <mailto:logback-user@qos.ch> > > <mailto:logback-user@qos.ch <mailto:logback-user@qos.ch>> > > > Subject: [logback-user] logback autoscan is not working > > > intermittently > > > in k8s pod > > > Message-ID: > > > > > > > > <CAO= > cJL+EMFCTe7En+7nqUmzaxQoYVEYN1GXCYwdwfkt0KbjiDQ(a)mail.gmail.com <mailto: > cJL%2BEMFCTe7En%2B7nqUmzaxQoYVEYN1GXCYwdwfkt0KbjiDQ(a)mail.gmail.com> > > > > > <mailto: > cJL%2BEMFCTe7En%2B7nqUmzaxQoYVEYN1GXCYwdwfkt0KbjiDQ(a)mail.gmail.com > <mailto: > cJL%252BEMFCTe7En%252B7nqUmzaxQoYVEYN1GXCYwdwfkt0KbjiDQ(a)mail.gmail.com>>> > > > Content-Type: text/plain; charset="utf-8" > > > > > > Hi team, > > > I have raised a detailed query here > > > > > < > https://stackoverflow.com/questions/68721761/logback-autoscan-is-not-workin… > < > https://stackoverflow.com/questions/68721761/logback-autoscan-is-not-workin… > > > > > > > < > https://stackoverflow.com/questions/68721761/logback-autoscan-is-not-workin… > < > https://stackoverflow.com/questions/68721761/logback-autoscan-is-not-workin… > >>> > > > about > > > the issue I am facing. > > > Can someone please share inputs or any hint for solving > the > > > above problem? > > > Let me know if any details are required from my side. > > > > > > Thanks, > > > Kedar. > > >

1 0

Re: [logback-user] Sysout message - LOGBACK: No context given
by ajitpawar 18 Aug '21

18 Aug '21

> Hi, > I am using logback-classic 1.2.3 for logging in my application > The logback.xml is attached. > I am seeing this message on console, > > LOGBACK: No context given for ch.qos.logback.core.spi.ContextAwareBase@787f845 > > Please note this message appears when used conversion rule 'highlight'. Same is the case for custom conversion rule as well. > Which is really annoying, how can we disable this message ? > > Thanks, > Ajit. > > Sent with [ProtonMail](https://protonmail.com/) Secure Email.

2 2

Logback DbAppender stops working when @RefreshScope annotation is used for config changes
by Moser Baer 17 Aug '21

17 Aug '21

Hi, I'm using logback's DBAppender to log the http request/response into the DataBase (logging_event) table in my Springboot app. Below given is the Java configuration class for DbAppender. @Configuration public class LogbackConfiguration { @Bean public DBAppender dbAppender(DataSource ds){ DBAppender dbAppender = new DBAppender(); LoggerContext loggerContext = (LoggerContext) LoggerFactory.getILoggerFactory(); Logger logger = loggerContext.getLogger("org.zalando.logbook"); loggerContext.start(); DataSourceConnectionSource connectionSource = new DataSourceConnectionSource(); connectionSource.setDataSource(ds ); connectionSource.setContext(loggerContext); connectionSource.start(); dbAppender.setConnectionSource(connectionSource); dbAppender.start(); logger.addAppender(dbAppender); return dbAppender; }} I have another configuration class that has configuration properties and the values of those properties can be changed dynamically. I'm using the @RefreshScope ( *org.springframework.cloud.context.config.annotation.RefreshScope*) annotation to get the new values of the config properties on the fly. The DBAppender works fine, except when I make any changes to any of the configuration properties externally (changing the value of an existing property or adding a new config property in Consul) while the app is running. After I make any changes to any config property externally, the DbAppender stops logging into the DB table. Console logger continues to work fine. No error/exception message. I will have to restart the app everytime after I change a config value to get the DbAppender working. Could you please guide me on this issue? Thank you!

1 0

Re: [logback-user] logback-user Digest, Vol 115, Issue 2
by Kedar Sirshikar 13 Aug '21

13 Aug '21

Hi Ceki, Thank you for the reply. Forgot to send the logs earlier so please refer attachment. I have also added Notes at lines 1 and 91 t describe the test. Thanks, Kedar. On Wed, Aug 11, 2021 at 3:00 AM <logback-user-request(a)qos.ch> wrote: > Send logback-user mailing list submissions to > logback-user(a)qos.ch > > To subscribe or unsubscribe via the World Wide Web, visit > http://mailman.qos.ch/mailman/listinfo/logback-user > or, via email, send a message with subject or body 'help' to > logback-user-request(a)qos.ch > > You can reach the person managing the list at > logback-user-owner(a)qos.ch > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of logback-user digest..." > > > Today's Topics: > > 1. logback autoscan is not working intermittently in k8s pod > (Kedar Sirshikar) > 2. Re: logback autoscan is not working intermittently in k8s pod > (Ceki Gülcü) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 10 Aug 2021 23:07:51 -0700 > From: Kedar Sirshikar <kedargsirshikar(a)gmail.com> > To: logback-user(a)qos.ch > Subject: [logback-user] logback autoscan is not working intermittently > in k8s pod > Message-ID: > <CAO= > cJL+EMFCTe7En+7nqUmzaxQoYVEYN1GXCYwdwfkt0KbjiDQ(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hi team, > I have raised a detailed query here > < > https://stackoverflow.com/questions/68721761/logback-autoscan-is-not-workin… > > > about > the issue I am facing. > Can someone please share inputs or any hint for solving the above problem? > Let me know if any details are required from my side. > > Thanks, > Kedar. >

2 3

logback autoscan is not working intermittently in k8s pod
by Kedar Sirshikar 11 Aug '21

11 Aug '21

Hi team, I have raised a detailed query here <https://stackoverflow.com/questions/68721761/logback-autoscan-is-not-workin…> about the issue I am facing. Can someone please share inputs or any hint for solving the above problem? Let me know if any details are required from my side. Thanks, Kedar.

2 1

Backport the fix of LOGBACK- in 1.2.x branch ?
by Laurent Vaills 04 Aug '21

04 Aug '21

Hi, I just noticed that the following issue https://jira.qos.ch/browse/LOGBACK-1465 (xxe vulnerability in Logback) has been fixed for 1.3.0-alpha7 . As this issue has been flagged by our vulnerability scanner, I was wondering if you plan to backport the fix in the branch 1.2.x and release a 1.2.6 ? Regards, Laurent

1 0

Logback 1.3.0-alpha5
by Ian Springer 28 Jul '21

28 Jul '21

Is Logback 1.3.0-alpha5 stable enough to use in production? I know alpha typically means not ready for production, but I also noticed the Logback docs now reference 1.3.0-alpha5. Thanks! Ian

1 0

Logback DbAppender is not working when a config property is updated dynamically using @RefreshScope annotation
by Moser Baer 27 Jul '21

27 Jul '21

Hi, I'm using logback in application to log the http request/response into the DataBase (logging_event) table. Below given is the Java configuration class for DbAppender. In my application, I have another configuration class that has some configuration properties and the values of those properties can change dynamically. I'm using the @RefreshScope (org.springframework.cloud. context.config.annotation.RefreshScope) annotation to get the new values of the config properties changed on the fly using https://www.consul.io/. The DBAppender works fine, except that when I make any changes to the configuration properties externally (changing the value of an existing property or adding a new config property in Consul) while the app is running. After I make any changes to a config property externally, the DbAppender will not insert logs into the DB table. These config properties are not related to the logging functionality. @Configuration public class LogbackConfiguration { @Bean public DBAppender dbAppender(DataSource ds){ DBAppender dbAppender = new DBAppender(); DataSourceConnectionSource connectionSource = new DataSourceConnectionSource(); connectionSource.setDataSource(ds ); connectionSource.start(); dbAppender.setConnectionSource(connectionSource); dbAppender.start(); LoggerContext loggerContext = (LoggerContext) LoggerFactory. getILoggerFactory(); Logger logger = loggerContext.getLogger("org.zalando.logbook"); logger.addAppender(dbAppender); return dbAppender; } } Below given is the configurations related to logging in my application.yml file - logbook: minimum-status: 100 exclude: - /actuator/** - /favicon.ico - /swagger-resources/** - /swagger-ui.html - /webjars/** logging: level: org.zalando.logbook: TRACE Could you please guide me to identify the root cause of this issue? Thanks

1 0

Release of logback version 1.2.4
by Ceki 19 Jul '21

19 Jul '21

Hello all, I am happy to announce the release of logback version 1.2.4. It contains bug fixes with no major changes. Note that the 1.2.x series offers significant performance improvements over the 1.1.x series. The 1.2.x series also fixes a rather severe serialization vulnerability in SocketServer and ServerSocketReceiver. Users running these components should upgrade immediately. Please refer to the news page for precise details. http://logback.qos.ch/news.html For review of performance figures, see: http://tinyurl.com/logbackPerf You can receive logback related announcements by subscribing to the QOS.ch announce mailing list. To subscribe to QOS.ch announce list, please visit the following URL. http://www.qos.ch/mailman/listinfo/announce You may also receive announcements via twitter by following: https://twitter.com/qos_ch Enjoy, -- Ceki Gülcü

1 0

Unsuccessful delete in FixedWindowRollingPolicy causes disk trashing and cpu at 100%
by Carl-Erik Kopseng 23 Jun '21

23 Jun '21

Hi, for some weeks we have observed some really mysterious behavior when enabling one of our appenders. This appender was configured specially to use the `FixedWindowRollingPolicy`. What we observed, was that after some time of debug logging, the CPU would suddenly hit the roof and have at least one core fully pegged at 100%. Using Jprofiler we found the issue to be various cases of `logger.debug()` that would be used by this special appender. Disabling the appender immediately fixed the issue (as we have `scan=true`) I debugged this yesterday and found the answer partly in the logs and in the logback code. This is the line that basically shows the issue: if (!file2zip.delete()) { addStatus(new WarnStatus("Could not delete [" + nameOfFile2zip + "].", this)); } The logs were full of this and I also found references to this online. I documented the entire process and findings in this repo: https://github.com/fatso83/logback-bug. The repo also contains a minimal attempt at recreating what I saw on the Windows servers on my local machine. I was unable to reproduce this locally, which I kind of need in order to fix this bug. So, I was just wondering if any of you had any tips? What could cause the file to be "locked" / prevented from being deleted? Would it be enough if someone had a read-handle on the file, for instance a log reader like `glogg <https://glogg.bonnefon.org>`? I made sure to close my own programs when looking at this, but there are multiple users that look at these logs. There is a single JVM running this app. -- Carl-Erik Kopseng Senior developer Diffia AS

1 1