Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 006EF200C28 for ; Mon, 13 Mar 2017 19:07:10 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id F30B8160B6C; Mon, 13 Mar 2017 18:07:09 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 252BF160B5D for ; Mon, 13 Mar 2017 19:07:08 +0100 (CET) Received: (qmail 92527 invoked by uid 500); 13 Mar 2017 18:07:07 -0000 Mailing-List: contact user-help@manifoldcf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@manifoldcf.apache.org Delivered-To: mailing list user@manifoldcf.apache.org Received: (qmail 92517 invoked by uid 99); 13 Mar 2017 18:07:07 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 Mar 2017 18:07:07 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id DD996182758 for ; Mon, 13 Mar 2017 18:07:06 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.998 X-Spam-Level: ** X-Spam-Status: No, score=2.998 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=2, KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_PASS=-0.001] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id Zk_SOfoNQvIX for ; Mon, 13 Mar 2017 18:07:05 +0000 (UTC) Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.143]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id C4F4E618A4 for ; Mon, 13 Mar 2017 18:07:04 +0000 (UTC) Received: from [85.158.136.83] by server-7.bemta-5.messagelabs.com id CE/42-24850-0CFD6C85; Mon, 13 Mar 2017 18:06:56 +0000 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrNIsWRWlGSWpSXmKPExsViZ8MxVXf//WM RBn8mGVk82/2X3YHR4+D/jADGKNbMvKT8igTWjIOXZAo26VU8aNrM3MC4RbOLkZNDSOACo8SE NUVdjFxA9iNGiamnbzNDONcYJS7cmc8OUsUmoCdxYu1mMFtEwFbizapTjCC2sICJxP2fGxgh4 pYSn6c9hqrRk/jx4DILiM0ioCox484Zti5Gdg5egUCJ7lSQKKOArMSXxtXMIDazgLjErSfzmU BsCQEBiSV7zjND2KISLx//Y4WwDSS2Lt3HAmErSrSvW80C0Zsnce88yHROoOmCEidnPmGZwCg 0C8nYWUjKZiEpg4jrSCzY/YkNwtaWWLbwNTOMfebAYyZk8QWM7KsYNYpTi8pSi3SNjPWSijLT M0pyEzNzdA0NTPVyU4uLE9NTcxKTivWS83M3MQIjpZ6BgXEH4452v0OMkhxMSqK8v48cixDiS 8pPqcxILM6ILyrNSS0+xCjDwaEkwZt8DygnWJSanlqRlpkDjFmYtAQHj5II73yQNG9xQWJucW Y6ROoUo6KUOK8sSEIAJJFRmgfXBksTlxhlpYR5GRkYGIR4ClKLcjNLUOVfMYpzMCoJ8/69CzS FJzOvBG76K6DFTECLE38eAVlckoiQkmpgrN6z9gPTY5tp9xL8l81OEAud3dLifOwAi5mmsEjE AX21p611RT+mhr+SP3AqpKG1VyRmx6QXl8SPCQXPy876IW7//sR5dQmXgB2fPyfeC015eLr10 8XtSd82aG3dobM96/ok70V3m5zLslf6ux/R/2+rcaXnYH7cmQ8t+w86r5y4zOP04wOpz5RYij MSDbWYi4oTAYaTHHcOAwAA X-Env-Sender: Guy.Standen@uk.fujitsu.com X-Msg-Ref: server-13.tower-36.messagelabs.com!1489428415!91966775!1 X-Originating-IP: [62.60.8.149] X-StarScan-Received: X-StarScan-Version: 9.2.3; banners=uk.fujitsu.com,-,- X-VirusChecked: Checked Received: (qmail 29122 invoked from network); 13 Mar 2017 18:06:55 -0000 Received: from unknown (HELO mailhost2.uk.fujitsu.com) (62.60.8.149) by server-13.tower-36.messagelabs.com with DHE-RSA-AES256-GCM-SHA384 encrypted SMTP; 13 Mar 2017 18:06:55 -0000 Received: from FJDUKEX04.fjdefence.fs.fujitsu.com ([145.227.169.137]) by mailhost2.uk.fujitsu.com (8.14.5/8.14.5) with ESMTP id v2DI6Roq018167 for ; Mon, 13 Mar 2017 18:06:47 GMT Received: from FJDUKEX04.fjdefence.fs.fujitsu.com (2002:91e3:a9ed::91e3:a9ed) by FJDUKEX04.fjdefence.fs.fujitsu.com (2002:91e3:a9ed::91e3:a9ed) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 13 Mar 2017 18:06:29 +0000 Received: from FJDUKEX04.fjdefence.fs.fujitsu.com ([fe80::9584:6310:44d0:3163]) by FJDUKEX04.fjdefence.fs.fujitsu.com ([fe80::9584:6310:44d0:3163%15]) with mapi id 15.00.1210.000; Mon, 13 Mar 2017 18:06:29 +0000 From: Standen Guy To: "user@manifoldcf.apache.org" Subject: ManifoldCF WebApps and Agents log4j logging Thread-Topic: ManifoldCF WebApps and Agents log4j logging Thread-Index: AdKcIZ4uX8pT2JoyRJy5nUtzIXhtOA== Date: Mon, 13 Mar 2017 18:06:29 +0000 Message-ID: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [172.30.77.145] Content-Type: multipart/alternative; boundary="_000_d104b059957e4dcd95279d58a03dc41aFJDUKEX04fjdefencefsfuj_" MIME-Version: 1.0 archived-at: Mon, 13 Mar 2017 18:07:10 -0000 --_000_d104b059957e4dcd95279d58a03dc41aFJDUKEX04fjdefencefsfuj_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi All, I wonder if anyone has any experience with getting logging= to roll the MCF log file when both Agents and WebApps are running togethe= r. I'm running MCF 2.6 on Windows. I set up logging.ini to log to a rolling file appender with a maximum file= size and maximum number of retained files configured as shown: "log4j.appender.MAIN.File=3Dlogs/manifoldcf.log log4j.rootLogger=3DWARN, MAIN log4j.appender.MAIN=3Dorg.apache.log4j.RollingFileAppender log4j.appender.MAIN.layout=3Dorg.apache.log4j.PatternLayout log4j.appender.MAIN.layout.ConversionPattern=3D%5p %d{ISO8601} (%t) - %m%n= log4j.appender.MAIN.MaxBackupIndex=3D5 log4j.appender.MAIN.MaxFileSize=3D100KB" If I run JUST the Agents process then logging runs exactly as I expected (= multiple files get created and rolled as expected) If I Run the MCF WebApps process as well, then the file size limit and num= ber of backup files is ignored. I end up with one large log file that does= not split or roll. It looks like the WebApps is using some fixed configuration for the log4J= properties that is overriding the ones in logging.ini. and affecting = how MCF Agents logs as well Does anyone know how to get the logging for both WebApps and Agents to rol= l, or how to separate the WebApps and Agents log files so that Agents can = have a rolling logger? Any advice appreciated. Guy Unless otherwise stated, this email has been sent from Fujitsu Services Li= mited (registered in England No 96056); Fujitsu EMEA PLC (registered in En= gland No 2216100) both with registered offices at: 22 Baker Street, London= W1U 3BW; PFU (EMEA) Limited, (registered in England No 1578652) and Fuji= tsu Laboratories of Europe Limited (registered in England No. 4153469) bot= h with registered offices at: Hayes Park Central, Hayes End Road, Hayes, M= iddlesex, UB4 8FE.=20 This email is only for the use of its intended recipient. Its contents are= subject to a duty of confidence and may be privileged. Fujitsu does not g= uarantee that this email has not been intercepted and amended or that it i= s virus-free. --_000_d104b059957e4dcd95279d58a03dc41aFJDUKEX04fjdefencefsfuj_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi All,

        &nb= sp;       I wonder if anyone has any experie= nce with getting logging to roll the MCF log file when both Agents and Web= Apps are running together.

