-
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 missing styles after optimization #11588
Comments
Certain settings in kibana will cause it to rebundle assets and occasionally this process goes wrong. We're tracking the removal of settings and plugins rebundling here. Does clearing out the |
Thanks for your reply. In the meantime I figured out that re-optimizing the bundle (by removing and reinstalling XPack in Kibana) was the way to go. If the problem re-occurs I'll try clearing the folder. Is there b.t.w. (off-topic) a way to trigger a optimize and cache bundles manually (like a command line tool or option)? |
There isn't anything explicit. Installing a plugin, removing the |
I renamed this for now, there's a few similar errors floating around with the same root cause. #9369 is another. It may be worth consolidating. |
Closing this, as a workaround exists to trigger an optimize and cache of the bundles manually. Feel free to re-open if this needs more discussion |
Kibana version:
5.3.1
Elasticsearch version:
5.3.1
Server OS version:
Ubuntu 16.04 LTS
Browser version:
Chrome 57
Browser OS version:
Windows 10
Original install method (e.g. download page, yum, from source, etc.):
.deb
Description of the problem including expected versus actual behavior:
I want to permanently disable the Xpack opt-out and dismiss messages that are shown after Kibana logon. So Iv'e updated the Kibana config:
xpack.monitoring.report_stats: false
Restart of Kibana took a long time: "message":"Optimizing and caching bundles for graph, monitoring, kibana, timelion, login, logout and status_page."
After this the navigation menu is completeky screwed up:
Removing the config line doens't help: the dismiss message will be shown again but the formatting is still screwed up.
Steps to reproduce:
The text was updated successfully, but these errors were encountered: