# Kibana keeps popping new messages on console **URL:** \ **Category:** Kibana\ **Created:** [January 29, 2019, 1:09pm UTC](https://discuss.elastic.co/t/kibana-keeps-popping-new-messages-on-console/166175 "2019-01-29T13:09:41Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![nitish\_upadhyay1](https://avatars.discourse-cdn.com/v4/letter/n/8c91f0/32.png) [@nitish\_upadhyay1](https://discuss.elastic.co/u/nitish_upadhyay1)\ **Post date:** [January 29, 2019, 1:09pm UTC](https://discuss.elastic.co/t/kibana-keeps-popping-new-messages-on-console/166175/1 "2019-01-29T13:09:41Z")
Hi Everyone, Greetings. Actually, i have been trying to use latest kibana in a 3 machine cluster. But after configuration, when i try to start kibana and access it from browser, some messages keeps popping on my terminal console. The version is kibana-6.5.4. while befire this i used kibana-6.2.1, where i never experienced this issue. I tried checking into github, but the files they are referring to like .babelrc are nowhere to be found in kibana or node\_modules or x-pack. Please someone help me with this. 1. Browserslist: caniuse-lite is outdated. Please run next command `npm update caniuse-lite browserslist` 2. [BABEL] Note: The code generator has deoptimised the styling of "/mnt/gene3/Analyze/packages/kibana-6.5.4-linux-x86\_64/node\_modules/x-pack/plugins/canvas/canvas\_plugin/types/all.js" as it exceeds the max of "500KB". ---
**Author:** ![Brandon\_Kobel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/brandon_kobel/32/14829_2.png) [@Brandon\_Kobel](https://discuss.elastic.co/u/Brandon_Kobel)\ **Post date:** [January 29, 2019, 5:34pm UTC](https://discuss.elastic.co/t/kibana-keeps-popping-new-messages-on-console/166175/2 "2019-01-29T17:34:53Z")
Hey @nitish_upadhyay1, are you running kibana-6.5.4 from [https://www.elastic.co/downloads/past-releases/kibana-6-5-4](https://www.elastic.co/downloads/past-releases/kibana-6-5-4)? Which messages are you seeing output, and what does your kibana.yml look like? ---
**Author:** ![nitish\_upadhyay1](https://avatars.discourse-cdn.com/v4/letter/n/8c91f0/32.png) [@nitish\_upadhyay1](https://discuss.elastic.co/u/nitish_upadhyay1)\ **Post date:** [January 30, 2019, 8:04am UTC](https://discuss.elastic.co/t/kibana-keeps-popping-new-messages-on-console/166175/3 "2019-01-30T08:04:49Z")
Hi @Brandon_Kobel, Thanks for the response. Yeah i have been using the kibana from the link that you have mentioned. Here i am attaching my kibana.yml file. # Kibana is served by a back end server. This setting specifies the port to use. #server.port: 5601 # Specifies the address to which the Kibana server will bind. IP addresses and host names are both valid values. # The default is 'localhost', which usually means remote machines will not be able to connect. # To allow connections from remote users, set this parameter to a non-loopback address. server.host: "10.21.0.104" # Enables you to specify a path to mount Kibana at if you are running behind a proxy. This only affects # the URLs generated by Kibana, your proxy is expected to remove the basePath value before forwarding requests # to Kibana. This setting cannot end in a slash. #server.basePath: "" # The maximum payload size in bytes for incoming server requests. #server.maxPayloadBytes: 1048576 # The Kibana server's name. This is used for display purposes. #server.name: "your-hostname" # The URL of the Elasticsearch instance to use for all your queries. elasticsearch.url: "[http://10.21.0.104:9200](http://10.21.0.104:9200)" # When this setting's value is true Kibana uses the hostname specified in the server.host # setting. When the value of this setting is false, Kibana uses the hostname of the host # that connects to this Kibana instance. #elasticsearch.preserveHost: true # Kibana uses an index in Elasticsearch to store saved searches, visualizations and # dashboards. Kibana creates a new index if the index doesn't already exist. #kibana.index: ".kibana-6" # The default application to load. #kibana.defaultAppId: "discover" # If your Elasticsearch is protected with basic authentication, these settings provide # the username and password that the Kibana server uses to perform maintenance on the Kibana # index at startup. Your Kibana users still need to authenticate with Elasticsearch, which # is proxied through the Kibana server. elasticsearch.username: "elastic" elasticsearch.password: "elastic" # Enables SSL and paths to the PEM-format SSL certificate and SSL key files, respectively. # These settings enable SSL for outgoing requests from the Kibana server to the browser. #server.ssl.enabled: false #server.ssl.certificate: /path/to/your/server.crt #server.ssl.key: /path/to/your/server.key # Optional settings that provide the paths to the PEM-format SSL certificate and key files. # These files validate that your Elasticsearch backend uses the same key files. #elasticsearch.ssl.certificate: /path/to/your/client.crt #elasticsearch.ssl.key: /path/to/your/client.key # Optional setting that enables you to specify a path to the PEM file for the certificate # authority for your Elasticsearch instance. #elasticsearch.ssl.certificateAuthorities: ["/path/to/your/CA.pem"] # To disregard the validity of SSL certificates, change this setting's value to 'none'. #elasticsearch.ssl.verificationMode: full # Time in milliseconds to wait for Elasticsearch to respond to pings. Defaults to the value of # the elasticsearch.requestTimeout setting. #elasticsearch.pingTimeout: 1500 # Time in milliseconds to wait for responses from the back end or Elasticsearch. This value # must be a positive integer. #elasticsearch.requestTimeout: 30000 # List of Kibana client-side headers to send to Elasticsearch. To send _no_ client-side # headers, set this value to (an empty list). #elasticsearch.requestHeadersWhitelist: [authorization] # Header names and values that are sent to Elasticsearch. Any custom headers cannot be overwritten # by client-side headers, regardless of the elasticsearch.requestHeadersWhitelist configuration. #elasticsearch.customHeaders: {} # Time in milliseconds for Elasticsearch to wait for responses from shards. Set to 0 to disable. #elasticsearch.shardTimeout: 0 # Time in milliseconds to wait for Elasticsearch at Kibana startup before retrying. #elasticsearch.startupTimeout: 5000 # Specifies the path where Kibana creates the process ID file. #pid.file: /var/run/kibana.pid # Enables you specify a file where Kibana stores log output. logging.dest: "/mnt/gene3/Analyze/logs/kibana.log" # Set the value of this setting to true to suppress all logging output. logging.silent: true # Set the value of this setting to true to suppress all logging output other than error messages. logging.quiet: true # Set the value of this setting to true to log all events, including system usage information # and all requests. logging.verbose: false # Set the interval in milliseconds to sample system and process performance # metrics. Minimum is 100ms. Defaults to 5000. #ops.interval: 5000 # The default locale. This locale can be used in certain circumstances to substitute any missing # translations. #i18n.defaultLocale: "en" ---
**Author:** ![nitish\_upadhyay1](https://avatars.discourse-cdn.com/v4/letter/n/8c91f0/32.png) [@nitish\_upadhyay1](https://discuss.elastic.co/u/nitish_upadhyay1)\ **Post date:** [January 30, 2019, 8:08am UTC](https://discuss.elastic.co/t/kibana-keeps-popping-new-messages-on-console/166175/4 "2019-01-30T08:08:08Z")
I am attaching the screenshots for the messages. ![screenshot-1](https://us1.discourse-cdn.com/elastic/original/3X/e/d/ed2195dc361d1804a68ab9cc9a72a82ed1ffc644.png) ![image-2019-01-21-17-20-35-528](https://us1.discourse-cdn.com/elastic/original/3X/3/6/3608c142e3bceedb34f74f782f94ef7dc976ee13.png) ---
**Author:** ![Brandon\_Kobel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/brandon_kobel/32/14829_2.png) [@Brandon\_Kobel](https://discuss.elastic.co/u/Brandon_Kobel)\ **Post date:** [January 30, 2019, 2:35pm UTC](https://discuss.elastic.co/t/kibana-keeps-popping-new-messages-on-console/166175/5 "2019-01-30T14:35:36Z")
Hey @nitish_upadhyay1, those log messages should cause you any concern. The "Browserslist: caniuse" log message will be resolved in 6.7 by [https://github.com/elastic/kibana/pull/29358](https://github.com/elastic/kibana/pull/29358), and feel free to create an issue [here](https://github.com/elastic/kibana/issues/new/choose) to address the log message about the deoptimized styling. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [February 27, 2019, 2:35pm UTC](https://discuss.elastic.co/t/kibana-keeps-popping-new-messages-on-console/166175/6 "2019-02-27T14:35:45Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.