-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kibana fails with fatal error if xpack.reporting.enabled is false #69621
Comments
Kibana fails to start with both true and false in
This is from a docker container running kibana version 7.8.0. The container ID is 7bd2290b8fd0.
|
Pinging @elastic/kibana-reporting-services (Team:Reporting Services) |
Apologies, this bug came about from the Reporting plugin migration to the new Kibana platform. It is fixed in 7.x but looks like it was fixed after the 7.8 release cut off. The fix will be in 7.8.1 |
Fixed in #69645 for 7.8.1 release |
@tsullivan just to be clear, does this mean we should add this option again (provided we want it)? |
If you want to configure Kibana to disable Reporting, unfortunately, you'll have to wait for 7.8.1 to come out so the Until then, it is a known issue (7.8.0) that the |
Roger that. |
* Updating winlogbeat to support the Elastic Common Schema * updating documentation for new winlogbeat files * Update to ES 7.8 * Updating deployment questions to make them more clear * Providing instructions to update winlogbeat * Adding syslog support * Adding directory creation command * Removing reporting settings as this is currently broken, Fixed in the unreleased 7.8.1 elastic/kibana#69621 * The module files are now actually shipped with ES 7.8.0 so not including them in the git, Removing the version named directory for install as this would break updates. * Removing module files that are no longer needed * changing install script to reflect the fact that network and hashing is now suitable in our recommended sysmon config * Updating winlogbeat to support ECS with forwarded events, Fixes the multi script issues * Updating logstash config to support syslog via pipelines * Adding pipeline upgrade paths and updating documentation * Updating Documentation and screenshots for v0.3 * Adding more screenshots of v0.3 * Adding kibana saved objects encryption key settings * Correcting variable name * adding screenshots for siem activation * Updating siem instructions and adding more screenshots * Removing NGINX mention as this was removed in v0.2
@tsullivan |
Kibana version: 7.8.0
Elasticsearch version: 7.8.0
Server OS version: Archlinux
Original install method (e.g. download page, yum, from source, etc.): Arch AUR package
Describe the bug: If xpack.reporting.enabled is false, kibana will never start successfully.
Steps to reproduce:
1.Add the following to kibana.yml:
xpack.reporting.enabled: false
2.Try to start kibana
Expected behavior:
Kibana starts successfully.
Provide logs and/or server output (if relevant):
It's unclear to me if this setting is still valid. The breaking changes notes for elasticsearch 7.8 mentions "Several X-Pack settings no longer have any effect and are deprecated...are always enabled for the default distribution and the following settings no longer have any effect." However, xpack.reporting.enabled is not one of the settings listed, nor does the Kibana documentation say anything about this setting being deprecated or invalid.
The text was updated successfully, but these errors were encountered: