Closed opoplawski closed 4 years ago
looks like more than 1 plugin declare that they own the opendistro_security.*
config, can you verify installed plugins? Kibana log should show what plugins are discovered during initialization process
I set 'logging.verbose: true' in /etc/kibana/kibana.yml. Then looking at the discovered plugin messages I see:
Nov 04 07:47:16 localhost kibana[178147]: {"type":"log","@timestamp":"2020-11-04T15:47:16Z","tags":["debug","plugins-discovery"],"pid":178147,"message":"Successfully discovered plugin \"opendistroSecurity\" at \"/usr/share/kibana/plugins/.plugin.installing\""}
Nov 04 07:47:16 localhost kibana[178147]: {"type":"log","@timestamp":"2020-11-04T15:47:16Z","tags":["debug","plugins-discovery"],"pid":178147,"message":"Successfully discovered plugin \"opendistroSecurity\" at \"/usr/share/kibana/plugins/opendistro_security\""}
That appears to be the only plugin discovered in .plugin.installing. Should I just delete that directory?
Looks like this is leftover from an attempt to install an update to opendistro_security as mentioned here: https://github.com/opendistro-for-elasticsearch/security-kibana-plugin/issues/503#issuecomment-707998584
Presumably that should have cleaned up the /usr/share/kibana/plugins/.plugin.installing directory?
We suffered a disk full condition on one of our elastic nodes. After getting that dealt with, kibana is no longer starting:
Any suggestions for how to resolve this? Thanks