# Logging not initialised properly after upgrade to 2.0 **URL:** \ **Category:** Elasticsearch\ **Created:** [November 25, 2015, 11:26am UTC](https://discuss.elastic.co/t/logging-not-initialised-properly-after-upgrade-to-2-0/35542 "2015-11-25T11:26:59Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![aodj](https://avatars.discourse-cdn.com/v4/letter/a/779978/32.png) [@aodj](https://discuss.elastic.co/u/aodj)\ **Post date:** [November 25, 2015, 11:26am UTC](https://discuss.elastic.co/t/logging-not-initialised-properly-after-upgrade-to-2-0/35542/1 "2015-11-25T11:26:59Z")
I'm currently testing out migrating to 2.0 from 1.7 but I keep receiving a notification saying > log4j:WARN No appenders could be found for logger (bootstrap). > 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. I'm running ES under Supervisor and the configuration parameters I was passing previously worked, and I can't see anything that would stop it from detecting my `logging.yml` in the breaking changes, so can anyone point out what's not correct? ES is being invoked with the following command: ``` /usr/share/elasticsearch/bin/elasticsearch -Des.default.path.home=/usr/share/elasticsearch -Des.default.path.logs=/var/log/elasticsearch -Des.default.path.data=/var/lib/elasticsearch -Des.default.path.conf=/home/ubuntu/conf/es/ ``` ---
**Author:** ![justnj](https://avatars.discourse-cdn.com/v4/letter/j/e19adc/32.png) [@justnj](https://discuss.elastic.co/u/justnj)\ **Post date:** [November 26, 2015, 11:55am UTC](https://discuss.elastic.co/t/logging-not-initialised-properly-after-upgrade-to-2-0/35542/2 "2015-11-26T11:55:06Z")
Hi can you please share the upgrade steps from 1.7 to 2.0 along with migration checklist ---
**Author:** ![aodj](https://avatars.discourse-cdn.com/v4/letter/a/779978/32.png) [@aodj](https://discuss.elastic.co/u/aodj)\ **Post date:** [November 26, 2015, 1:30pm UTC](https://discuss.elastic.co/t/logging-not-initialised-properly-after-upgrade-to-2-0/35542/3 "2015-11-26T13:30:43Z")
The blog detailed the release of 2.0.0 GA here: [https://www.elastic.co/blog/elasticsearch-2-0-0-released](https://www.elastic.co/blog/elasticsearch-2-0-0-released) The first step would be to run the [ES Migration plugin](http://github.com/elastic/elasticsearch-migration) which details any problems you might have. Once everything checks out you should read over the [breaking changes list](https://www.elastic.co/guide/en/elasticsearch/reference/2.0/breaking-changes-2.0.html) ---
**Author:** ![aodj](https://avatars.discourse-cdn.com/v4/letter/a/779978/32.png) [@aodj](https://discuss.elastic.co/u/aodj)\ **Post date:** [November 26, 2015, 3:53pm UTC](https://discuss.elastic.co/t/logging-not-initialised-properly-after-upgrade-to-2-0/35542/4 "2015-11-26T15:53:01Z")
I resolved this eventually; the problem appears to be related to missing fields in `logging.yml`. I discovered this after diff-ing the one I had and the one that ships with the ES 2.0 deb package. The error presented in the logs was completely useless and I guess is part of the reason [this](https://github.com/elastic/elasticsearch/issues/14953) issue exists. The error presented sent me off down a wrong path. You can view the diff of the two files [here](https://www.diffnow.com/?report=k2hax) (mine is on the right hand side). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 5, 2017, 11:35pm UTC](https://discuss.elastic.co/t/logging-not-initialised-properly-after-upgrade-to-2-0/35542/5 "2017-07-05T23:35:33Z")