# "Failed to configure logging" error on start up **URL:** \ **Category:** Elasticsearch\ **Created:** [July 30, 2014, 6:36pm UTC](https://discuss.elastic.co/t/failed-to-configure-logging-error-on-start-up/18985 "2014-07-30T18:36:24Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Peter\_Li](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/peter_li/32/109125_2.png) [@Peter\_Li](https://discuss.elastic.co/u/Peter_Li)\ **Post date:** [July 30, 2014, 6:36pm UTC](https://discuss.elastic.co/t/failed-to-configure-logging-error-on-start-up/18985/1 "2014-07-30T18:36:24Z")
I have a setup with multiple servers. The file tree for each is like the following: /data/ configs/ elastic-1.yml logging-1.yml scripts/ (empty) elastic-core/ (from distribution) bin/... config/... lib/... logs/... elastic-1/ bin --\> ../elastic-core/bin config/ elasticsearch.yml --\> ../../configs/elastic-1.yml logging.yml --\> ../../configs/logging-1.yml scripts --\> ../../configs/scripts data/... lib --\> ../elastic-core/lib logs/... In the elastic-1.yml, I have: path.conf=/data/elastic-1/config When I start the node without the config/scripts symbolic link: /data/elastic-1/bin/elasticsearch -Des.config=/data/elastic-1/config/elasticsearch.yml It runs fine. But if I have the scripts link/directory, it complains of: Failed to configure logging... org.elasticsearch.ElasticsearchException: Failed to load logging configuration at org.elasticsearch.common.logging.log4j.LogConfigurator.resolveConfig(LogConfigurator.java:117) at org.elasticsearch.common.logging.log4j.LogConfigurator.configure(LogConfigurator.java:81) at org.elasticsearch.bootstrap.Bootstrap.setupLogging(Bootstrap.java:94) at org.elasticsearch.bootstrap.Bootstrap.main(Bootstrap.java:178) at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:32) Caused by: java.nio.file.FileSystemException: /data/elastic-1/config: Unknown error 1912615013 at sun.nio.fs.UnixException.translateToIOException(Unknown Source) at sun.nio.fs.UnixException.asIOException(Unknown Source) at sun.nio.fs.UnixDirectoryStream$UnixDirectoryIterator.readNextEntry(Unknown Source) at sun.nio.fs.UnixDirectoryStream$UnixDirectoryIterator.hasNext(Unknown Source) at java.nio.file.FileTreeWalker.walk(Unknown Source) at java.nio.file.FileTreeWalker.walk(Unknown Source) at java.nio.file.Files.walkFileTree(Unknown Source) at org.elasticsearch.common.logging.log4j.LogConfigurator.resolveConfig(LogConfigurator.java:107) ... 4 more log4j:WARN No appenders could be found for logger (common.jna). log4j:WARN Please initialize the log4j system properly. log4j:WARN See [http://logging.apache.org/log4j/1.2/faq.html#noconfig](http://logging.apache.org/log4j/1.2/faq.html#noconfig) for more info. Any guesses as to why it is complaining ? Thanks in advance. -- 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). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/c4afc564-eae2-4826-8675-3f968bd7133b%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/c4afc564-eae2-4826-8675-3f968bd7133b%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Peter\_Li](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/peter_li/32/109125_2.png) [@Peter\_Li](https://discuss.elastic.co/u/Peter_Li)\ **Post date:** [July 30, 2014, 6:54pm UTC](https://discuss.elastic.co/t/failed-to-configure-logging-error-on-start-up/18985/2 "2014-07-30T18:54:32Z")
Did more experiments. If I used a "real" scripts directory, instead of a symbolic link, then no error message. But does this means that I will have to drop the same script into all my server's config/scripts directory ? It would be nice to use symbolic links for this. Any suggestions ? On Wednesday, July 30, 2014 1:36:24 PM UTC-5, Peter Li wrote: > I have a setup with multiple servers. > The file tree for each is like the following: > > /data/ > configs/ > elastic-1.yml > logging-1.yml > scripts/ > (empty) > elastic-core/ (from distribution) > bin/... > config/... > lib/... > logs/... > elastic-1/ > bin --\> ../elastic-core/bin > config/ > elasticsearch.yml --\> ../../configs/elastic-1.yml > logging.yml --\> ../../configs/logging-1.yml > scripts --\> ../../configs/scripts > data/... > lib --\> ../elastic-core/lib > logs/... > > In the elastic-1.yml, I have: > > path.conf=/data/elastic-1/config > > When I start the node without the config/scripts symbolic link: > > /data/elastic-1/bin/elasticsearch > -Des.config=/data/elastic-1/config/elasticsearch.yml > > It runs fine. But if I have the scripts link/directory, it complains of: > > Failed to configure logging... > org.elasticsearch.ElasticsearchException: Failed to load logging > configuration > at > org.elasticsearch.common.logging.log4j.LogConfigurator.resolveConfig(LogConfigurator.java:117) > at > org.elasticsearch.common.logging.log4j.LogConfigurator.configure(LogConfigurator.java:81) > at org.elasticsearch.bootstrap.Bootstrap.setupLogging(Bootstrap.java:94) > at org.elasticsearch.bootstrap.Bootstrap.main(Bootstrap.java:178) > at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:32) > Caused by: java.nio.file.FileSystemException: /data/elastic-1/config: > Unknown error 1912615013 > at sun.nio.fs.UnixException.translateToIOException(Unknown Source) > at sun.nio.fs.UnixException.asIOException(Unknown Source) > at > sun.nio.fs.UnixDirectoryStream$UnixDirectoryIterator.readNextEntry(Unknown > Source) > at sun.nio.fs.UnixDirectoryStream$UnixDirectoryIterator.hasNext(Unknown > Source) > at java.nio.file.FileTreeWalker.walk(Unknown Source) > at java.nio.file.FileTreeWalker.walk(Unknown Source) > at java.nio.file.Files.walkFileTree(Unknown Source) > at > org.elasticsearch.common.logging.log4j.LogConfigurator.resolveConfig(LogConfigurator.java:107) > ... 4 more > log4j:WARN No appenders could be found for logger (common.jna). > log4j:WARN Please initialize the log4j system properly. > log4j:WARN See [Apache log4j 1.2 - Frequently Asked Technical Questions](http://logging.apache.org/log4j/1.2/faq.html#noconfig) for > more info. > > Any guesses as to why it is complaining ? > > Thanks in advance. -- 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). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/5a010109-7f5e-43a4-b0b6-1ee59957fb8d%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/5a010109-7f5e-43a4-b0b6-1ee59957fb8d%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Ivan](https://avatars.discourse-cdn.com/v4/letter/i/df788c/32.png) [@Ivan](https://discuss.elastic.co/u/Ivan)\ **Post date:** [July 31, 2014, 4:18pm UTC](https://discuss.elastic.co/t/failed-to-configure-logging-error-on-start-up/18985/3 "2014-07-31T16:18:40Z")
That scenario should not happen since FileVisitOption.FOLLOW\_LINKS is enabled. > Seems like a bug somewhere. -- Ivan On Wed, Jul 30, 2014 at 11:54 AM, Peter Li [jenli.peter@gmail.com](mailto:jenli.peter@gmail.com) wrote: > Did more experiments. If I used a "real" scripts directory, instead of a > symbolic link, > then no error message. But does this means that I will have to drop the > same script > into all my server's config/scripts directory ? It would be nice to use > symbolic links > for this. > > Any suggestions ? > > On Wednesday, July 30, 2014 1:36:24 PM UTC-5, Peter Li wrote: > > > I have a setup with multiple servers. > > The file tree for each is like the following: > > > > /data/ > > configs/ > > elastic-1.yml > > logging-1.yml > > scripts/ > > (empty) > > elastic-core/ (from distribution) > > bin/... > > config/... > > lib/... > > logs/... > > elastic-1/ > > bin --\> ../elastic-core/bin > > config/ > > elasticsearch.yml --\> ../../configs/elastic-1.yml > > logging.yml --\> ../../configs/logging-1.yml > > scripts --\> ../../configs/scripts > > data/... > > lib --\> ../elastic-core/lib > > logs/... > > > > In the elastic-1.yml, I have: > > > > path.conf=/data/elastic-1/config > > > > When I start the node without the config/scripts symbolic link: > > > > /data/elastic-1/bin/elasticsearch -Des.config=/data/elastic-1/ > > config/elasticsearch.yml > > > > It runs fine. But if I have the scripts link/directory, it complains of: > > > > Failed to configure logging... > > org.elasticsearch.ElasticsearchException: Failed to load logging > > configuration > > at org.elasticsearch.common.logging.log4j.LogConfigurator. > > resolveConfig(LogConfigurator.java:117) > > at org.elasticsearch.common.logging.log4j.LogConfigurator. > > configure(LogConfigurator.java:81) > > at org.elasticsearch.bootstrap.Bootstrap.setupLogging(Bootstrap.java:94) > > at org.elasticsearch.bootstrap.Bootstrap.main(Bootstrap.java:178) > > at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:32) > > Caused by: java.nio.file.FileSystemException: /data/elastic-1/config: > > Unknown error 1912615013 > > at sun.nio.fs.UnixException.translateToIOException(Unknown Source) > > at sun.nio.fs.UnixException.asIOException(Unknown Source) > > at sun.nio.fs.UnixDirectoryStream$UnixDirectoryIterator.readNextEntry(Unknown > > Source) > > at sun.nio.fs.UnixDirectoryStream$UnixDirectoryIterator.hasNext(Unknown > > Source) > > at java.nio.file.FileTreeWalker.walk(Unknown Source) > > at java.nio.file.FileTreeWalker.walk(Unknown Source) > > at java.nio.file.Files.walkFileTree(Unknown Source) > > at org.elasticsearch.common.logging.log4j.LogConfigurator. > > resolveConfig(LogConfigurator.java:107) > > ... 4 more > > log4j:WARN No appenders could be found for logger (common.jna). > > log4j:WARN Please initialize the log4j system properly. > > log4j:WARN See [Apache log4j 1.2 - Frequently Asked Technical Questions](http://logging.apache.org/log4j/1.2/faq.html#noconfig) for > > more info. > > > > Any guesses as to why it is complaining ? > > > > Thanks in advance. > > -- > 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). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/5a010109-7f5e-43a4-b0b6-1ee59957fb8d%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/5a010109-7f5e-43a4-b0b6-1ee59957fb8d%40googlegroups.com) > [https://groups.google.com/d/msgid/elasticsearch/5a010109-7f5e-43a4-b0b6-1ee59957fb8d%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/5a010109-7f5e-43a4-b0b6-1ee59957fb8d%40googlegroups.com?utm_medium=email&utm_source=footer) > . > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- 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). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQB-aWq4cOJ0%2BZMuBBOwCWSBjk70JNgHu8bLLg8tt4F%3DWw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQB-aWq4cOJ0%2BZMuBBOwCWSBjk70JNgHu8bLLg8tt4F%3DWw%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**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, 1:11am UTC](https://discuss.elastic.co/t/failed-to-configure-logging-error-on-start-up/18985/4 "2017-07-06T01:11:57Z")