Kibana upgrade to 7.3 Error

hi ,

After 7.3 Kibana upgrade from 6.2.4 getting below error . My elastic is working fine with 7.3 version.
I guess it's related to chromium.

log [14:01:54.270] [warning][security] Session cookies will be transmitted over insecure connections. This is not recommended.
log [14:01:54.613] [info][status][plugin:file_upload@7.3.0] Status changed from uninitialized to yellow - Waiting for Elasticsearch
log [14:01:54.616] [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 [14:01:54.617] [info][status][plugin:encrypted_saved_objects@7.3.0] Status changed from uninitialized to green - Ready
log [14:01:54.627] [info][status][plugin:snapshot_restore@7.3.0] Status changed from uninitialized to yellow - Waiting for Elasticsearch
log [14:01:54.640] [info][status][plugin:actions@7.3.0] Status changed from uninitialized to green - Ready
log [14:01:54.648] [info][status][plugin:alerting@7.3.0] Status changed from uninitialized to green - Ready
log [14:01:54.651] [info][status][plugin:data@7.3.0] Status changed from uninitialized to green - Ready
log [14:01:54.789] [info][status][plugin:timelion@7.3.0] Status changed from uninitialized to green - Ready
log [14:01:54.793] [info][status][plugin:ui_metric@7.3.0] Status changed from uninitialized to green - Ready
log [14:01:54.796] [info][status][plugin:visualizations@7.3.0] Status changed from uninitialized to green - Ready
log [14:01:55.220] [info][status][plugin:elasticsearch@7.3.0] Status changed from yellow to green - Ready
log [14:01:55.398] [info][license][xpack] Imported license information from Elasticsearch for the [data] cluster: mode: trial | status: expired | expiry date: 2019-06-09T10:32:56+00:00
log [14:01:55.416] [info][kibana-monitoring][monitoring] Monitoring status upload endpoint is not enabled in Elasticsearch:Monitoring stats collection is stopped
log [14:01:55.430] [info][status][plugin:maps@7.3.0] Status changed from yellow to green - Ready
log [14:01:56.002] [info][status][plugin:reporting@7.3.0] Status changed from uninitialized to green - Ready
log [14:01:56.048] [warning][reporting] The Reporting plugin encountered issues launching Chromium in a self-test. You may have trouble generating reports: [Error: Failed to launch chrome!
[0814/140156.009927:WARNING:resource_bundle.cc(357)] locale_file_path.empty() for locale
[0814/140156.010324:FATAL:zygote_host_impl_linux.cc(116)] No usable sandbox! Update your kernel or see https://chromium.googlesource.com/chromium/src/+/master/docs/linux_suid_sandbox_development.md for more information on developing with the SUID sandbox. If you want to live dangerously and need an immediate workaround, you can try using --no-sandbox.
#0 0x556382c83049
#1 0x556382c071c3
#2 0x556382c067de
#3 0x55638403652e
#4 0x556382bb6aeb
#5 0x55638403c7aa
#6 0x556382bb05f1
#7 0x556382ca67f8
#8 0x556382ca6885
#9 0x556382bef303
#10 0x7f97370893d5 __libc_start_main
#11 0x55638117302a _start

Received signal 6
#0 0x556382c83049
#1 0x556382c071c3
#2 0x556382c82bd1
#3 0x7f973872d5d0
#4 0x7f973709d207 __GI_raise
#5 0x7f973709e8f8 __GI_abort
#6 0x556382c81a05
#7 0x556382c06a21
#8 0x55638403652e
#9 0x556382bb6aeb
#10 0x55638403c7aa
#11 0x556382bb05f1
#12 0x556382ca67f8
#13 0x556382ca6885
#14 0x556382bef303
#15 0x7f97370893d5 __libc_start_main
#16 0x55638117302a _start
r8: 0000000000000000 r9: 726174735f636269 r10: 0000000000000008 r11: 0000000000000202
r12: 00007ffc4971f048 r13: 0000000000000161 r14: 00007ffc4971f9b0 r15: 00007ffc4971f9a8
di: 00000000000024c7 si: 00000000000024c7 bp: 00007ffc4971eff0 bx: 00001ade5caa8b80
dx: 0000000000000006 ax: 0000000000000000 cx: ffffffffffffffff sp: 00007ffc4971eeb8
ip: 00007f973709d207 efl: 0000000000000202 cgf: 0000000000000033 erf: 0000000000000000
trp: 0000000000000000 msk: 0000000000000000 cr2: 0000000000000000
[end of stack trace]
Calling _exit(1). Core file will not be generated.

TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md
]
log [14:01:56.049] [warning][reporting] See Chromium's log output at "/home/wiproadmin/kibana-7.3.0-linux-x86_64/data/headless_shell-linux/chrome_debug.log"
log [14:01:56.049] [warning][reporting] Reporting plugin self-check failed. Please check the Kibana Reporting settings. Error: Could not close browser client handle!
log [14:01:56.201] [info][listening] Server running at http://10.210.16.240:5601
log [14:01:56.212] [info][server][Kibana][http] http server running
log [14:01:56.215] [warning][task_manager] Task vis_telemetry "oss_telemetry-vis_telemetry" failed in attempt to run: [version_conflict_engine_exception] [oss_telemetry-vis_telemetry]: version conflict, required seqNo [185], primary term [10]. current document has seqNo [186] and primary term [10], with { index_uuid="vzJFT7KWQOqfLmKirBaFWg" & shard="0" & index=".kibana_task_manager" }
log [14:01:56.217] [info][status][plugin:spaces@7.3.0] Status changed from yellow to green - Ready

BR//
Sajal

What OS are running Kibana on?
Also, if you're not using the reporting feature after the upgrade, Kibana should work just fine for you, looks like the reporting modules is the one with the error.

HI Marius ,

OS details : CentOS version 7

What should i do to run Kibana properly

image

Can you check the guide here under "File permissions"? also the last one with "Unable to use Chromium sandbox".
https://www.elastic.co/guide/en/kibana/current/reporting-troubleshooting.html

Do you have this set?

Hi Len ,

No i didn't set . What is this for ?

Hi Marius ,

Still i am unable to use Chromium sandbox . What i have to set in CAP_SYS_ADMIN or which other parameter i need to set ?

Well, you're getting an error that it's not set. Try setting it and see if it fixes the larger problem.

Hi Marius ,

After installing plugins and giving file permission. Issue still persits

Hi Len ,

What should be the value for xpack.encrypted_saved_objects.encryptionKey : ?

Per the doc:
An arbitrary string of 32 characters or more that is used to encrypt credentials in a cookie. It is crucial that this key is not exposed to users of Kibana. By default, a value is automatically generated in memory. If you use that default behavior, all sessions are invalidated when Kibana restarts.