- logback-user - mailman3.qos.ch

Joran Conditional Configuration
by Josh Cooke 19 Oct '21

19 Oct '21

Hi, Support for Joran Conditional Configuration was removed in 1.3.0-alpha5, I believe with the intention to rebuild it. We’re now in a situation where major release versions of common open source libraries (Jetty 10, for example) are importing recent versions of the 1.3 alpha, forcing users to upgrade their dependency trees accordingly. We use conditional configuration widely in our applications but we’re unable to upgrade logback beyond alpha4 due to the lack of conditional support. Is this support going to be re-implemented any time soon? How can we work around the compatibility issues? We’re currently in the difficult position of not being able to update a large number of dependencies because they all lead back to logback >alpha5. Any help would be much appreciated! Thanks, Josh <https://www.starlingbank.com/?utm_source=gmail&utm_medium=email&utm_campaig…> JOSH COOKE TECH LEAD - DATA ENGINEERING STARLING BANK Download from App Store <https://itunes.apple.com/gb/app/starling-bank/id956806430?pt=117314812&ct=e…> or Google Play <https://play.google.com/store/apps/details?id=com.starlingbank.android&refe…> and apply for an account in minutes. <https://www.starlingbank.com/?utm_source=gmail&utm_medium=email&utm_campaig…> <https://twitter.com/StarlingBank/> <https://www.facebook.com/starlingbank/> <https://www.instagram.com/starlingbank/> <https://www.starlingbank.com/?utm_source=gmail&utm_medium=email&utm_campaig…>We’re hiring - click here to discover more <https://www.starlingbank.com/careers/>. Starling Bank is registered in England and Wales as Starling Bank Limited (No.09092149), 3rd floor, 2 Finsbury Avenue, London, EC2M 2PP <https://maps.google.com/?q=3rd+floor,+2+Finsbury+Avenue,+London,+EC2M+2PP&e…>. We are authorised by the Prudential Regulation Authority and regulated by the Financial Conduct Authority and the Prudential Regulation Authority under registration number 730166. Starling Bank Limited is a member of the Financial Services Compensation Scheme and the Financial Ombudsman Service.

2 1

Re: [logback-user] Ambiguous vulnerability assessment help
by Angelo Rauseo 10 Sep '21

10 Sep '21