I’m running MCF 2.6 on Windows.

I set up logging.ini to log to a rolling file appen= der with a maximum file size and maximum number of retained files configur= ed as shown:

 

“log4j.appender.MAIN.File=3Dlogs/manifoldcf.l= og

log4j.rootLogger=3DWARN, MAIN

log4j.appender.MAIN=3Dorg.apache.log4j.RollingFileA= ppender

log4j.appender.MAIN.layout=3Dorg.apache.log4j.Patte= rnLayout

log4j.appender.MAIN.layout.ConversionPattern=3D%5p = %d{ISO8601} (%t) - %m%n

log4j.appender.MAIN.MaxBackupIndex=3D5

log4j.appender.MAIN.MaxFileSize=3D100KB”=

 

If I run JUST the Agents process then logging runs = exactly as I expected (multiple files get created and rolled as expected)<= o:p>

 

If I Run the MCF WebApps process as well, then the = file size limit and number of backup files is ignored. I end up with one l= arge log file that does not split or roll.

 

It looks like the WebApps  is using some fixed= configuration for the log4J  properties  that is overriding the=   ones in  logging.ini. and affecting how MCF Agents logs as wel= l

 

Does anyone know how to get the logging for both We= bApps and Agents to roll, or how to separate the WebApps and Agents log fi= les so that Agents can have a rolling logger?

 

Any advice appreciated.

 

Guy

 


Unless otherwise stated, this email has been sent from Fujitsu Services Li= mited (registered in England No 96056); Fujitsu EMEA PLC (registered in En= gland No 2216100) both with registered offices at: 22 Baker Street, London= W1U 3BW; PFU (EMEA) Limited, (registered in England No 1578652) and Fuji= tsu Laboratories of Europe Limited (registered in England No. 4153469) bot= h with registered offices at: Hayes Park Central, Hayes End Road, Hayes, M= iddlesex, UB4 8FE.
This email is only for the use of its intended recipient. Its contents are= subject to a duty of confidence and may be privileged. Fujitsu does not g= uarantee that this email has not been intercepted and amended or that it i= s virus-free.
--_000_d104b059957e4dcd95279d58a03dc41aFJDUKEX04fjdefencefsfuj_--