# Logging setup

**URL:** <https://discuss.elastic.co/t/logging-setup/8775>\
**Category:** Elasticsearch\
**Created:** [August 17, 2012, 7:08pm UTC](https://discuss.elastic.co/t/logging-setup/8775 "2012-08-17T19:08:55Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ivan](https://avatars.discourse-cdn.com/v4/letter/i/df788c/32.png) [@Ivan](https://discuss.elastic.co/u/Ivan)\
**Post date:** [August 17, 2012, 7:08pm UTC](https://discuss.elastic.co/t/logging-setup/8775/1 "2012-08-17T19:08:55Z")

</div>

I rarely look into my ElasticSearch server logs, but when trying to  
debug a current issue (JVM crashes), I noticed that I have not been  
looking in a while.

The wrapper is properly logging. In fact, those logs complain about  
log4j not being setup:  
INFO | jvm 1 | 2012/08/17 11:33:09 | log4j:WARN No appenders  
could be found for logger (node).  
INFO | jvm 1 | 2012/08/17 11:33:09 | log4j:WARN Please initialize  
the log4j system properly.  
INFO | jvm 1 | 2012/08/17 11:33:09 | log4j:WARN See  
[http://logging.apache.org/log4j/1.2/faq.html#noconfig](http://logging.apache.org/log4j/1.2/faq.html#noconfig) for

Is logging.xml the file used for logging? I never had an issue before.  
I am using the service wrapper, so I added the xml file to my  
classpath. Here are some settings from my elasticsearch.conf file:

wrapper.java.classpath.4=/shared/elasticsearch-config/config/logging.xml  
wrapper.java.additional.13=-Des.path.conf=/shared/elasticsearch-config/config/

The java process starts up with the correct classpath, but log4j still  
complains. Not sure at what point I lost logging.

Cheers,

Ivan

--

---

<div class="post-metadata">

**Author:** ![Logan\_Hardy](https://avatars.discourse-cdn.com/v4/letter/l/ecae2f/32.png) [@Logan\_Hardy](https://discuss.elastic.co/u/Logan_Hardy)\
**Post date:** [August 19, 2012, 6:11pm UTC](https://discuss.elastic.co/t/logging-setup/8775/2 "2012-08-19T18:11:51Z")

</div>

Ivan,  
I'm running elasticsearch-0.19.8 and It's using "config/logging.yml" not  
.xml. There is no reference to it all in elasticsearch.conf.

Logan

On Friday, August 17, 2012 1:08:55 PM UTC-6, Ivan Brusic wrote:

> I rarely look into my Elasticsearch server logs, but when trying to  
> debug a current issue (JVM crashes), I noticed that I have not been  
> looking in a while.
> 
> The wrapper is properly logging. In fact, those logs complain about  
> log4j not being setup:  
> INFO | jvm 1 | 2012/08/17 11:33:09 | log4j:WARN No appenders  
> could be found for logger (node).  
> INFO | jvm 1 | 2012/08/17 11:33:09 | log4j:WARN Please initialize  
> the log4j system properly.  
> INFO | jvm 1 | 2012/08/17 11:33:09 | log4j:WARN See  
> [Apache log4j 1.2 - Frequently Asked Technical Questions](http://logging.apache.org/log4j/1.2/faq.html#noconfig) for
> 
> Is logging.xml the file used for logging? I never had an issue before.  
> I am using the service wrapper, so I added the xml file to my  
> classpath. Here are some settings from my elasticsearch.conf file:
> 
> wrapper.java.classpath.4=/shared/elasticsearch-config/config/logging.xml  
> wrapper.java.additional.13=-Des.path.conf=/shared/elasticsearch-config/config/
> 
> The java process starts up with the correct classpath, but log4j still  
> complains. Not sure at what point I lost logging.
> 
> Cheers,
> 
> Ivan

--

---

<div class="post-metadata">

**Author:** ![Ivan](https://avatars.discourse-cdn.com/v4/letter/i/df788c/32.png) [@Ivan](https://discuss.elastic.co/u/Ivan)\
**Post date:** [August 22, 2012, 6:02am UTC](https://discuss.elastic.co/t/logging-setup/8775/3 "2012-08-22T06:02:36Z")

</div>

Yup, that was it. Fat-fingered typing on my part. No wonder logging  
stopped at some point. So many years of typing .xml that I did not  
even spot the error. Thanks.

--  
Ivan

On Sun, Aug 19, 2012 at 11:11 AM, Logan Hardy [logan@tynt.com](mailto:logan@tynt.com) wrote:

> Ivan,  
> I'm running elasticsearch-0.19.8 and It's using "config/logging.yml" not  
> .xml. There is no reference to it all in elasticsearch.conf.
> 
> Logan
> 
> On Friday, August 17, 2012 1:08:55 PM UTC-6, Ivan Brusic wrote:
> 
> > I rarely look into my Elasticsearch server logs, but when trying to  
> > debug a current issue (JVM crashes), I noticed that I have not been  
> > looking in a while.
> > 
> > The wrapper is properly logging. In fact, those logs complain about  
> > log4j not being setup:  
> > INFO | jvm 1 | 2012/08/17 11:33:09 | log4j:WARN No appenders  
> > could be found for logger (node).  
> > INFO | jvm 1 | 2012/08/17 11:33:09 | log4j:WARN Please initialize  
> > the log4j system properly.  
> > INFO | jvm 1 | 2012/08/17 11:33:09 | log4j:WARN See  
> > [Apache log4j 1.2 - Frequently Asked Technical Questions](http://logging.apache.org/log4j/1.2/faq.html#noconfig) for
> > 
> > Is logging.xml the file used for logging? I never had an issue before.  
> > I am using the service wrapper, so I added the xml file to my  
> > classpath. Here are some settings from my elasticsearch.conf file:
> > 
> > wrapper.java.classpath.4=/shared/elasticsearch-config/config/logging.xml
> > 
> > wrapper.java.additional.13=-Des.path.conf=/shared/elasticsearch-config/config/
> > 
> > The java process starts up with the correct classpath, but log4j still  
> > complains. Not sure at what point I lost logging.
> > 
> > Cheers,
> > 
> > Ivan
> 
> --

--

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 3:15am UTC](https://discuss.elastic.co/t/logging-setup/8775/4 "2017-07-06T03:15:32Z")

</div>


