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

Error: Unexpected config.watch("indexPatterns:warnAboutUnsupportedTimePatterns", fn) call on unrecognized configuration setting #14995

Closed
darkpixel opened this issue Nov 16, 2017 · 4 comments
Labels
bug Fixes for quality problems that affect the customer experience Team:Operations Team label for Operations Team

Comments

@darkpixel
Copy link

Kibana version:
6.0.0 x64

Elasticsearch version:
6.0.0

Server OS version:
Mint 18.1 (Based on Ubuntu 16.04)

Browser version:
Chrome 62.0.3202.89 x64

Browser OS version:
Mint 18.1 (Based on Ubuntu 16.04)

Original install method (e.g. download page, yum, from source, etc.):
Downloaded .deb packages from elastic.co

Description of the problem including expected versus actual behavior:
Upgraded Elasticsearch and Kibana from 5.6ish to 6.0 on a test machine.
Both packages installed successfully.
Kibana starts up with the menu bar on the left-hand side and a blank page on the right. It doesn't matter which menu I click on, nothing happens. Error message in dev console (see below).

Tried clearing cache, tried alternate browser (Firefox), no change.

Steps to reproduce:

  1. Open http://127.0.0.1:5601/ and the issue occurs

Errors in browser console (if relevant):

commons.bundle.js?v=15533:38 Error: Unexpected `config.watch("indexPatterns:warnAboutUnsupportedTimePatterns", fn)` call on unrecognized configuration setting "indexPatterns:warnAboutUnsupportedTimePatterns".
Setting an initial value via `config.set("indexPatterns:warnAboutUnsupportedTimePatterns", value)` before binding
any custom setting configuration watchers for "indexPatterns:warnAboutUnsupportedTimePatterns" may fix this issue.
    at watch (commons.bundle.js?v=15533:72)
    at Object.config.watch (commons.bundle.js?v=15533:72)
    at kibana.bundle.js?v=15533:1
    at commons.bundle.js?v=15533:2
    at baseForOwn (commons.bundle.js?v=15533:1)
    at Function.forOwn (commons.bundle.js?v=15533:2)
    at new BoundToConfigObj (kibana.bundle.js?v=15533:1)
    at Object.IsUserAwareOfUnsupportedTimePatternProvider (kibana.bundle.js?v=15533:28)
    at Object.invoke (commons.bundle.js?v=15533:36)
    at instantiate (commons.bundle.js?v=15533:86)
(anonymous) @ commons.bundle.js?v=15533:38
(anonymous) @ commons.bundle.js?v=15533:38
$apply @ commons.bundle.js?v=15533:39
(anonymous) @ commons.bundle.js?v=15533:35
invoke @ commons.bundle.js?v=15533:36
doBootstrap @ commons.bundle.js?v=15533:35
bootstrap @ commons.bundle.js?v=15533:35
chrome.bootstrap @ commons.bundle.js?v=15533:1
(anonymous) @ kibana.bundle.js?v=15533:1
__webpack_require__ @ commons.bundle.js?v=15533:1
window.webpackJsonp @ commons.bundle.js?v=15533:1
(anonymous) @ kibana.bundle.js?v=15533:1
kibana.bundle.js?v=15533:286 setting active api to [es_5_0]

Provide logs and/or server output (if relevant):

Nothing logged in stderr or stdout logs.

@tylersmalley tylersmalley added the bug Fixes for quality problems that affect the customer experience label Nov 16, 2017
@tylersmalley
Copy link
Contributor

@spalger, any ideas on this?

@spalger
Copy link
Contributor

spalger commented Nov 21, 2017

@darkpixel do you have any plugins installed? Maybe a proxy between Kibana and the browser? If you visit view-source:127.0.0.1:5601/app/kibana in Chrome do you see indexPatterns:warnAboutUnsupportedTimePatterns in a mess of HTML escaped quotes like this?:

image

The default settings are responsible for telling the UI which config settings are valid, and this specific setting is defined by Kibana in src/core_plugins/kibana/ui_setting_defaults.js, do you see the setting in there?

@darkpixel
Copy link
Author

darkpixel commented Nov 21, 2017

I think it was related to issue #13685.
The .kibana index was locked (as well as a few other indices). Since it was a test machine cluster I ended up blowing stuff away to get them to unlock. After I did that, Kibana started working properly.

@snide snide added the Team:Operations Team label for Operations Team label Aug 7, 2018
@snide
Copy link
Contributor

snide commented Aug 7, 2018

There hasn't been active discussion on this issue for quite awhile. We're doing a cleaning of our backlog. If you feel this closure is in error please feel free to reopen.

@snide snide closed this as completed Aug 7, 2018
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 Team:Operations Team label for Operations Team
Projects
None yet
Development

No branches or pull requests

4 participants