Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-user@lucene.apache.org
Received-SPF: pass (athena.apache.org: domain of apache@elyograg.org
 designates 166.70.79.219 as permitted sender)
Message-ID: <54C05F53.7040907@elyograg.org>
Date: Wed, 21 Jan 2015 19:24:19 -0700
From: Shawn Heisey <apache@elyograg.org>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64;
 rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: solr-user@lucene.apache.org
Subject: Re: permanently reducing logging levels for Solr
References: 
 <DM2PR0701MB1280BB94F7B06E68067A2FB3E8480@DM2PR0701MB1280.namprd07.prod.outlook.com>
In-Reply-To: 
 <DM2PR0701MB1280BB94F7B06E68067A2FB3E8480@DM2PR0701MB1280.namprd07.prod.outlook.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

On 1/21/2015 1:14 PM, Nemani, Raj wrote:
> How can I reduce the logging levels to SEVERE that survives a Tomcat restart or a machine reboot in Solr.  As you may know, I can change the logging levels from the logging page in admin console but those changes are not persistent across Tomcat server restart or machine reboot.
> Following is the information about the Solr version from Info page in admin console.
>
> Solr Specification Version: 3.2.0
> Solr Implementation Version: 3.2.0 1129474 - rmuir - 2011-05-30 23:07:15
> Lucene Specification Version: 3.2.0
> Lucene Implementation Version: 3.2.0 1129474 - 2011-05-30 23:08:57
>
> Please let me know if there is any other information that you may need.
>
> Thank you in advance for your help

The Solr 3.x example uses java.util.logging, not the log4j that was
introduced in the example for 4.3.0.  Your other reply talks about
log4j, which may not be the right framework for your install.

I have no way to know what container or logging framework you're using. 
You will need to create a configuration file for whatever slf4j binding
is in use on your install and most likely add a system property to your
java commandline for startup so that your logging config gets used.  If
you're using java.util.logging, look for help with the
java.util.logging.config.file system property.

FYI -- if you reduce the logging level to WARN, a normally functioning
Solr will log almost nothing, and you'll be able to see ERROR and WARN
messages, which is extremely important for troubleshooting.  Dropping
the level to SEVERE is not necessary, and will make it impossible to
tell what happened when something goes wrong.

Thanks,
Shawn