Skip to content
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

Closed
dave-wheeler opened this issue Jun 19, 2020 · 9 comments
Closed

Kibana fails with fatal error if xpack.reporting.enabled is false #69621

dave-wheeler opened this issue Jun 19, 2020 · 9 comments
Assignees
Labels
bug Fixes for quality problems that affect the customer experience Feature:Reporting:Framework Reporting issues pertaining to the overall framework needs-team Issues missing a team label

Comments

@dave-wheeler
Copy link

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):

Jun 19 10:10:00 hostname systemd[1]: Started Kibana - dashboard for Elasticsearch.
Jun 19 10:10:17 hostname node[185796]:  FATAL  Error: [config validation of [xpack.reporting].enabled]: definition for this key is missing
Jun 19 10:10:19 hostname systemd[1]: kibana.service: Main process exited, code=exited, status=1/FAILURE
Jun 19 10:10:19 hostname systemd[1]: kibana.service: Failed with result 'exit-code'.
Jun 19 10:10:19 hostname systemd[1]: kibana.service: Scheduled restart job, restart counter is at 1.

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.

@sastorsl
Copy link

sastorsl commented Jun 22, 2020

Kibana fails to start with both true and false in kibana.yml:

  • xpack.reporting.enabled: true
  • xpack.reporting.enabled: false

This is from a docker container running kibana version 7.8.0. The container ID is 7bd2290b8fd0.

Jun 22 12:40:44 <hostname> 7bd2290b8fd0[1559]: {"type":"log","@timestamp":"2020-06-22T10:40:44Z","tags":["fatal","root"],"pid":9,"message":"{ Error: [config validation of [xpack.reporting].enabled]: definition for this key is missing\n    at ObjectType.validate (/usr/share/kibana/node_modules/@kbn/config-schema/target/out/types/type.js:61:19)\n    at ConfigService.validateAtPath (/usr/share/kibana/src/core/server/config/config_service.js:188:19)\n    at MapSubscriber.getDistinctConfig.pipe.config [as project] (/usr/share/kibana/src/core/server/config/config_service.js:196:81)\n    at MapSubscriber._next (/usr/share/kibana/node_modules/rxjs/internal/operators/map.js:49:35)\n    at MapSubscriber.Subscriber.next (/usr/share/kibana/node_modules/rxjs/internal/Subscriber.js:66:18)\n    at DistinctUntilChangedSubscriber._next (/usr/share/kibana/node_modules/rxjs/internal/operators/distinctUntilChanged.js:69:30)\n    at DistinctUntilChangedSubscriber.Subscriber.next (/usr/share/kibana/node_modules/rxjs/internal/Subscriber.js:66:18)\n    at MapSubscriber._next (/usr/share/kibana/node_modules/rxjs/internal/operators/map.js:55:26)\n    at MapSubscriber.Subscriber.next (/usr/share/kibana/node_modules/rxjs/internal/Subscriber.js:66:18)\n    at ReplaySubject._subscribe (/usr/share/kibana/node_modules/rxjs/internal/ReplaySubject.js:76:28)\n    at ReplaySubject.Observable._trySubscribe (/usr/share/kibana/node_modules/rxjs/internal/Observable.js:44:25)\n    at ReplaySubject.Subject._trySubscribe (/usr/share/kibana/node_modules/rxjs/internal/Subject.js:102:51)\n    at ReplaySubject.Observable.subscribe (/usr/share/kibana/node_modules/rxjs/internal/Observable.js:30:22)\n    at MapSubscriber.shareReplayOperation (/usr/share/kibana/node_modules/rxjs/internal/operators/shareReplay.js:44:32)\n    at Observable.subscribe (/usr/share/kibana/node_modules/rxjs/internal/Observable.js:25:31)\n    at MapOperator.call (/usr/share/kibana/node_modules/rxjs/internal/operators/map.js:32:23)\n  cause:\n   { Error: definition for this key is missing\n       at ObjectType.onError (/usr/share/kibana/node_modules/@kbn/config-schema/target/out/types/type.js:86:20)\n       at type.Type.schema.error (/usr/share/kibana/node_modules/@kbn/config-schema/target/out/types/type.js:51:53)\n       at finish (/usr/share/kibana/node_modules/joi/lib/types/any/index.js:529:50)\n       at type._validate (/usr/share/kibana/node_modules/joi/lib/types/any/index.js:618:24)\n       at type._validateWithOptions (/usr/share/kibana/node_modules/joi/lib/types/any/index.js:674:29)\n       at module.exports.internals.Any.root.validate (/usr/share/kibana/node_modules/joi/lib/index.js:146:23)\n       at ObjectType.validate (/usr/share/kibana/node_modules/@kbn/config-schema/target/out/types/type.js:56:72)\n       at ConfigService.validateAtPath (/usr/share/kibana/src/core/server/config/config_service.js:188:19)\n       at MapSubscriber.getDistinctConfig.pipe.config [as project] (/usr/share/kibana/src/core/server/config/config_service.js:196:81)\n       at MapSubscriber._next (/usr/share/kibana/node_modules/rxjs/internal/operators/map.js:49:35)\n       at MapSubscriber.Subscriber.next (/usr/share/kibana/node_modules/rxjs/internal/Subscriber.js:66:18)\n       at DistinctUntilChangedSubscriber._next (/usr/share/kibana/node_modules/rxjs/internal/operators/distinctUntilChanged.js:69:30)\n       at DistinctUntilChangedSubscriber.Subscriber.next (/usr/share/kibana/node_modules/rxjs/internal/Subscriber.js:66:18)\n       at MapSubscriber._next (/usr/share/kibana/node_modules/rxjs/internal/operators/map.js:55:26)\n       at MapSubscriber.Subscriber.next (/usr/share/kibana/node_modules/rxjs/internal/Subscriber.js:66:18)\n       at ReplaySubject._subscribe (/usr/share/kibana/node_modules/rxjs/internal/ReplaySubject.js:76:28) cause: undefined, path: [ 'enabled' ] } }"}
Jun 22 12:40:44 <hostname> 7bd2290b8fd0[1559]:
Jun 22 12:40:44 <hostname> 7bd2290b8fd0[1559]: FATAL  Error: [config validation of [xpack.reporting].enabled]: definition for this key is missing
Jun 22 12:40:44 <hostname> 7bd2290b8fd0[1559]:

