# Unable to fet ch data from kibana\_settings collector **URL:** \ **Category:** Kibana\ **Created:** [March 19, 2018, 6:03pm UTC](https://discuss.elastic.co/t/unable-to-fet-ch-data-from-kibana-settings-collector/124624 "2018-03-19T18:03:47Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![vaishali1](https://avatars.discourse-cdn.com/v4/letter/v/f05b48/32.png) [@vaishali1](https://discuss.elastic.co/u/vaishali1)\ **Post date:** [March 19, 2018, 6:03pm UTC](https://discuss.elastic.co/t/unable-to-fet-ch-data-from-kibana-settings-collector/124624/1 "2018-03-19T18:03:47Z")
Hi, Can anyone explain me this Warning? I installed X-pack-6.2.2 for elasticsearch and kibana. When i try to run Kibana.bat. I can login to "localhost:9200" **Config: Error 503 Service Unavailable: Request Timeout after 30000ms** log [17:57:05.350] [warning][kibana-monitoring][monitoring-ui] Unable to fet ch data from kibana\_settings collector Unhandled rejection TypeError: Cannot read property 'result' of undefined at C:/Users/328347935/Downloads/EKL/kibana-6.2.2-windows-x86\_64/kibana-6.2.2 -windows-x86\_64/plugins/x-pack/plugins/monitoring/server/kibana\_monitoring/lib/t ype\_collector.js:91:50 at Array.filter (native) at C:/Users/328347935/Downloads/EKL/kibana-6.2.2-windows-x86\_64/kibana-6.2.2 -windows-x86\_64/plugins/x-pack/plugins/monitoring/server/kibana\_monitoring/lib/t ype\_collector.js:91:29 at next (native) at step (C:\Users\328347935\Downloads\EKL\kibana-6.2.2-windows-x86\_64\kibana -6.2.2-windows-x86\_64\plugins\x-pack\plugins\monitoring\server\kibana\_monitoring \lib\type\_collector.js:18:202) at C:\Users\328347935\Downloads\EKL\kibana-6.2.2-windows-x86\_64\kibana-6.2.2 -windows-x86\_64\plugins\x-pack\plugins\monitoring\server\kibana\_monitoring\lib\t ype\_collector.js:18:383 at tryCatcher (C:\Users\328347935\Downloads\EKL\kibana-6.2.2-windows-x86\_64 kibana-6.2.2-windows-x86\_64\plugins\x-pack\node\_modules\bluebird\js\release\util .js:11:23) at Promise.\_settlePromiseFromHandler (C:\Users\328347935\Downloads\EKL\kiban a-6.2.2-windows-x86\_64\kibana-6.2.2-windows-x86\_64\plugins\x-pack\node\_modules\b luebird\js\release\promise.js:489:31) at Promise.\_settlePromise (C:\Users\328347935\Downloads\EKL\kibana-6.2.2-win dows-x86\_64\kibana-6.2.2-windows-x86\_64\plugins\x-pack\node\_modules\bluebird\js release\promise.js:546:18) at Promise.\_settlePromise0 (C:\Users\328347935\Downloads\EKL\kibana-6.2.2-wi ndows-x86\_64\kibana-6.2.2-windows-x86\_64\plugins\x-pack\node\_modules\bluebird\js \release\promise.js:591:10) at Promise.\_settlePromises (C:\Users\328347935\Downloads\EKL\kibana-6.2.2-wi ndows-x86\_64\kibana-6.2.2-windows-x86\_64\plugins\x-pack\node\_modules\bluebird\js \release\promise.js:674:18) at Promise.\_fulfill (C:\Users\328347935\Downloads\EKL\kibana-6.2.2-windows-x 86\_64\kibana-6.2.2-windows-x86\_64\plugins\x-pack\node\_modules\bluebird\js\releas e\promise.js:615:18) at MappingPromiseArray.PromiseArray.\_resolve (C:\Users\328347935\Downloads\E KL\kibana-6.2.2-windows-x86\_64\kibana-6.2.2-windows-x86\_64\plugins\x-pack\node\_m odules\bluebird\js\release\promise\_array.js:125:19) at MappingPromiseArray.\_promiseFulfilled (C:\Users\328347935\Downloads\EKL\k ibana-6.2.2-windows-x86\_64\kibana-6.2.2-windows-x86\_64\plugins\x-pack\node\_modul es\bluebird\js\release\map.js:97:18) at Promise.\_settlePromise (C:\Users\328347935\Downloads\EKL\kibana-6.2.2-win dows-x86\_64\kibana-6.2.2-windows-x86\_64\plugins\x-pack\node\_modules\bluebird\js release\promise.js:551:26) at Promise.\_settlePromise0 (C:\Users\328347935\Downloads\EKL\kibana-6.2.2-wi ndows-x86\_64\kibana-6.2.2-windows-x86\_64\plugins\x-pack\node\_modules\bluebird\js \release\promise.js:591:10) at Promise.\_settlePromises (C:\Users\328347935\Downloads\EKL\kibana-6.2.2-wi ndows-x86\_64\kibana-6.2.2-windows-x86\_64\plugins\x-pack\node\_modules\bluebird\js \release\promise.js:674:18) at Promise.\_fulfill (C:\Users\328347935\Downloads\EKL\kibana-6.2.2-windows-x 86\_64\kibana-6.2.2-windows-x86\_64\plugins\x-pack\node\_modules\bluebird\js\releas e\promise.js:615:18) at Promise.\_resolveCallback (C:\Users\328347935\Downloads\EKL\kibana-6.2.2-w indows-x86\_64\kibana-6.2.2-windows-x86\_64\plugins\x-pack\node\_modules\bluebird\j s\release\promise.js:416:57) at Promise.\_settlePromiseFromHandler (C:\Users\328347935\Downloads\EKL\kiban a-6.2.2-windows-x86\_64\kibana-6.2.2-windows-x86\_64\plugins\x-pack\node\_modules\b luebird\js\release\promise.js:502:17) at Promise.\_settlePromise (C:\Users\328347935\Downloads\EKL\kibana-6.2.2-win dows-x86\_64\kibana-6.2.2-windows-x86\_64\plugins\x-pack\node\_modules\bluebird\js release\promise.js:546:18) at Promise.\_settlePromise0 (C:\Users\328347935\Downloads\EKL\kibana-6.2.2-wi ndows-x86\_64\kibana-6.2.2-windows-x86\_64\plugins\x-pack\node\_modules\bluebird\js \release\promise.js:591:10) ---
**Author:** ![chrisronline](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chrisronline/32/28230_2.png) [@chrisronline](https://discuss.elastic.co/u/chrisronline)\ **Post date:** [March 23, 2018, 4:47pm UTC](https://discuss.elastic.co/t/unable-to-fet-ch-data-from-kibana-settings-collector/124624/2 "2018-03-23T16:47:56Z")
Hi @vaishali1, Can your post your `kibana.yml` configuration file? Thanks, Chris ---
**Author:** ![tsullivan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tsullivan/32/31077_2.png) [@tsullivan](https://discuss.elastic.co/u/tsullivan)\ **Post date:** [March 23, 2018, 5:18pm UTC](https://discuss.elastic.co/t/unable-to-fet-ch-data-from-kibana-settings-collector/124624/3 "2018-03-23T17:18:18Z")
Heya, > `Config: Error 503 Service Unavailable: Request Timeout after 30000ms` I'm not sure what that's in regards to, since I'm not able to see which request that response is associated with. > `Unhandled rejection TypeError: Cannot read property 'result' of undefined at C:/Users/328347935/Downloads/EKL/kibana-6.2.2-windows-x86_64/kibana-6.2.2 -windows-x86_64/plugins/x-pack/plugins/monitoring/server/kibana_monitoring/lib/t ype_collector.js:91:50` This is a bug and from my investigation it's possibly around no `.kibana-monitoring-*` indices being available, or permissions not allowing read access to those indices for the kibana system user. It will be fixed in 6.3 but that should also be backported to 6.2.x - it's a matter of a bad lookup on a property of a data object where the data isn't there. Just curious, what's the status of Kibana and the connection to Elasticsearch? What is the status of your Monitoring setup? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [April 20, 2018, 5:18pm UTC](https://discuss.elastic.co/t/unable-to-fet-ch-data-from-kibana-settings-collector/124624/4 "2018-04-20T17:18:21Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.