Update: Some more data has emerged, and after inquiring with JFrog, they pointed me to the issue being connected to what is under work in https://jira.qos.ch/browse/LOGBACK-1574 and https://github.com/qos-ch/logback/pull/305. It seems the root of the concern is the hostname validation. Angelo From: Angelo Rauseo <angelo.rauseo(a)workday.com> Date: Tuesday, September 7, 2021 at 09:00 To: logback users list <logback-user(a)qos.ch> Subject: Re: [External Sender] Re: [logback-user] Ambiguous vulnerability assessment help Ciao David, Thank you for your reply and the recommendations. I am trying to reach out to JFrog and to see what data they have, and I think it is reasonable to not use logback apis to reach out to servers via TLS/SSL to stay safe. Even with all the precautions, I am still a bit confused by the lack of details and somewhat concerned about finding the root cause of a MiTM issue. Is there anyone here with experience of TLS connectivity in logback? Which would be the APIs involved? Thanks for your time, Angelo From: logback-user <logback-user-bounces(a)qos.ch> on behalf of David Roussel <nabble(a)diroussel.xsmail.com> Reply-To: logback users list <logback-user(a)qos.ch> Date: Saturday, September 4, 2021 at 02:10 To: logback users list <logback-user(a)qos.ch> Subject: [External Sender] Re: [logback-user] Ambiguous vulnerability assessment help Ciao Angelo, To reproduce this might take quite a bit of work, as the report you copied doesn’t provide details of how the MITM cert was spoofed. It might be as simple as not validating the cert at all. But if you have support from JFrog, then I would be best to contact them for more details. I don’t currently use logback myself, but when I did I never relied on any feature that connected out to TLS endpoints. If you don’t either, then you can ignore this issue. If your logback usage does include connecting out to TLS endpoints, then in each case you need to consider how confidential is that data, what could the impact of a MITM be, and what control do you have over the cert validation. The problem is that there are many ways in which TLS connections can be made, even just parsing an XML document can cause network requests. David On 27 Aug 2021, at 17:31, Angelo Rauseo <angelo.rauseo(a)workday.com<mailto:angelo.rauseo@workday.com>> wrote: Hello everyone, I am looking for details about a vulnerability listed in JFrog X-Ray (see below) that does not have much data attached to it in the report (no CVE, no links to analysis). My end goal would be to eventually help resolve it, but I have no data about the source to start from. Anyone here that can help me assess it? Thank you for your time and assistance! Angelo ┌─────────────────────┬────────────────────────────────────────────────────────────────────────────────────────────────────┐ │ Summary │ logback SSL Certificate Validation Failure MitM Spoofing │ ├─────────────────────┼────────────────────────────────────────────────────────────────────────────────────────────────────┤ │ Severity │ MEDIUM │ ├─────────────────────┼────────────────────────────────────────────────────────────────────────────────────────────────────┤ │ Description │ logback contains a flaw as X.509 certificates are not properly validated. By spoofing the TLS/SSL │ │ │ server via a certificate that appears valid, an attacker with the ability to intercept network │ │ │ traffic (e.g. MitM, DNS cache poisoning) can disclose and optionally manipulate transmitted data. │ ├─────────────────────┼────────────────────────────────────────────────────────────────────────────────────────────────────┤ │ Type │ SECURITY │ ├─────────────────────┼────────────────────────────────────────────────────────────────────────────────────────────────────┤ │ Provider │ JFrog │ ├─────────────────────┼────────────────────────────────────────────────────────────────────────────────────────────────────┤ │ Issues │ 4.0/CVSS:2.0/AV:N/AC:H/Au:N/C:P/I:P/A:N │ ├─────────────────────┼────────────────────────────────────────────────────────────────────────────────────────────────────┤ │ Edited │ 2021-04-15T09:22:04Z │ ├─────────────────────┼────────────────────────────────────────────────────────────────────────────────────────────────────┤ │ Created │ 2019-05-02T00:00:00.297Z │ ├─────────────────────┼────────────────────────────────────────────────────────────────────────────────────────────────────┤ │ Impact paths │ - │ │ │ /sha256__11533f8a115abc3bbf6840bebe91a8616a0ee04cd4bdad4094ed62e6f86d4432.tar.gz/usr/share/fugu/li │ │ │ b/ch.qos.logback-logback-core-1.2.3.jar │ ├─────────────────────┼────────────────────────────────────────────────────────────────────────────────────────────────────┤ │ │ Affected component ID: gav://ch.qos.logback:logback-core:1.2.3 │ ├─────────────────────┼────────────────────────────────────────────────────────────────────────────────────────────────────┤ │ Vulnerable versions │ 1.0.12 ≤ Version ≤ 1.3.0-alpha5 │ ├─────────────────────┼────────────────────────────────────────────────────────────────────────────────────────────────────┤ │ Fixed versions │ │ └─────────────────────┴────────────────────────────────────────────────────────────────────────────────────────────────────┘ _______________________________________________ logback-user mailing list logback-user(a)qos.ch<mailto:logback-user@qos.ch> http://mailman.qos.ch/mailman/listinfo/logback-user<https://urldefense.proofpoint.com/v2/url?u=http-3A__mailman.qos.ch_mailman_…>

1 0

Ambiguous vulnerability assessment help
by Angelo Rauseo 07 Sep '21

07 Sep '21

Hello everyone, I am looking for details about a vulnerability listed in JFrog X-Ray (see below) that does not have much data attached to it in the report (no CVE, no links to analysis). My end goal would be to eventually help resolve it, but I have no data about the source to start from. Anyone here that can help me assess it? Thank you for your time and assistance! Angelo ┌─────────────────────┬────────────────────────────────────────────────────────────────────────────────────────────────────┐ │ Summary │ logback SSL Certificate Validation Failure MitM Spoofing │ ├─────────────────────┼────────────────────────────────────────────────────────────────────────────────────────────────────┤ │ Severity │ MEDIUM │ ├─────────────────────┼────────────────────────────────────────────────────────────────────────────────────────────────────┤ │ Description │ logback contains a flaw as X.509 certificates are not properly validated. By spoofing the TLS/SSL │ │ │ server via a certificate that appears valid, an attacker with the ability to intercept network │ │ │ traffic (e.g. MitM, DNS cache poisoning) can disclose and optionally manipulate transmitted data. │ ├─────────────────────┼────────────────────────────────────────────────────────────────────────────────────────────────────┤ │ Type │ SECURITY │ ├─────────────────────┼────────────────────────────────────────────────────────────────────────────────────────────────────┤ │ Provider │ JFrog │ ├─────────────────────┼────────────────────────────────────────────────────────────────────────────────────────────────────┤ │ Issues │ 4.0/CVSS:2.0/AV:N/AC:H/Au:N/C:P/I:P/A:N │ ├─────────────────────┼────────────────────────────────────────────────────────────────────────────────────────────────────┤ │ Edited │ 2021-04-15T09:22:04Z │ ├─────────────────────┼────────────────────────────────────────────────────────────────────────────────────────────────────┤ │ Created │ 2019-05-02T00:00:00.297Z │ ├─────────────────────┼────────────────────────────────────────────────────────────────────────────────────────────────────┤ │ Impact paths │ - │ │ │ /sha256__11533f8a115abc3bbf6840bebe91a8616a0ee04cd4bdad4094ed62e6f86d4432.tar.gz/usr/share/fugu/li │ │ │ b/ch.qos.logback-logback-core-1.2.3.jar │ ├─────────────────────┼────────────────────────────────────────────────────────────────────────────────────────────────────┤ │ │ Affected component ID: gav://ch.qos.logback:logback-core:1.2.3 │ ├─────────────────────┼────────────────────────────────────────────────────────────────────────────────────────────────────┤ │ Vulnerable versions │ 1.0.12 ≤ Version ≤ 1.3.0-alpha5 │ ├─────────────────────┼────────────────────────────────────────────────────────────────────────────────────────────────────┤ │ Fixed versions │ │ └─────────────────────┴────────────────────────────────────────────────────────────────────────────────────────────────────┘

