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 4.0.0 BETA1 - Editing and putting visualizations on dashboards results in error #1557

Closed
mycrEEpy opened this issue Oct 7, 2014 · 16 comments
Assignees
Labels
bug Fixes for quality problems that affect the customer experience not reproducible
Milestone

Comments

@mycrEEpy
Copy link

mycrEEpy commented Oct 7, 2014

Everytime i create a visualization, save it and enter the editing mode or put it onto a dashboard i get the following error:

Fatal Error

aggConfig.vis.indexPattern.fields is undefined

FieldAggParamFactory/FieldAggParam.prototype.deserialize@http://xxx.xxx.xxx.xxx:5601/index.js:103023
AggConfigFactory/AggConfig.prototype.fillDefaults/<@http://xxx.xxx.xxx.xxx:5601/index.js:104513
AggConfigFactory/AggConfig.prototype.fillDefaults@http://xxx.xxx.xxx.xxx:5601/index.js:104502
AggConfig@http://xxx.xxx.xxx.xxx:5601/index.js:104487
AggConfigsFactory/AggConfigs/<.initialSet<@http://xxx.xxx.xxx.xxx:5601/index.js:104620
AggConfigs@http://xxx.xxx.xxx.xxx:5601/index.js:104618
VisFactory/Vis.prototype.setState@http://xxx.xxx.xxx.xxx:5601/index.js:104757
Vis@http://xxx.xxx.xxx.xxx:5601/index.js:104706
SavedVis.prototype._createVis@http://xxx.xxx.xxx.xxx:5601/index.js:105995
SavedVis.prototype._afterEsResp/<@http://xxx.xxx.xxx.xxx:5601/index.js:105974
qFactory/defer/deferred.promise.then/wrappedCallback@http://xxx.xxx.xxx.xxx:5601/index.js:20763
qFactory/ref/<.then/<@http://xxx.xxx.xxx.xxx:5601/index.js:20849
Scope.prototype.$eval@http://xxx.xxx.xxx.xxx:5601/index.js:21892
Scope.prototype.$digest@http://xxx.xxx.xxx.xxx:5601/index.js:21704
Scope.prototype.$apply@http://xxx.xxx.xxx.xxx:5601/index.js:21996
done@http://xxx.xxx.xxx.xxx:5601/index.js:17569
completeRequest@http://xxx.xxx.xxx.xxx:5601/index.js:17783
createHttpBackend/</xhr.onreadystatechange@http://xxx.xxx.xxx.xxx:5601/index.js:17726
@mycrEEpy
Copy link
Author

mycrEEpy commented Oct 7, 2014

Deleting the kibana-int index and restarting Kibana now fixed the problem.

@mycrEEpy
Copy link
Author

mycrEEpy commented Oct 7, 2014

After creating some visualizations the error occurs again.

@TiNico22
Copy link

TiNico22 commented Oct 7, 2014

Having the same issue.
Did you used a fresh new install Kibana 4 + ES1.4 or migrate ES1.3 to 1.4 for testing Kibana 4 ?
Or did you delete some older indices ?

@mycrEEpy
Copy link
Author

mycrEEpy commented Oct 7, 2014

At first i created a new 1.4 Cluster with Kibana 4 and imported the shakespeare.json and got the error.
Then i tried copying the data from one of our pre 1.4 Clusters to a new 1.4 Cluster which worked for a while but after some time the error occured again.

@TiNico22
Copy link

TiNico22 commented Oct 7, 2014

For me, it seems that I have seen the error for the first time after tring to use a former kibana 3 dashbord (just to see if it can work ...), I was using kibana 3 in from of ES 1.4 since few days. I was also accesing, in the same browser kibana3 & 4 against the same ES 1.4.

@rashidkpc
Copy link
Contributor

Next time this occurs can you try deleting your index pattern and recreating it to see if that solves the problem? I think it might be related to another issue that we believe to be a race condition.

@rashidkpc rashidkpc added bug Fixes for quality problems that affect the customer experience not reproducible labels Oct 7, 2014
@CullyB
Copy link

CullyB commented Oct 7, 2014

I can recreate this every time I create a visualization. I see the blue message bar indicating that the visualization has been saved - then a brief moment later (when it tries to refresh/reload the saved index?) the error message pops up.

I've tried deleting the visualization and recreating without success; I've also tried loading the saved visualization from a different browser but without success.

@mycrEEpy
Copy link
Author

mycrEEpy commented Oct 8, 2014

@rashidkpc deleting the index pattern and recreating it fixes the problem. i will try to reproduce the error and inform you how to do it.

@mycrEEpy
Copy link
Author

mycrEEpy commented Oct 8, 2014

Reproduced it but have no clue which triggers it.

Other fact:
Firefox throws the error in the fist comment but Chrome does throw an other error

Fatal Error

Cannot read property 'byName' of undefined

TypeError: Cannot read property 'byName' of undefined
    at BaseAggParam.FieldAggParamFactory.FieldAggParam.deserialize (http://xxx.xxx.xxx.xxx:5601/index.js:103023:47)
    at http://xxx.xxx.xxx.xxx:5601/index.js:104513:28
    at Array.forEach (native)
    at AggConfigFactory.AggConfig.fillDefaults (http://xxx.xxx.xxx.xxx:5601/index.js:104502:27)
    at new AggConfig (http://xxx.xxx.xxx.xxx:5601/index.js:104487:12)
    at http://xxx.xxx.xxx.xxx:5601/index.js:104620:18
    at Array.map (native)
    at Registry.AggConfigs (http://xxx.xxx.xxx.xxx:5601/index.js:104618:42)
    at VisFactory.Vis.setState (http://xxx.xxx.xxx.xxx:5601/index.js:104757:19)
    at new Vis (http://xxx.xxx.xxx.xxx:5601/index.js:104706:12)

@happy49sky
Copy link

After create some visualisation, the error occurs again. And old saved ones are also unavailable.

@mycrEEpy
Copy link
Author

mycrEEpy commented Oct 8, 2014

After only using Chrome for a while now i had no errors.
But as soon as i access Kibana 4 with Firefox the errors occur again.
I'm using Firefox Version 24.0 as only this is supported by our company.

@happy49sky
Copy link

Is it related to browser version ? Both chrome and safari don't work.

@mycrEEpy
Copy link
Author

mycrEEpy commented Oct 8, 2014

Now it's also happening with chrome.

@mycrEEpy
Copy link
Author

mycrEEpy commented Oct 8, 2014

Seems to be a duplicate of #1561 with just another error message in different browsers.

@TiNico22
Copy link

TiNico22 commented Oct 8, 2014

I am running FF31 esr under Linux

@spalger spalger self-assigned this Oct 8, 2014
@spalger spalger added this to the 4.0.0-BETA2 milestone Oct 8, 2014
@spalger
Copy link
Contributor

spalger commented Oct 8, 2014

I have no doubt that this is caused by the same bug causing #1561. Closing for now.

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 not reproducible
Projects
None yet
Development

No branches or pull requests

6 participants