Return-Path: X-Original-To: apmail-logging-log4j-user-archive@www.apache.org Delivered-To: apmail-logging-log4j-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D2DB417210 for ; Wed, 25 Mar 2015 13:59:53 +0000 (UTC) Received: (qmail 19894 invoked by uid 500); 25 Mar 2015 13:59:53 -0000 Delivered-To: apmail-logging-log4j-user-archive@logging.apache.org Received: (qmail 19839 invoked by uid 500); 25 Mar 2015 13:59:53 -0000 Mailing-List: contact log4j-user-help@logging.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Log4J Users List" Reply-To: "Log4J Users List" Delivered-To: mailing list log4j-user@logging.apache.org Received: (qmail 19821 invoked by uid 99); 25 Mar 2015 13:59:53 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Mar 2015 13:59:53 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of remko.popma@gmail.com designates 209.85.218.47 as permitted sender) Received: from [209.85.218.47] (HELO mail-oi0-f47.google.com) (209.85.218.47) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Mar 2015 13:59:47 +0000 Received: by oiag65 with SMTP id g65so21802888oia.2 for ; Wed, 25 Mar 2015 06:57:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=nJNDWnzziXPg2R0FFeMhlRTfbHBlnR0MS94G5VP3q50=; b=ocmmUs2glJKj9igog9dWsX4I4q86ZEzemDWFmMDNwwCv9YDA32trq/fojZQiTwlPvg A5v2JsZ6ZNBMQb8/ARj2zD1ExsdMwsr1xRqxTQrH+fnQj8xonLYST5QK+Fnz2aq2wTZu a0Xm2gYKASCt2dcLGCr858dngTqEA+mWIrFcbycWPKSAEn7N7abCeMl/BDFE4UOhU8Do Y9xt1UbfKvedbI3BbolokYJGs6xDltqTjngEMaq50O/+88xDdY/tR9BhQAQi/56UCjoU x3p0Ge9wltL5WTsXNbYbMel2LyTmoWb75M7MpyBSgxLNkeFmlnP/Jh2uIu5VulAmOsGE WWQA== MIME-Version: 1.0 X-Received: by 10.202.7.1 with SMTP id 1mr7207503oih.16.1427291877321; Wed, 25 Mar 2015 06:57:57 -0700 (PDT) Received: by 10.182.79.38 with HTTP; Wed, 25 Mar 2015 06:57:57 -0700 (PDT) In-Reply-To: References: <17D35F66-5FA1-4AAB-9179-CD7512F3BAE8@gmail.com> Date: Wed, 25 Mar 2015 22:57:57 +0900 Message-ID: Subject: Re: Intermittent log file compression issue From: Remko Popma To: Log4J Users List Content-Type: multipart/alternative; boundary=001a113d19d656b02b05121d49ea X-Virus-Checked: Checked by ClamAV on apache.org --001a113d19d656b02b05121d49ea Content-Type: text/plain; charset=UTF-8 Great! Glad to hear that the problem is resolved. -Remko On Wed, Mar 25, 2015 at 10:30 PM, Richard Kolb wrote: > Hi Remko, > > Seems I found the issue. > > I have two Web apps in the same container that use the same log4j2.xml and > they are in different class loaders. > I misread the docs and assumed it would work. > > I am guessing there is a race condition where the one application is > writing while the other tries to archive. > > Does that make sense? > > Regards, > Richard. > On 25 Mar 2015 12:39, "Richard Kolb" wrote: > > > Hi Remko. > > > > Another symptom is that the log files are not cleared on the daily > > archive. > > > > I.e I started the server on Friday morning and it logs to audit.log and > it > > archives daily. > > The audit.log file now contains all the logs since Friday and it not > > cleared. > > The archived logs also contain all the logs to the point they were > > archived. > > > > Regards, > > Richard. > > On 25 Mar 2015 09:20, "Richard Kolb" wrote: > > > >> Hi Remko > >> > >> On 25 March 2015 at 04:21, Remko Popma wrote: > >> > >>> So, if you specify the config location with system property > >>> "log4j.configurationFile" then old log files are compressed correctly > on > >>> rollover, correct? > >>> > >> > >> Correct. > >> I specify with the parameter > -Dlog4j.configurationFile=file:../log4j2.xml > >> When I did my tests on the command line I specified an absolute path to > >> log4j2.xml > >> > >> See the attached screen shot of the logs that got archived and then > >> suddenly not. > >> I specified the log paths and gzip paths as an absolute directory. > >> > >> 1) This file got gzipped : > >> > >> *2015-03-25 08:55:37,315 DEBUG RollingFileManager executing > >> synchronous FileRenameAction[C:\usr\local\applications\work* > *-api\domain\work-api\logs\audit.log > >> to > C:\usr\local\applications\work-api\domain\work-api\logs\2015-03\aud* > *it-2015-03-25_08_54-1.log, > >> renameEmptyFiles=false]* *2015-03-25 08:55:37,315 DEBUG > >> RollingFileManager executing async > >> GzCompressAction[C:\usr\local\applications\work-api* > *\domain\work-api\logs\2015-03\audit-2015-03-25_08_54-1.log > >> to C:\usr\local\applications\work-api\domain\work* > *-api\logs\2015-03\audit-2015-03-25_08_54-1.log.gz, > >> deleteSource=true]* > >> > >> 2) This one did the move but not the gzip > >> > >> *2015-03-25 08:56:05,817 TRACE PatternProcessor.getNextTime returning > >> 2015/03/25-08:57:00.000, nextFileTime=2015/03/25-08* *:56:00.000, > >> prevFileTime=2015/03/25-08:55:00.000, current=2015/03/25-08:56:05.817, > >> freq=EVERY_MINUTE* *2015-03-25 08:56:05,832 TRACE > >> DefaultRolloverStrategy.purge() took 0.004088928 seconds* *2015-03-25 > >> 08:56:05,832 DEBUG RollingFileManager executing synchronous > >> FileRenameAction[C:\usr\local\applications\work* > *-api\domain\work-api\logs\audit.log > >> to > C:\usr\local\applications\work-api\domain\work-api\logs\2015-03\aud* > *it-2015-03-25_08_55-1.log, > >> renameEmptyFiles=false]* > >> It seems the GzCompressAction log never comes up. > >> > >> > >> > >>> If you include the config file in your application jar and rely on the > >>> classpath then what happens? Is rollover the only thing that breaks? > >>> > >> > >> I have not tried this yet. I will do that now. > >> > >> > >>> > >>> In the latter case, have you tried an absolute path? > >>> (You can use an env: or sys: lookup to make the absolute path prefix > >>> configurable, for example > >>> > filePath="${sys:logdir}/$${date:yyyy-MM}/fault-%d{yyyy-MM-dd_hh_mm}-%i.log.gz" > >>> where the value of system property "logdir" is an absolute path.) > >>> > >> > >> Thanks, yes I did this in the above tests. > >> > >> regards, > >> Richard. > >> > >> > >> > >>> > >>> Sent from my iPhone > >>> > >>> > On 2015/03/24, at 23:42, Richard Kolb wrote: > >>> > > >>> > Hi Remko, > >>> > > >>> > Thanks, very much. > >>> > Changing FilePattern to filePattern did not solve the issue. > >>> > The * was an typeo in the email, sorry for that. > >>> > > >>> > I am still experiencing the same issue inside the container and I > can't > >>> > recreate the issue with the same log4j2.xml outside the container. > >>> > > >>> > Next step is to check the log4j2 fine logs and I will report back. > >>> > > >>> > Regards, > >>> > Richard. > >>> > Can you try filePattern with a lower-case 'f' and remove the '*' > >>> characters > >>> > from the filePattern path? > >>> > > >>> > For example: > >>> >> FilePattern=" > >>> >> *logs/$${date:yyyy-MM}/fault-%d{yyyy-MM-dd_hh_mm}-%i.log.gz*" > >>> > > >>> > > >>> > Should be > >>> >> filePattern=" > >>> >> logs/$${date:yyyy-MM}/fault-%d{yyyy-MM-dd_hh_mm}-%i.log.gz" > >>> > > >>> > > >>> > Regards, > >>> > Remko > >>> > > >>> > Sent from my iPhone > >>> > > >>> >> On 2015/03/24, at 17:12, Richard Kolb wrote: > >>> >> > >>> >> Hello, > >>> >> > >>> >> I am using log4j 2.2 on Windows 2008 using Java 7 and I'm > >>> experiencing an > >>> >> intermittent issue where my log files used to compress, but now just > >>> move > >>> >> to the archive directory uncompressed. > >>> >> > >>> >> To debug, I changed the file pattern to be on the minute level (in > >>> bold), > >>> >> and I am getting the same issue > >>> >> > >>> >> Any help would be greatly be appreciated.. > >>> >> > >>> >> thanks, > >>> >> Richard. > >>> >> > >>> >> > >>> >> >>> > monitorInterval="30"> > >>> >> > >>> >> >>> >> immediateFlush="false" append="true" > >>> >> FilePattern="logs/$${date:yyyy-MM}/all-%d{yyyy-MM-dd}-%i.log.gz"> > >>> >> > >>> >> %d %m%n > >>> >> > >>> >> > >>> >> modulate="true" > >>> /> > >>> >> > >>> >> > >>> >> > >>> >> > >>> >> >>> >> immediateFlush="false" append="true" > >>> >> > >>> > FilePattern="logs/$${date:yyyy-MM}/audit-%d{yyyy-MM-dd_hh_mm}-%i.log.gz"> > >>> >> > >>> >> %d %m%n > >>> >> > >>> >> > >>> >> modulate="true" > >>> /> > >>> >> > >>> >> > >>> >> > >>> >> > >>> >> >>> >> immediateFlush="false" append="true" FilePattern=" > >>> >> *logs/$${date:yyyy-MM}/fault-%d{yyyy-MM-dd_hh_mm}-%i.log.gz*"> > >>> >> > >>> >> %d %m%n > >>> >> > >>> >> > >>> >> modulate="true" > >>> /> > >>> >> > >>> >> > >>> >> > >>> >> > >>> >> > >>> >> > >>> >> >>> >> fileName="logs/webservices.log" immediateFlush="false" append="true" > >>> >> FilePattern=" > >>> >> *logs/$${date:yyyy-MM}/webservices-%d{yyyy-MM-dd_hh_mm}-%i.log.gz*"> > >>> >> > >>> >> %d %m%n > >>> >> > >>> >> > >>> >> modulate="true" > >>> /> > >>> >> > >>> >> > >>> >> > >>> >> > >>> >> > >>> >> > >>> >> > >>> >> > >>> >> > >>> >> > >>> >> > >>> >> > >>> >> > >>> >> > >>> >> > >>> >> > >>> >> > >>> >> > >>> >> > >>> >> > >>> >> > >>> >> > >>> >> > >>> > > >>> > --------------------------------------------------------------------- > >>> > To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org > >>> > For additional commands, e-mail: log4j-user-help@logging.apache.org > >>> > >>> --------------------------------------------------------------------- > >>> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org > >>> For additional commands, e-mail: log4j-user-help@logging.apache.org > >>> > >>> > >> > --001a113d19d656b02b05121d49ea--