@timroes timroes added bug Fixes for quality problems that affect the customer experience Team:Reporting Services triage_needed labels Jun 22, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-reporting-services (Team:Reporting Services)

@tsullivan
Copy link
Member

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

@tsullivan
Copy link
Member

tsullivan commented Jun 22, 2020

original PR: #68288

backport for 7.8.1: #69645

@tsullivan
Copy link
Member

Fixed in #69645 for 7.8.1 release

@sastorsl
Copy link

@tsullivan just to be clear, does this mean we should add this option again (provided we want it)?

@tsullivan
Copy link
Member

If you want to configure Kibana to disable Reporting, unfortunately, you'll have to wait for 7.8.1 to come out so the xpack.reporting.enabled setting can be used without interfering with Kibana startup.

Until then, it is a known issue (7.8.0) that the xpack.reporting.enabled setting can't be accessed.

@sastorsl
Copy link

Roger that.

duncan-ncc added a commit to ukncsc/lme that referenced this issue Jul 2, 2020
duncan-ncc added a commit to ukncsc/lme that referenced this issue Jul 9, 2020
* 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
@cbluth
Copy link

cbluth commented Aug 12, 2020

@tsullivan
i am encountering this issue too.
what is the best way to upgrade, elasticsearch first, and then kibana?
or can i run 7.8.0 of elastic and 7.8.1 for kibana?

@sophiec20 sophiec20 added Feature:Reporting:Framework Reporting issues pertaining to the overall framework and removed (Deprecated) Team:Reporting Services labels Aug 21, 2024
@botelastic botelastic bot added the needs-team Issues missing a team label label Aug 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience Feature:Reporting:Framework Reporting issues pertaining to the overall framework needs-team Issues missing a team label
Projects
None yet
Development

No branches or pull requests

7 participants