Updated from Kibana 7.17.17 > 7.17.18 and now fails to Start

Elastic Stack Kibana
1

I upgraded my Kibana from 7.17.17-> 7.17.18 and now on startup received: FATAL Error: EACCES: permission denied, stat '/nonexistent/.config/puppeteer'.

If i downgrade to 7.17.17 , no issues.

Any ideas ?

2

Hello @tonybfj
can you share the full error message with us?

3

There is a similar error in v8 and v7.

4 
-- The unit kibana.service has entered the 'failed' state with result 'exit-code'.
Feb 29 09:01:52 <HOSTNAME> systemd[1]: Reloading.
Feb 29 09:01:54 <HOSTNAME> systemd[1]: Reloading.
Feb 29 09:01:55 <HOSTNAME> systemd[1]: Started Cluster Controlled kibana.
-- Subject: Unit kibana.service has finished start-up
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Unit kibana.service has finished starting up.
--
-- The start-up result is done.
Feb 29 09:02:03 <HOSTNAME> kibana[1349652]:  FATAL  Error: EACCES: permission denied, stat '/nonexistent/.config/puppeteer'
Feb 29 09:02:03 <HOSTNAME> systemd[1]: kibana.service: Main process exited, code=exited, status=1/FAILURE
Feb 29 09:02:03 <HOSTNAME> systemd[1]: kibana.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://access.redhat.com/support

Thats about it im afraid , kibana.log hasnt updated due to the fact the service doesnt fully start

5

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