2 2

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

02 Sep '21

Sharing few latest learnings from reproduction attempts. This issue is not getting reproduced in kubectl version 1.16.2 and I am still trying to drill down further to check if it is only kubectl version (from 1.16.3 onwards) causing this problem or there is something else also. Is anyone aware of any workaround apart from restarting the java process ? Thanks, Kedar. On Wed, Aug 25, 2021 at 5:30 PM <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 > (Kedar Sirshikar) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 25 Aug 2021 17:30:00 -0700 > From: Kedar Sirshikar <kedargsirshikar(a)gmail.com> > To: logback-user(a)qos.ch > Subject: Re: [logback-user] logback autoscan is not working > intermittently in k8s pod > Message-ID: > <CAO=cJL+zaL3y+16Z-bNzR_f= > gvDiXPDK94oTN3--bttO6SutbA(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > I already attempted splitting the logback xml configuration file however it > did not help either. After that failure, I initiated this email thread. > > In k8s, this logback functionality needs to be enhanced because log level > will be changed at runtime using CLI exposed from OAM (orchestration and > Administration Management) node and then ConfigMap is responsible to > populate/update the logback config file across all pod replicas so per my > understanding, it is not possible to have the second file > on a path which does not suffer from timestamp glitch. > > > Thanks, > Kedar. > > > On Tue, Aug 24, 2021 at 2:02 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: Abmelden (Carl-Erik Kopseng) > > 2. Re: logback autoscan is not working intermittently in k8s pod > > (Ceki Gülcü) > > > > > > ---------------------------------------------------------------------- > > > > Message: 1 > > Date: Tue, 24 Aug 2021 10:16:31 +0200 > > From: Carl-Erik Kopseng <carlerik(a)diffia.com> > > To: logback users list <logback-user(a)qos.ch> > > Subject: Re: [logback-user] Abmelden > > Message-ID: > > < > > CAAjb5vxiskBqGznv-OvWd6NyFJjuajbYtp42RdqKMSdycFM0tg(a)mail.gmail.com> > > Content-Type: text/plain; charset="utf-8" > > > > You can unsuccessful yourself. The link to manage your subscription is > > present in every email. Press it and scroll down to the unsubscribe > > section. > > > > man. 23. aug. 2021, 17:14 skrev Neda Danilovic <danilovic.neda(a)gmail.com > >: > > > > > Could somebody unsubscribe me from this list? > > > > > > -- > > > Neda Danilović > > > _______________________________________________ > > > logback-user mailing list > > > logback-user(a)qos.ch > > > http://mailman.qos.ch/mailman/listinfo/logback-user > >

1 0

Release Date of 1.2.6?
by s_v_k＠web.de 31 Aug '21

31 Aug '21

Dear all, Release Version 1.3.0-alpha6 includes the fix from logback-1465, but we cannot add an alpha version to our project. Could you share the planned release date of 1.3.0(?), which hopefully also includes the mentioned fix? Many thanks! Best, Sascha

1 0

Release of logback version 1.3.0-alpha10
by Ceki Gülcü 31 Aug '21

31 Aug '21

Hello all, I am happy to announce the release of logback version 1.3.0-alpha10, the best performing logback yet. It requires slf4j-api version 2.0.0-alpha4 or later. For benchmarking figures please see: http://logback.qos.ch/performance.html This version supports the fluent-API introduced in SLF4J 2.0.x. It also supports Jigsaw/Java9 modularization. Joran, logback's configuration system, has been rewritten to use an internal representation model which can be processed separately. Given the breadth of the changes, support for SiftingAppender and Groovy configuration have been dropped temporarily. No new features are available in this version. Future releases will gradually introduce new features made possible by Joran representation model. The 1.3.x series requires Java 8 at runtime. If you wish to build logback from source, you will need Java 9. Please refer to the news page for precise details. http://logback.qos.ch/news.html 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ü

4 5

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

26 Aug '21

I already attempted splitting the logback xml configuration file however it did not help either. After that failure, I initiated this email thread. In k8s, this logback functionality needs to be enhanced because log level will be changed at runtime using CLI exposed from OAM (orchestration and Administration Management) node and then ConfigMap is responsible to populate/update the logback config file across all pod replicas so per my understanding, it is not possible to have the second file on a path which does not suffer from timestamp glitch. Thanks, Kedar. On Tue, Aug 24, 2021 at 2:02 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: Abmelden (Carl-Erik Kopseng) > 2. Re: logback autoscan is not working intermittently in k8s pod > (Ceki Gülcü) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 24 Aug 2021 10:16:31 +0200 > From: Carl-Erik Kopseng <carlerik(a)diffia.com> > To: logback users list <logback-user(a)qos.ch> > Subject: Re: [logback-user] Abmelden > Message-ID: > < > CAAjb5vxiskBqGznv-OvWd6NyFJjuajbYtp42RdqKMSdycFM0tg(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > You can unsuccessful yourself. The link to manage your subscription is > present in every email. Press it and scroll down to the unsubscribe > section. > > man. 23. aug. 2021, 17:14 skrev Neda Danilovic <danilovic.neda(a)gmail.com>: > > > Could somebody unsubscribe me from this list? > > > > -- > > Neda Danilović > > _______________________________________________ > > logback-user mailing list > > logback-user(a)qos.ch > > http://mailman.qos.ch/mailman/listinfo/logback-user >

1 0

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

24 Aug '21

Thank you Raymond for sharing the inputs so looks like this is a bottleneck from logback especially with k8s ConfigMap. Is there any workaround (apart from restarting the java process) to address this issue ? OR I'll have to wait until it gets fixed from logback by considering checksum per below suggestion. Hello Ceki, please share your advice if you have any. Thanks, Kedar. On Fri, Aug 20, 2021 at 7:06 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 > (Raymond Augé) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 20 Aug 2021 10:05:22 -0400 > From: Raymond Augé <raymond.auge(a)liferay.com> > To: logback users list <logback-user(a)qos.ch> > Subject: Re: [logback-user] logback autoscan is not working > intermittently in k8s pod > Message-ID: > < > CAMm6HcC+fKzu4ux-z-WpDQK+LgWt_shwaEvB7OtR3J5dJe-UVQ(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Here's a direct link [1] to the explanation of the issue which I confirmed > myself to be the actual issue I was facing. > > Maybe it will help both the OP and logback :) > > [1] https://blog.arkey.fr/2019/09/13/watchservice-and-bind-mount/ > > > On Fri, Aug 20, 2021 at 10:01 AM Raymond Augé <raymond.auge(a)liferay.com> > wrote: > > > Hi, a long time lurker here 🙂. > > > > So, I suspect the issue is with k8s and it's volumes for config > > maps/secrets symlinks are a pain point in Java. Even inotify based > > WachService cannot handle them. > > > > The issue is that logback is only using a timestamp to detect > > configuration file changes, which is fine as we know in 99% of Java > usages. > > > > However, this doesn't seem to work with the config map volumes supplied > in > > a k8s env because they use symlinks which don't cause the timestamp to > > change, I agree it's weird and unexpected. > > > > However, supplying configuration files via K8s config maps is going to > > start being a much more common use case as time passes. > > > > Logback should probably start including a checksum to detect if the > > contents of the file have changed and use a logical OR with the timestamp > > check so that either changes causes a reload. > > > > FYI, I had to patch a similar issue in Apache Felix Fileinstall due to > the > > same k8s config maps/secrets issue [1] > > > > My 2 cents, > > Ray > > > > [1] https://issues.apache.org/jira/browse/FELIX-6229 > > > > > > On Fri., Aug. 20, 2021, 5:35 a.m. Ceki Gülcü, <ceki(a)qos.ch> wrote: > > > >> 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(a)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(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 > >> > <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. > >> > >

2 1

Abmelden
by Neda Danilovic 24 Aug '21

24 Aug '21

Could somebody unsubscribe me from this list? -- Neda Danilović

2 1

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

20 Aug '21

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 in ConfigurationWatchListUtil is different on both versions. Thanks, Kedar. On Sat, Aug 14, 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, 13 Aug 2021 14:51:09 +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: <f39cbede-6e95-7e60-d01e-ca27599bf453(a)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>> 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>> > > 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>> > > > > > > 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>> 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. 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>> > > To: logback-user(a)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>> > > 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… > >> > > 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. > >

3 3