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

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 restart, 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
]
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
log [09:37:47.134] [info][server][Kibana][http] http server running at 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" }

kibana.yml file
server.port: 5601
server.host: "0.0.0.0"
server.name: kibana
elasticsearch.hosts: ["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: "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

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

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

is it preventing kibana to come up?

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**

kibana.yml file
server.port: 5601
server.host: "0.0.0.0"
server.name: kibana
elasticsearch.hosts: ["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

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?
  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" }

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...