Return-Path: X-Original-To: apmail-storm-user-archive@minotaur.apache.org Delivered-To: apmail-storm-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 000B011918 for ; Sat, 5 Apr 2014 15:12:47 +0000 (UTC) Received: (qmail 90178 invoked by uid 500); 5 Apr 2014 15:12:46 -0000 Delivered-To: apmail-storm-user-archive@storm.apache.org Received: (qmail 89955 invoked by uid 500); 5 Apr 2014 15:12:45 -0000 Mailing-List: contact user-help@storm.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@storm.incubator.apache.org Delivered-To: mailing list user@storm.incubator.apache.org Received: (qmail 89946 invoked by uid 99); 5 Apr 2014 15:12:42 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 05 Apr 2014 15:12:42 +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 raymond.poling@citi.com designates 67.231.153.94 as permitted sender) Received: from [67.231.153.94] (HELO mx0b-00123c01.pphosted.com) (67.231.153.94) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 05 Apr 2014 15:12:34 +0000 Received: from pps.filterd (m0008248 [127.0.0.1]) by mx0b-00123c02.pphosted.com (8.14.5/8.14.5) with SMTP id s35FA860031780 for ; Sat, 5 Apr 2014 15:12:13 GMT Received: from mail.citigroup.com (smtpoutbound.citigroup.com [192.193.222.17]) by mx0b-00123c02.pphosted.com with ESMTP id 1jr69b5vqh-1 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT) for ; Sat, 05 Apr 2014 15:12:13 +0000 Received: from imbhub-sw34.nam.nsroot.net (namdlpdimpmw07.nam.nsroot.net [169.193.148.107]) by smtpinbound.citigroup.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id s35FBh3v027923 for ; Sat, 5 Apr 2014 15:12:12 GMT Received: from EXTXIHT04.nam.nsroot.net (EXTXIHT04.nam.nsroot.net [169.177.87.31]) by imbhub-sw34.nam.nsroot.net (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id s35FCAPV030853 for ; Sat, 5 Apr 2014 15:12:10 GMT Received: from EXTXHT06.nam.nsroot.net (169.177.87.43) by EXTXIHT04.nam.nsroot.net (169.177.87.31) with Microsoft SMTP Server (TLS) id 14.3.174.1; Sat, 5 Apr 2014 10:12:10 -0500 Received: from EXTXMB21.nam.nsroot.net ([169.177.87.26]) by EXTXHT06.nam.nsroot.net ([169.177.87.43]) with mapi id 14.03.0174.001; Sat, 5 Apr 2014 10:12:09 -0500 From: "Poling, Raymond " To: "'user@storm.incubator.apache.org'" Subject: RE: Logging issues in Storm Thread-Topic: Logging issues in Storm Thread-Index: AQHPUNB4Sqs0uy3ZdEW9OwbspTKtt5sDINRQ Date: Sat, 5 Apr 2014 15:12:09 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [169.177.87.250] Content-Type: multipart/alternative; boundary="_000_FC0B269FDD2F7A47876B7AAAB6690BA72993FE2BEXTXMB21namnsro_" MIME-Version: 1.0 X-CFilter-Loop: Reflected X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.11.87,1.0.14,0.0.0000 definitions=2014-04-05_01:2014-04-04,2014-04-05,1970-01-01 signatures=0 X-Virus-Checked: Checked by ClamAV on apache.org --_000_FC0B269FDD2F7A47876B7AAAB6690BA72993FE2BEXTXMB21namnsro_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Try looking under $STORM_HOME/logs/worker-SLOT.log for the worker that is r= unning your code. SL4j and log4j get bridged back to Storm's native logback= logger. From: Kashyap Mhaisekar [mailto:kashyap.m@gmail.com] Sent: Saturday, April 05, 2014 9:10 AM To: user@storm.incubator.apache.org Subject: Logging issues in Storm Hi, For making Log4j logs to work in storm, what needs to be done? I have used both Slf4j and Log4j directly and it works when executed as a s= tandalone java program (Logs get printed where they need to). However, the = moment I submit cluster (StormSubmitter) or LocalCluster, the logs dont app= ear. Even Sysouts dont get printed. I see some of the sysouts in Supervisor.log = but the sysouts from spouts and bolts are not there anywhere. I came across cluster.xml under .../storm/logback which seems to indicate a= ll loggers should be configured here? Any ideas on what I might be missing? Regards, Kashyap --_000_FC0B269FDD2F7A47876B7AAAB6690BA72993FE2BEXTXMB21namnsro_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Try looking under $STORM_= HOME/logs/worker-SLOT.log for the worker that is running your code. SL4j an= d log4j get bridged back to Storm’s native logback logger.=

 <= /p>

From: Kashyap = Mhaisekar [mailto:kashyap.m@gmail.com]
Sent: Saturday, April 05, 2014 9:10 AM
To: user@storm.incubator.apache.org
Subject: Logging issues in Storm

 

Hi,

For making Log4j logs to work in storm, what needs t= o be done?

I have used both Slf4j and Log4j directly and it wor= ks when executed as a standalone java program (Logs get printed where they = need to). However, the moment I submit cluster (StormSubmitter) or LocalClu= ster, the logs dont appear.

 

Even Sysouts dont get printed. I see some of the sys= outs in Supervisor.log but the sysouts from spouts and bolts are not there = anywhere.

 

I came across cluster.xml under .../storm/logback wh= ich seems to indicate all loggers should be configured here?

 

Any ideas on what I might be missing?

 

Regards,

Kashyap

--_000_FC0B269FDD2F7A47876B7AAAB6690BA72993FE2BEXTXMB21namnsro_--