# log4j:WARN No appenders could be found for logger (node) **URL:** \ **Category:** Elasticsearch\ **Created:** [May 9, 2013, 9:04pm UTC](https://discuss.elastic.co/t/log4j-warn-no-appenders-could-be-found-for-logger-node/11907 "2013-05-09T21:04:43Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![the\_nozzle](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/the_nozzle/32/1935_2.png) [@the\_nozzle](https://discuss.elastic.co/u/the_nozzle)\ **Post date:** [May 9, 2013, 9:04pm UTC](https://discuss.elastic.co/t/log4j-warn-no-appenders-could-be-found-for-logger-node/11907/1 "2013-05-09T21:04:43Z")
Hey everyone Started to get that warning after upgrading to 0.9. Tried the usual configuration options to no avail (config pasted below). Any help would be appreciated.. To make sure that the paths are set I uncommented all the environment variables pertaining to logging and config paths .. cat /etc/sysconfig/elasticsearch ES\_PATH\_LOG=/var/log/elasticsearch ES\_PATH\_DATA=/var/lib/elasticsearch ES\_PATH\_WORK=/tmp/elasticsearch ES\_PATH\_CONF=/etc/elasticsearch ES\_CONFIG=/etc/elasticsearch/elasticsearch.yml ES\_INCLUDE=/usr/share/elasticsearch/bin/elasticsearch.in.sh ES\_MIN\_MEM=12g ES\_MAX\_MEM=12g logging.yml: rootLogger: INFO, file logger: # log action execution errors for easier debugging action: DEBUG # reduce the logging for aws, too much is logged under the default INFO com.amazonaws: WARN # gateway #gateway: DEBUG #index.gateway: DEBUG # peer shard recovery #index.shard.recovery: DEBUG # discovery #discovery: TRACE appender: file: type: file file: ${path.logs}/${cluster.name}.log layout: type: pattern conversionPattern: "[%d{ISO8601}][%-5p][%-25c] %m%n" and also added /etc/elasticsearch/elasticsearch.yml path.conf: /etc/elasticsearch path.data: /var/lib/elasticsearch path.work: /tmp/elasticsearch path.logs: /var/log/elasticsearch This setup was working fine with 0.19.2 .. So I am not sure what changed and where. Could this be some odd java class path loading issue ? Once again - thanks for any help. -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![the\_nozzle](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/the_nozzle/32/1935_2.png) [@the\_nozzle](https://discuss.elastic.co/u/the_nozzle)\ **Post date:** [May 9, 2013, 9:06pm UTC](https://discuss.elastic.co/t/log4j-warn-no-appenders-could-be-found-for-logger-node/11907/2 "2013-05-09T21:06:13Z")
Forgot to add - java version "1.7.0\_21" Java(TM) SE Runtime Environment (build 1.7.0\_21-b11) Java HotSpot(TM) 64-Bit Server VM (build 23.21-b01, mixed mode) on centos 5.5 On Thursday, May 9, 2013 2:04:43 PM UTC-7, the\_nozzle wrote: > Hey everyone > > Started to get that warning after upgrading to 0.9. Tried the usual > configuration options to no avail (config pasted below). Any help would be > appreciated.. > To make sure that the paths are set I uncommented all the environment > variables pertaining to logging and config paths .. > > cat /etc/sysconfig/elasticsearch > ES\_PATH\_LOG=/var/log/elasticsearch > ES\_PATH\_DATA=/var/lib/elasticsearch > ES\_PATH\_WORK=/tmp/elasticsearch > ES\_PATH\_CONF=/etc/elasticsearch > ES\_CONFIG=/etc/elasticsearch/elasticsearch.yml > > ES\_INCLUDE=/usr/share/elasticsearch/bin/elasticsearch.in.sh > > ES\_MIN\_MEM=12g > > ES\_MAX\_MEM=12g > > logging.yml: > > rootLogger: INFO, file > logger: > > # log action execution errors for easier debugging > > action: DEBUG > > # reduce the logging for aws, too much is logged under the default INFO > > com.amazonaws: WARN > > # gateway > > #gateway: DEBUG > #index.gateway: DEBUG > > # peer shard recovery > > #index.shard.recovery: DEBUG > > # discovery > > #discovery: TRACE > > appender: > file: > type: file > file: ${path.logs}/${cluster.name}.log > layout: > type: pattern > conversionPattern: "[%d{ISO8601}][%-5p][%-25c] %m%n" > > and also added /etc/elasticsearch/elasticsearch.yml > path.conf: /etc/elasticsearch > path.data: /var/lib/elasticsearch > path.work: /tmp/elasticsearch > path.logs: /var/log/elasticsearch > > This setup was working fine with 0.19.2 .. So I am not sure what changed > and where. Could this be some odd java class path loading issue ? Once > again - thanks for any help. -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\ **Post date:** [May 9, 2013, 10:24pm UTC](https://discuss.elastic.co/t/log4j-warn-no-appenders-could-be-found-for-logger-node/11907/3 "2013-05-09T22:24:31Z")
You use the service wrapper, maybe? Add $ES\_HOME/config/logging.yml to your classpath. Jörg Am 09.05.13 23:04, schrieb the\_nozzle: > Hey everyone > > Started to get that warning after upgrading to 0.9. Tried the usual > configuration options to no avail (config pasted below). Any help > would be appreciated.. > To make sure that the paths are set I uncommented all the environment > variables pertaining to logging and config paths .. > > cat /etc/sysconfig/elasticsearch > ES\_PATH\_LOG=/var/log/elasticsearch > ES\_PATH\_DATA=/var/lib/elasticsearch > ES\_PATH\_WORK=/tmp/elasticsearch > ES\_PATH\_CONF=/etc/elasticsearch > ES\_CONFIG=/etc/elasticsearch/elasticsearch.yml > > ES\_INCLUDE=/usr/share/elasticsearch/bin/elasticsearch.in.sh > > ES\_MIN\_MEM=12g > > ES\_MAX\_MEM=12g > > logging.yml: > > rootLogger: INFO, file > logger: > > # log action execution errors for easier debugging > > action: DEBUG > > # reduce the logging for aws, too much is logged under the default INFO > > com.amazonaws: WARN > > # gateway > > #gateway: DEBUG > #index.gateway: DEBUG > > # peer shard recovery > > #index.shard.recovery: DEBUG > > # discovery > > #discovery: TRACE > > appender: > file: > type: file > file: ${path.logs}/${cluster.name}.log > layout: > type: pattern > conversionPattern: "[%d{ISO8601}][%-5p][%-25c] %m%n" > > and also added /etc/elasticsearch/elasticsearch.yml > path.conf: /etc/elasticsearch > path.data: /var/lib/elasticsearch > path.work: /tmp/elasticsearch > path.logs: /var/log/elasticsearch > > This setup was working fine with 0.19.2 .. So I am not sure what > changed and where. Could this be some odd java class path loading > issue ? Once again - thanks for any help. > > -- > You received this message because you are subscribed to the Google > Groups "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send > an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![the\_nozzle](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/the_nozzle/32/1935_2.png) [@the\_nozzle](https://discuss.elastic.co/u/the_nozzle)\ **Post date:** [May 10, 2013, 12:46am UTC](https://discuss.elastic.co/t/log4j-warn-no-appenders-could-be-found-for-logger-node/11907/4 "2013-05-10T00:46:35Z")
Unfortunately still no bueno - I tried with ES\_INCLUDE and without and still getting the same result... I also played around with the init.d script and exported those vars there and not getting any love - anything else I could try ? My current working setup is 19.8 .. Curious what could of changed so drastically since then. On Thursday, May 9, 2013 3:24:31 PM UTC-7, Jörg Prante wrote: > You use the service wrapper, maybe? > > Add $ES\_HOME/config/logging.yml to your classpath. > > Jörg > > Am 09.05.13 23:04, schrieb the\_nozzle: > > > Hey everyone > > > > Started to get that warning after upgrading to 0.9. Tried the usual > > configuration options to no avail (config pasted below). Any help > > would be appreciated.. > > To make sure that the paths are set I uncommented all the environment > > variables pertaining to logging and config paths .. > > > > cat /etc/sysconfig/elasticsearch > > ES\_PATH\_LOG=/var/log/elasticsearch > > ES\_PATH\_DATA=/var/lib/elasticsearch > > ES\_PATH\_WORK=/tmp/elasticsearch > > ES\_PATH\_CONF=/etc/elasticsearch > > ES\_CONFIG=/etc/elasticsearch/elasticsearch.yml > > > > ES\_INCLUDE=/usr/share/elasticsearch/bin/elasticsearch.in.sh > > > > ES\_MIN\_MEM=12g > > > > ES\_MAX\_MEM=12g > > > > logging.yml: > > > > rootLogger: INFO, file > > logger: > > > > # log action execution errors for easier debugging > > > > action: DEBUG > > > > # reduce the logging for aws, too much is logged under the default > > INFO > > > com.amazonaws: WARN > > > > # gateway > > > > #gateway: DEBUG > > #index.gateway: DEBUG > > > > # peer shard recovery > > > > #index.shard.recovery: DEBUG > > > > # discovery > > > > #discovery: TRACE > > > > appender: > > file: > > type: file > > file: ${path.logs}/${cluster.name}.log > > layout: > > type: pattern > > conversionPattern: "[%d{ISO8601}][%-5p][%-25c] %m%n" > > > > and also added /etc/elasticsearch/elasticsearch.yml > > path.conf: /etc/elasticsearch > > path.data: /var/lib/elasticsearch > > path.work: /tmp/elasticsearch > > path.logs: /var/log/elasticsearch > > > > This setup was working fine with 0.19.2 .. So I am not sure what > > changed and where. Could this be some odd java class path loading > > issue ? Once again - thanks for any help. > > > > -- > > You received this message because you are subscribed to the Google > > Groups "elasticsearch" group. > > To unsubscribe from this group and stop receiving emails from it, send > > an email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \. > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![the\_nozzle](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/the_nozzle/32/1935_2.png) [@the\_nozzle](https://discuss.elastic.co/u/the_nozzle)\ **Post date:** [May 10, 2013, 12:50am UTC](https://discuss.elastic.co/t/log4j-warn-no-appenders-could-be-found-for-logger-node/11907/5 "2013-05-10T00:50:36Z")
Figured it out - added /etc/elasticsearch/logging.yml to the classpath and exported from init.d scritpt. Thanks. On Thursday, May 9, 2013 5:46:35 PM UTC-7, the\_nozzle wrote: > Unfortunately still no bueno - I tried with ES\_INCLUDE and without and > still getting the same result... I also played around with the init.d > script and exported those vars there and not getting any love - anything > else I could try ? My current working setup is 19.8 .. Curious what could > of changed so drastically since then. > > On Thursday, May 9, 2013 3:24:31 PM UTC-7, Jörg Prante wrote: > > > You use the service wrapper, maybe? > > > > Add $ES\_HOME/config/logging.yml to your classpath. > > > > Jörg > > > > Am 09.05.13 23:04, schrieb the\_nozzle: > > > > > Hey everyone > > > > > > Started to get that warning after upgrading to 0.9. Tried the usual > > > configuration options to no avail (config pasted below). Any help > > > would be appreciated.. > > > To make sure that the paths are set I uncommented all the environment > > > variables pertaining to logging and config paths .. > > > > > > cat /etc/sysconfig/elasticsearch > > > ES\_PATH\_LOG=/var/log/elasticsearch > > > ES\_PATH\_DATA=/var/lib/elasticsearch > > > ES\_PATH\_WORK=/tmp/elasticsearch > > > ES\_PATH\_CONF=/etc/elasticsearch > > > ES\_CONFIG=/etc/elasticsearch/elasticsearch.yml > > > > > > ES\_INCLUDE=/usr/share/elasticsearch/bin/elasticsearch.in.sh > > > > > > ES\_MIN\_MEM=12g > > > > > > ES\_MAX\_MEM=12g > > > > > > logging.yml: > > > > > > rootLogger: INFO, file > > > logger: > > > > > > # log action execution errors for easier debugging > > > > > > action: DEBUG > > > > > > # reduce the logging for aws, too much is logged under the default > > > > INFO > > > > > com.amazonaws: WARN > > > > > > # gateway > > > > > > #gateway: DEBUG > > > #index.gateway: DEBUG > > > > > > # peer shard recovery > > > > > > #index.shard.recovery: DEBUG > > > > > > # discovery > > > > > > #discovery: TRACE > > > > > > appender: > > > file: > > > type: file > > > file: ${path.logs}/${cluster.name}.log > > > layout: > > > type: pattern > > > conversionPattern: "[%d{ISO8601}][%-5p][%-25c] %m%n" > > > > > > and also added /etc/elasticsearch/elasticsearch.yml > > > path.conf: /etc/elasticsearch > > > path.data: /var/lib/elasticsearch > > > path.work: /tmp/elasticsearch > > > path.logs: /var/log/elasticsearch > > > > > > This setup was working fine with 0.19.2 .. So I am not sure what > > > changed and where. Could this be some odd java class path loading > > > issue ? Once again - thanks for any help. > > > > > > -- > > > You received this message because you are subscribed to the Google > > > Groups "elasticsearch" group. > > > To unsubscribe from this group and stop receiving emails from it, send > > > an email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com). > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\ **Post date:** [May 10, 2013, 12:54am UTC](https://discuss.elastic.co/t/log4j-warn-no-appenders-could-be-found-for-logger-node/11907/6 "2013-05-10T00:54:01Z")
I was talking about the classpath, not ES\_INCLUDE (I think it is ES\_CLASSPATH) The error comes from the logger unable to find logging.yml which is in $ES\_HOME/configuration/ What distribution do you use by any chance? zip? rpm? service wrapper? Maybe it is a packaging related issue. Jörg Am 10.05.13 02:46, schrieb the\_nozzle: > Unfortunately still no bueno - I tried with ES\_INCLUDE and without and > still getting the same result... I also played around with the init.d > script and exported those vars there and not getting any love - > anything else I could try ? My current working setup is 19.8 .. > Curious what could of changed so drastically since then. -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\ **Post date:** [May 10, 2013, 12:55am UTC](https://discuss.elastic.co/t/log4j-warn-no-appenders-could-be-found-for-logger-node/11907/7 "2013-05-10T00:55:45Z")
Weird... looks like this init.d script is wrong, from which distribution is it? Jörg Am 10.05.13 02:50, schrieb the\_nozzle: > Figured it out - added /etc/elasticsearch/logging.yml to the > classpath and exported from init.d scritpt. Thanks. -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![the\_nozzle](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/the_nozzle/32/1935_2.png) [@the\_nozzle](https://discuss.elastic.co/u/the_nozzle)\ **Post date:** [May 10, 2013, 1:32am UTC](https://discuss.elastic.co/t/log4j-warn-no-appenders-could-be-found-for-logger-node/11907/8 "2013-05-10T01:32:13Z")
I think the init.d script is the one that came with the 0.19.8 rpm for centos 5.5. I'm playing around with the generic rpm at the moment . Hmm odd issue - the configuration does not seem to be read at all for some reason and all the logging is going to stdout (It doesnt look like ES knows anything about the rest of the cluster) .. On Thursday, May 9, 2013 5:55:45 PM UTC-7, Jörg Prante wrote: > Weird... looks like this init.d script is wrong, from which distribution > is it? > > Jörg > > Am 10.05.13 02:50, schrieb the\_nozzle: > > > Figured it out - added /etc/elasticsearch/logging.yml to the > > classpath and exported from init.d scritpt. Thanks. -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![the\_nozzle](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/the_nozzle/32/1935_2.png) [@the\_nozzle](https://discuss.elastic.co/u/the_nozzle)\ **Post date:** [May 11, 2013, 12:12am UTC](https://discuss.elastic.co/t/log4j-warn-no-appenders-could-be-found-for-logger-node/11907/9 "2013-05-11T00:12:43Z")
Just to add - poked at the init.d script a bit and cleaned up/tweaked the config - so the elasticsearch.yml is being read (connection attempts are being made to the other nodes), but for some reason I'm still getting the log output on the console and not in the file... the final set of option passed to ES is as follows : -Des.config=/usr/share/elasticsearch/config//elasticsearch.yml -Des.path.conf=/usr/share/elasticsearch/config/ -Des.path.home=/usr/share/elasticsearch -Des.path.logs=/var/log/elasticsearch -Des.path.data=/var/lib/elasticsearch -Des.path.work=/tmp/elasticsearch -Des.path.plugins=/usr/share/elasticsearch/plugins -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**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, 2:37am UTC](https://discuss.elastic.co/t/log4j-warn-no-appenders-could-be-found-for-logger-node/11907/10 "2017-07-06T02:37:07Z")