# Error Warning how to resolve it (highlighted errors in BLACK colour)

**URL:** <https://discuss.elastic.co/t/error-warning-how-to-resolve-it-highlighted-errors-in-black-colour/210320>\
**Category:** Kibana\
**Created:** [December 3, 2019, 9:46am UTC](https://discuss.elastic.co/t/error-warning-how-to-resolve-it-highlighted-errors-in-black-colour/210320 "2019-12-03T09:46:41Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![Hari\_Reddy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hari_reddy/32/53713_2.png) [@Hari\_Reddy](https://discuss.elastic.co/u/Hari_Reddy)\
**Post date:** [December 3, 2019, 9:46am UTC](https://discuss.elastic.co/t/error-warning-how-to-resolve-it-highlighted-errors-in-black-colour/210320/1 "2019-12-03T09:46:41Z")

</div>

bash-4.4$ cd usr/share/kibana/bin/  
bash-4.4$ ./kibana  
log [09:37:37.708] [info][plugins-system] Setting up [4] plugins: [security,translations,inspector,data]  
log [09:37:37.716] [info][plugins][security] Setting up plugin  
log [09:37:37.718] [**warning**][config][plugins][security] Generating a random key for xpack.security.encryptionKey. **To prevent sessions from being invalidated on restar** t, please set xpack.security.encryptionKey in kibana.yml  
log [09:37:37.719] [**warning**][config][plugins][security] Session cookies will be transmitted over insecure connections. **This is not recommended.**  
log [09:37:37.730] [info][plugins][translations] Setting up plugin  
log [09:37:37.731] [info][data][plugins] Setting up plugin  
log [09:37:37.736] [info][plugins-system] Starting [3] plugins: [security,translations,data]  
log [09:37:45.075] [info][status][plugin:kibana@7.4.2] Status changed from uninitialized to green - Ready  
log [09:37:45.081] [info][status][plugin:elasticsearch@7.4.2] Status changed from uninitialized to yellow - Waiting for Elasticsearch  
log [09:37:45.084] [info][status][plugin:xpack\_main@7.4.2] Status changed from uninitialized to yellow - Waiting for Elasticsearch  
log [09:37:45.102] [info][status][plugin:telemetry@7.4.2] Status changed from uninitialized to green - Ready  
log [09:37:45.108] [info][status][plugin:graph@7.4.2] Status changed from uninitialized to yellow - Waiting for Elasticsearch  
log [09:37:45.120] [info][status][plugin:monitoring@7.4.2] Status changed from uninitialized to green - Ready  
log [09:37:45.124] [info][status][plugin:spaces@7.4.2] Status changed from uninitialized to yellow - Waiting for Elasticsearch  
log [09:37:45.170] [info][status][plugin:security@7.4.2] Status changed from uninitialized to green - Ready  
log [09:37:45.172] [info][status][plugin:searchprofiler@7.4.2] Status changed from uninitialized to yellow - Waiting for Elasticsearch  
log [09:37:45.176] [info][status][plugin:ml@7.4.2] Status changed from uninitialized to yellow - Waiting for Elasticsearch  
log [09:37:45.246] [info][status][plugin:tilemap@7.4.2] Status changed from uninitialized to yellow - Waiting for Elasticsearch  
log [09:37:45.248] [info][status][plugin:watcher@7.4.2] Status changed from uninitialized to yellow - Waiting for Elasticsearch  
log [09:37:45.271] [info][status][plugin:grokdebugger@7.4.2] Status changed from uninitialized to yellow - Waiting for Elasticsearch  
log [09:37:45.282] [info][status][plugin:dashboard\_mode@7.4.2] Status changed from uninitialized to green - Ready  
log [09:37:45.285] [info][status][plugin:logstash@7.4.2] Status changed from uninitialized to yellow - Waiting for Elasticsearch  
log [09:37:45.295] [info][status][plugin:beats\_management@7.4.2] Status changed from uninitialized to yellow - Waiting for Elasticsearch  
log [09:37:45.316] [info][status][plugin:apm\_oss@7.4.2] Status changed from uninitialized to green - Ready  
log [09:37:45.351] [info][status][plugin:apm@7.4.2] Status changed from uninitialized to green - Ready  
log [09:37:45.354] [info][status][plugin:code@7.4.2] Status changed from uninitialized to green - Ready  
log [09:37:45.356] [info][status][plugin:data@7.4.2] Status changed from uninitialized to green - Ready  
log [09:37:45.360] [info][status][plugin:visualizations@7.4.2] Status changed from uninitialized to green - Ready  
log [09:37:45.364] [info][status][plugin:interpreter@7.4.2] Status changed from uninitialized to green - Ready  
log [09:37:45.366] [info][status][plugin:tile\_map@7.4.2] Status changed from uninitialized to green - Ready  
log [09:37:45.373] [info][status][plugin:task\_manager@7.4.2] Status changed from uninitialized to green - Ready  
log [09:37:45.379] [info][status][plugin:maps@7.4.2] Status changed from uninitialized to yellow - Waiting for Elasticsearch  
log [09:37:45.409] [info][status][plugin:canvas@7.4.2] Status changed from uninitialized to green - Ready  
log [09:37:45.415] [info][status][plugin:license\_management@7.4.2] Status changed from uninitialized to green - Ready  
log [09:37:45.417] [info][status][plugin:cloud@7.4.2] Status changed from uninitialized to green - Ready  
log [09:37:45.420] [info][status][plugin:index\_management@7.4.2] Status changed from uninitialized to yellow - Waiting for Elasticsearch  
log [09:37:45.443] [info][status][plugin:console@7.4.2] Status changed from uninitialized to green - Ready  
log [09:37:45.445] [info][status][plugin:console\_extensions@7.4.2] Status changed from uninitialized to green - Ready  
log [09:37:45.448] [info][status][plugin:index\_lifecycle\_management@7.4.2] Status changed from uninitialized to yellow - Waiting for Elasticsearch  
log [09:37:45.463] [info][status][plugin:metrics@7.4.2] Status changed from uninitialized to green - Ready  
log [09:37:45.511] [info][status][plugin:infra@7.4.2] Status changed from uninitialized to green - Ready  
log [09:37:45.514] [info][status][plugin:rollup@7.4.2] Status changed from uninitialized to yellow - Waiting for Elasticsearch  
log [09:37:45.524] [info][siem] Plugin initializing  
log [09:37:45.572] [info][siem] Plugin done initializing  
log [09:37:45.574] [info][status][plugin:siem@7.4.2] Status changed from uninitialized to green - Ready  
log [09:37:45.582] [info][status][plugin:remote\_clusters@7.4.2] Status changed from uninitialized to yellow - Waiting for Elasticsearch  
log [09:37:45.589] [info][status][plugin:cross\_cluster\_replication@7.4.2] Status changed from uninitialized to yellow - Waiting for Elasticsearch  
log [09:37:45.622] [info][status][plugin:upgrade\_assistant@7.4.2] Status changed from uninitialized to green - Ready  
log [09:37:45.663] [info][status][plugin:uptime@7.4.2] Status changed from uninitialized to green - Ready  
log [09:37:45.666] [info][status][plugin:oss\_telemetry@7.4.2] Status changed from uninitialized to green - Ready  
log [09:37:45.668] [info][status][plugin:file\_upload@7.4.2] Status changed from uninitialized to yellow - Waiting for Elasticsearch  
log [09:37:45.672] [**warning**][encrypted\_saved\_objects] **Generating a random key for xpack.encrypted\_saved\_objects.encryptionKey. To be able to decrypt encrypted saved objects attributes after restart, please set xpack.encrypted\_saved\_objects.encryptionKey in** kibana.yml  
log [09:37:45.674] [info][status][plugin:encrypted\_saved\_objects@7.4.2] Status changed from uninitialized to green - Ready  
log [09:37:45.696] [info][status][plugin:snapshot\_restore@7.4.2] Status changed from uninitialized to yellow - Waiting for Elasticsearch  
log [09:37:45.707] [info][status][plugin:kibana\_react@7.4.2] Status changed from uninitialized to green - Ready  
log [09:37:45.709] [info][status][plugin:region\_map@7.4.2] Status changed from uninitialized to green - Ready  
log [09:37:45.799] [info][status][plugin:timelion@7.4.2] Status changed from uninitialized to green - Ready  
log [09:37:45.802] [info][status][plugin:ui\_metric@7.4.2] Status changed from uninitialized to green - Ready  
log [09:37:45.804] [info][status][plugin:markdown\_vis@7.4.2] Status changed from uninitialized to green - Ready  
log [09:37:45.807] [info][status][plugin:metric\_vis@7.4.2] Status changed from uninitialized to green - Ready  
log [09:37:45.809] [info][status][plugin:table\_vis@7.4.2] Status changed from uninitialized to green - Ready  
log [09:37:45.811] [info][status][plugin:tagcloud@7.4.2] Status changed from uninitialized to green - Ready  
log [09:37:45.814] [info][status][plugin:vega@7.4.2] Status changed from uninitialized to green - Ready  
log [09:37:45.819] [**warning][browser-driver][reporting] Enabling the Chromium sandbox provides an additional layer of protection.**  
log [09:37:46.204] [info][status][plugin:elasticsearch@7.4.2] Status changed from yellow to green - Ready  
log [09:37:46.260] [info][license][xpack] Imported license information from Elasticsearch for the [data] cluster: mode: basic | status: active  
log [09:37:46.278] [info][status][plugin:xpack\_main@7.4.2] Status changed from yellow to green - Ready  
log [09:37:46.278] [info][status][plugin:graph@7.4.2] Status changed from yellow to green - Ready  
log [09:37:46.281] [info][status][plugin:searchprofiler@7.4.2] Status changed from yellow to green - Ready  
log [09:37:46.282] [info][status][plugin:ml@7.4.2] Status changed from yellow to green - Ready  
log [09:37:46.282] [info][status][plugin:tilemap@7.4.2] Status changed from yellow to green - Ready  
log [09:37:46.283] [info][status][plugin:watcher@7.4.2] Status changed from yellow to green - Ready  
log [09:37:46.284] [info][status][plugin:grokdebugger@7.4.2] Status changed from yellow to green - Ready  
log [09:37:46.284] [info][status][plugin:logstash@7.4.2] Status changed from yellow to green - Ready  
log [09:37:46.284] [info][status][plugin:beats\_management@7.4.2] Status changed from yellow to green - Ready  
log [09:37:46.285] [info][status][plugin:index\_management@7.4.2] Status changed from yellow to green - Ready  
log [09:37:46.286] [info][status][plugin:index\_lifecycle\_management@7.4.2] Status changed from yellow to green - Ready  
log [09:37:46.286] [info][status][plugin:rollup@7.4.2] Status changed from yellow to green - Ready  
log [09:37:46.287] [info][status][plugin:remote\_clusters@7.4.2] Status changed from yellow to green - Ready  
log [09:37:46.287] [info][status][plugin:cross\_cluster\_replication@7.4.2] Status changed from yellow to green - Ready  
log [09:37:46.287] [info][status][plugin:file\_upload@7.4.2] Status changed from yellow to green - Ready  
log [09:37:46.288] [info][status][plugin:snapshot\_restore@7.4.2] Status changed from yellow to green - Ready  
log [09:37:46.289] [info][kibana-monitoring][monitoring] Starting monitoring stats collection  
log [09:37:46.311] [info][status][plugin:maps@7.4.2] Status changed from yellow to green - Ready  
log [09:37:46.842] **[warning][reporting] Generating a random key for xpack.reporting.encryptionKey. To prevent pending reports from failing on restart, please set xpack.reporting.encryptionKey in kibana.yml**  
log [09:37:46.848] [info][status][plugin:reporting@7.4.2] Status changed from uninitialized to green - Ready  
log [09:37:46.961] [**warning**][reporting] The Reporting plugin encountered issues launching Chromium in a self-test. You may have trouble generating reports: **[Error: Failed to launch chrome!**  
/var/lib/kibana/headless\_shell-linux/headless\_shell: **error** while loading shared libraries: libnss3.so: cannot open shared object **file: No such file or directory**

TROUBLESHOOTING: [https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md](https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md)  
]  
log [09:37:46.962] [**warning**][reporting] See **Chromium's log output** at "/var/lib/kibana/headless\_shell-linux/chrome\_debug.log"  
log [09:37:46.965] [**warning**][reporting] Reporting **plugin self-check failed**. Please check the Kibana Reporting settings. **Error: Could not close browser client handle!**  
log [09:37:47.066] [info][listening] Server running at [http://0.0.0.0:5601](http://0.0.0.0:5601)  
log [09:37:47.134] [info][server][Kibana][http] http server running at [http://0.0.0.0:5601](http://0.0.0.0:5601)  
log [09:37:47.139] [info][status][plugin:spaces@7.4.2] Status changed from yellow to green - Ready  
log [09:37:47.145] [**warning**][telemetry] **Error scheduling task** , received [task:oss\_telemetry-vis\_telemetry]: version conflict, **document already exists** (current version [7]): [version\_conflict\_engine\_exception] [task:oss\_telemetry-vis\_telemetry]: version conflict, document already exists (current version [7]), with { index\_uuid="O4vz6PwARXSCDPz-OAVyBQ" & shard="0" & index=".kibana\_task\_manager\_1" }  
log [09:37:47.147] [**warning]**[maps] **Error scheduling telemetry task** , received [task:Maps-maps\_telemetry]: version conflict, document already exists (current version [10]): [version\_conflict\_engine\_exception] [task:Maps-maps\_telemetry]: version conflict, document already exists (current version [10]), with { index\_uuid="O4vz6PwARXSCDPz-OAVyBQ" & shard="0" & index=".kibana\_task\_manager\_1" }

---

<div class="post-metadata">

**Author:** ![Hari\_Reddy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hari_reddy/32/53713_2.png) [@Hari\_Reddy](https://discuss.elastic.co/u/Hari_Reddy)\
**Post date:** [December 3, 2019, 9:59am UTC](https://discuss.elastic.co/t/error-warning-how-to-resolve-it-highlighted-errors-in-black-colour/210320/2 "2019-12-03T09:59:52Z")

</div>

**kibana.yml file**  
server.port: 5601  
server.host: "0.0.0.0"  
server.name: kibana  
elasticsearch.hosts: ["[http://localhost:9200](http://localhost:9200)"]  
elasticsearch.username: "elastic"  
elasticsearch.password: "Bangaram9$"  
xpack.reporting.capture.browser.chromium.disableSandbox: true  
csp.strict: true  
xpack.security.sessionTimeout: 3600000  
xpack.security.enabled: true

---

<div class="post-metadata">

**Author:** ![mathur7vidit](https://avatars.discourse-cdn.com/v4/letter/m/d07c76/32.png) [@mathur7vidit](https://discuss.elastic.co/u/mathur7vidit)\
**Post date:** [December 3, 2019, 10:22am UTC](https://discuss.elastic.co/t/error-warning-how-to-resolve-it-highlighted-errors-in-black-colour/210320/4 "2019-12-03T10:22:18Z")

</div>

xpack.reporting.enabled: true  
xpack.reporting.encryptionKey: "something\_secret"  
xpack.reporting.queue.timeout: 600000  
xpack.reporting.csv.maxSizeBytes: 20971520

try placing these settings. it will fix warning related to generating random key. telemetry related issue was faced in my cluster as well, but i have never seen any impact of it till date.. sharing you more details on other warnings

---

<div class="post-metadata">

**Author:** ![mathur7vidit](https://avatars.discourse-cdn.com/v4/letter/m/d07c76/32.png) [@mathur7vidit](https://discuss.elastic.co/u/mathur7vidit)\
**Post date:** [December 3, 2019, 10:26am UTC](https://discuss.elastic.co/t/error-warning-how-to-resolve-it-highlighted-errors-in-black-colour/210320/5 "2019-12-03T10:26:02Z")

</div>

i dont think there is need of placing **xpack.reporting.capture.browser.chromium.disableSandbox: true** setting. it is automatically handled if you have xpack installed. read below link  
[https://www.elastic.co/guide/en/kibana/current/reporting-chromium-sandbox.html](https://www.elastic.co/guide/en/kibana/current/reporting-chromium-sandbox.html)

---

<div class="post-metadata">

**Author:** ![Hari\_Reddy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hari_reddy/32/53713_2.png) [@Hari\_Reddy](https://discuss.elastic.co/u/Hari_Reddy)\
**Post date:** [December 3, 2019, 12:16pm UTC](https://discuss.elastic.co/t/error-warning-how-to-resolve-it-highlighted-errors-in-black-colour/210320/6 "2019-12-03T12:16:38Z")

</div>

added these things in kibana.yml but still getting same error

---

<div class="post-metadata">

**Author:** ![mathur7vidit](https://avatars.discourse-cdn.com/v4/letter/m/d07c76/32.png) [@mathur7vidit](https://discuss.elastic.co/u/mathur7vidit)\
**Post date:** [December 3, 2019, 12:31pm UTC](https://discuss.elastic.co/t/error-warning-how-to-resolve-it-highlighted-errors-in-black-colour/210320/7 "2019-12-03T12:31:11Z")

</div>

is it preventing kibana to come up?

---

<div class="post-metadata">

**Author:** ![mathur7vidit](https://avatars.discourse-cdn.com/v4/letter/m/d07c76/32.png) [@mathur7vidit](https://discuss.elastic.co/u/mathur7vidit)\
**Post date:** [December 3, 2019, 12:33pm UTC](https://discuss.elastic.co/t/error-warning-how-to-resolve-it-highlighted-errors-in-black-colour/210320/8 "2019-12-03T12:33:10Z")

</div>

can you tell me what all warning messages are still showing.. config shared above should fix \*\* **[warning][reporting] Generating a random key for xpack.reporting.encryptionKey. To prevent pending reports from failing on restart, please set xpack.reporting.encryptionKey in kibana.yml**\*\*

---

<div class="post-metadata">

**Author:** ![Hari\_Reddy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hari_reddy/32/53713_2.png) [@Hari\_Reddy](https://discuss.elastic.co/u/Hari_Reddy)\
**Post date:** [December 3, 2019, 12:36pm UTC](https://discuss.elastic.co/t/error-warning-how-to-resolve-it-highlighted-errors-in-black-colour/210320/9 "2019-12-03T12:36:07Z")

</div>

**kibana.yml file**  
server.port: 5601  
server.host: "0.0.0.0"  
server.name: kibana  
elasticsearch.hosts: ["[http://localhost:9200](http://localhost:9200)"]  
elasticsearch.username: "elastic"  
elasticsearch.password: "Bangaram9$"  
xpack.reporting.capture.browser.chromium.disableSandbox: true  
csp.strict: true  
xpack.security.sessionTimeout: 3600000  
xpack.security.enabled: true  
xpack.reporting.enabled: true  
xpack.reporting.encryptionKey: "bangaram"  
xpack.reporting.queue.timeout: 600000  
xpack.reporting.csv.maxSizeBytes: 20971520

---

<div class="post-metadata">

**Author:** ![mathur7vidit](https://avatars.discourse-cdn.com/v4/letter/m/d07c76/32.png) [@mathur7vidit](https://discuss.elastic.co/u/mathur7vidit)\
**Post date:** [December 3, 2019, 12:40pm UTC](https://discuss.elastic.co/t/error-warning-how-to-resolve-it-highlighted-errors-in-black-colour/210320/10 "2019-12-03T12:40:54Z")

</div>

Can you confirm few things

1. what license you are using?
2. is kibana console coming up or not?
3. what all warning messages are still coming?

---

<div class="post-metadata">

**Author:** ![Hari\_Reddy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hari_reddy/32/53713_2.png) [@Hari\_Reddy](https://discuss.elastic.co/u/Hari_Reddy)\
**Post date:** [December 3, 2019, 12:48pm UTC](https://discuss.elastic.co/t/error-warning-how-to-resolve-it-highlighted-errors-in-black-colour/210320/11 "2019-12-03T12:48:04Z")

</div>

> [@mathur7vidit](#):
>
> preventing

1. basic license

2. kibana console and everything working fine but i am not satisfied because of that warnings

3. **Warnings**  
**a)**  
log [12:14:24.117] [warning][config][plugins][security] Generating a random key for xpack.security.encryptionKey. To prevent sessions from being invalidated on restart, please set xpack.security.encryptionKey in kibana.yml  
**b)**  
log [12:14:24.118] [warning][config][plugins][security] Session cookies will be transmitted over insecure connections. This is not recommended.  
**c)**  
log [12:14:34.262] [warning][encrypted\_saved\_objects] Generating a random key for xpack.encrypted\_saved\_objects.encryptionKey. To be able to decrypt encrypted saved objects attributes after restart, please set xpack.encrypted\_saved\_objects.encryptionKey in kibana.yml  
**d)**  
log [12:14:34.417] [warning][browser-driver][reporting] Enabling the Chromium sandbox provides an additional layer of protection.  
**e)**  
log [12:14:35.912] [warning][reporting] The Reporting plugin encountered issues launching Chromium in a self-test. You may have trouble generating reports: [Error: Failed to launch chrome!  
**f)**  
log [12:14:35.913] [warning][reporting] See Chromium's log output at "/var/lib/kibana/headless\_shell-linux/chrome\_debug.log"  
**g)**  
log [12:14:35.914] [warning][reporting] Reporting plugin self-check failed. Please check the Kibana Reporting settings. Error: Could not close browser client handle!  
**f)**  
log [12:14:35.997] [warning][telemetry] Error scheduling task, received [task:oss\_telemetry-vis\_telemetry]: version conflict, document already exists (current version [7]): [version\_conflict\_engine\_exception] [task:oss\_telemetry-vis\_telemetry]: version conflict, document already exists (current version [7]), with { index\_uuid="O4vz6PwARXSCDPz-OAVyBQ" & shard="0" & index=".kibana\_task\_manager\_1" }  
**g)**  
log [12:14:35.998] [warning][maps] Error scheduling telemetry task, received [task:Maps-maps\_telemetry]: version conflict, document already exists (current version [10]): [version\_conflict\_engine\_exception] [task:Maps-maps\_telemetry]: version conflict, document already exists (current version [10]), with { index\_uuid="O4vz6PwARXSCDPz-OAVyBQ" & shard="0" & index=".kibana\_task\_manager\_1" }

---

<div class="post-metadata">

**Author:** ![Hari\_Reddy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hari_reddy/32/53713_2.png) [@Hari\_Reddy](https://discuss.elastic.co/u/Hari_Reddy)\
**Post date:** [December 3, 2019, 1:27pm UTC](https://discuss.elastic.co/t/error-warning-how-to-resolve-it-highlighted-errors-in-black-colour/210320/12 "2019-12-03T13:27:01Z")

</div>

i am looking for one more option suppose, i just logged in **kibana** console with **username** and **password** now i am not using kibana .. so when i am inactive then it should logot automatically..and if i again open it then should ask **username** and **password** again, how we can put condition for it using x-pack...

---

<div class="post-metadata">

**Author:** ![Jay\_Tran](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jay_tran/32/47985_2.png) [@Jay\_Tran](https://discuss.elastic.co/u/Jay_Tran)\
**Post date:** [December 28, 2019, 1:51am UTC](https://discuss.elastic.co/t/error-warning-how-to-resolve-it-highlighted-errors-in-black-colour/210320/13 "2019-12-28T01:51:42Z")

</div>

Hi hari,

I got the same issues event though I launched kibana without security mode. can you tell me know how to resolve them?

---

<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:** [January 25, 2020, 1:57am UTC](https://discuss.elastic.co/t/error-warning-how-to-resolve-it-highlighted-errors-in-black-colour/210320/14 "2020-01-25T01:57:47Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.