# Error after upgrading to Kibana 4.2 - Full page does not render

**URL:** <https://discuss.elastic.co/t/error-after-upgrading-to-kibana-4-2-full-page-does-not-render/37258>\
**Category:** Kibana\
**Created:** [December 15, 2015, 3:59pm UTC](https://discuss.elastic.co/t/error-after-upgrading-to-kibana-4-2-full-page-does-not-render/37258 "2015-12-15T15:59:50Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![fetzilla](https://avatars.discourse-cdn.com/v4/letter/f/77aa72/32.png) [@fetzilla](https://discuss.elastic.co/u/fetzilla)\
**Post date:** [December 15, 2015, 3:59pm UTC](https://discuss.elastic.co/t/error-after-upgrading-to-kibana-4-2-full-page-does-not-render/37258/1 "2015-12-15T15:59:50Z")

</div>

Here's the error log from Kibana

FATAL CLI ERROR YAMLException: can not read a block mapping entry; a multiline key may not be an implicit key at line 73, column 1:

```
^
at generateError (/opt/kibana/node_modules/js-yaml/lib/js-yaml/loader.js:160:10)
at throwError (/opt/kibana/node_modules/js-yaml/lib/js-yaml/loader.js:166:9)
at readBlockMapping (/opt/kibana/node_modules/js-yaml/lib/js-yaml/loader.js:1027:9)
at composeNode (/opt/kibana/node_modules/js-yaml/lib/js-yaml/loader.js:1315:12)
at readDocument (/opt/kibana/node_modules/js-yaml/lib/js-yaml/loader.js:1478:3)
at loadDocuments (/opt/kibana/node_modules/js-yaml/lib/js-yaml/loader.js:1538:5)
at load (/opt/kibana/node_modules/js-yaml/lib/js-yaml/loader.js:1555:19)
at Object.safeLoad (/opt/kibana/node_modules/js-yaml/lib/js-yaml/loader.js:1573:10)
at module.exports (/opt/kibana/src/cli/serve/readYamlConfig.js:43:19)
at Command.callee$1$0$ (/opt/kibana/src/cli/serve/serve.js:66:22)
at tryCatch (/opt/kibana/node_modules/babel-runtime/regenerator/runtime.js:67:40)
at GeneratorFunctionPrototype.invoke [as _invoke] (/opt/kibana/node_modules/babel-runtime/regenerator/runtime.js:315:22)
at GeneratorFunctionPrototype.prototype.(anonymous function) [as next] (/opt/kibana/node_modules/babel-runtime/regenerator/runtime.js:100:21)
at invoke (/opt/kibana/node_modules/babel-runtime/regenerator/runtime.js:136:37)
at enqueueResult (/opt/kibana/node_modules/babel-runtime/regenerator/runtime.js:185:17)
at new Promise (/opt/kibana/node_modules/babel-core/node_modules/core-js/modules/es6.promise.js:183:7)

```

I'm not sure where to go from here

---

<div class="post-metadata">

**Author:** ![Court](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/court/32/6640_2.png) [@Court](https://discuss.elastic.co/u/Court)\
**Post date:** [December 15, 2015, 8:32pm UTC](https://discuss.elastic.co/t/error-after-upgrading-to-kibana-4-2-full-page-does-not-render/37258/2 "2015-12-15T20:32:45Z")

</div>

This seems to be choking on your kibana.yml file. Can you upload yours? Just make sure to change any secure config values (e.g. shield credentials) before uploading.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [December 15, 2015, 10:30pm UTC](https://discuss.elastic.co/t/error-after-upgrading-to-kibana-4-2-full-page-does-not-render/37258/3 "2015-12-15T22:30:59Z")

</div>

> [@fetzilla](#):
>
> FATAL CLI ERROR YAMLException: can not read a block mapping entry; a multiline key may not be an implicit key at line 73, column 1

Check line 73 of your config.

---

<div class="post-metadata">

**Author:** ![ddusza](https://avatars.discourse-cdn.com/v4/letter/d/e19b73/32.png) [@ddusza](https://discuss.elastic.co/u/ddusza)\
**Post date:** [December 16, 2015, 4:01pm UTC](https://discuss.elastic.co/t/error-after-upgrading-to-kibana-4-2-full-page-does-not-render/37258/4 "2015-12-16T16:01:14Z")

</div>

I had the same problem (among others), and found that the kibana.yml file that came with the kibana-4.2.0-linux-x64.tar.gz file I used to upgrade, had this at the bottom:

```
# Set this to true to log all events, including system usage information and all requests.
# logging.verbose

```

I saw the error when I uncommented the last line to turn on logging. It was missing the colon and 'true'. After I added the missing parts, it worked fine.

```
# Set this to true to log all events, including system usage information and all requests.
logging.verbose: true
```

---

<div class="post-metadata">

**Author:** ![fetzilla](https://avatars.discourse-cdn.com/v4/letter/f/77aa72/32.png) [@fetzilla](https://discuss.elastic.co/u/fetzilla)\
**Post date:** [December 16, 2015, 8:06pm UTC](https://discuss.elastic.co/t/error-after-upgrading-to-kibana-4-2-full-page-does-not-render/37258/5 "2015-12-16T20:06:32Z")

</div>

My config file had 72 lines

I decided to uplift to Kibana 4.3 and see if that fixed it. It did. Everything is now working as expected.

Thanks for the help everyone!

---

<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, 2:06pm UTC](https://discuss.elastic.co/t/error-after-upgrading-to-kibana-4-2-full-page-does-not-render/37258/6 "2017-07-06T14:06:26Z")

</div>