Kibana Crashes Periodically

jleezer · June 19, 2019, 2:41pm

Hello,

I'm seeing an issue where Kibana periodically crashes.
OS: CentOS Linux release 7.6
Kibana/ES Version: 6.6.2, Base Version

Checking in the logs it appears that Kibana might be restarting itself periodically at the same time:

[37m  log  e[39m [10:00:55.591] [e[32minfoe[39m][e[93mstatuse[39m][plugin:elasticsearch@6.6.2] Status changed from red to green - Ready
e[31m error e[39m [22:52:48.272] [e[31merrore[39m][client][connection] e[31mError: Parse Errore[39m
e[31m error e[39m [22:53:16.545] [e[31merrore[39m][client][connection] e[31mError: Parse Errore[39m
e[31m error e[39m [22:53:16.547] [e[31merrore[39m][client][connection] e[31mError: Parse Errore[39m
e[31m error e[39m [22:53:16.549] [e[31merrore[39m][client][connection] e[31mError: Parse Errore[39m
e[31m error e[39m [22:53:16.552] [e[31merrore[39m][client][connection] e[31mError: Parse Errore[39m
e[31m error e[39m [22:53:16.571] [e[31merrore[39m][client][connection] e[31mError: Parse Errore[39m
e[31m error e[39m [22:53:16.582] [e[31merrore[39m][client][connection] e[31mError: Parse Errore[39m
e[31m error e[39m [22:53:16.584] [e[31merrore[39m][client][connection] e[31mError: Parse Errore[39m
e[31m error e[39m [22:53:16.932] [e[31merrore[39m][client][connection] e[31mError: Parse Errore[39m
e[31m error e[39m [22:53:16.934] [e[31merrore[39m][client][connection] e[31mError: Parse Errore[39m
e[31m error e[39m [22:53:17.128] [e[31merrore[39m][client][connection] e[31mError: Parse Errore[39m
e[31m error e[39m [22:53:17.137] [e[31merrore[39m][client][connection] e[31mError: Parse Errore[39m
e[31m error e[39m [22:53:20.833] [e[31merrore[39m][client][connection] e[31mError: Parse Errore[39m
e[31m error e[39m [22:53:29.946] [e[31merrore[39m][client][connection] e[31mError: Parse Errore[39m
events.js:174
      throw er; // Unhandled 'error' event
      ^

Error: read ECONNRESET
    at TCP.onStreamRead (internal/stream_base_commons.js:111:27)
Emitted 'error' event at:
    at emitErrorNT (internal/streams/destroy.js:82:8)
    at emitErrorAndCloseNT (internal/streams/destroy.js:50:3)
    at process._tickCallback (internal/process/next_tick.js:63:19)
e[37m  log  e[39m [22:53:47.795] [e[31mwarninge[39m][plugin] Skipping non-plugin directory at /usr/share/kibana/src/legacy/core_plugins/ems_util
e[37m  log  e[39m [22:53:48.475] [e[32minfoe[39m][e[93mstatuse[39m][plugin:kibana@6.6.2] Status changed from uninitialized to green - Ready
e[37m  log  e[39m [22:53:48.502] [e[32minfoe[39m][e[93mstatuse[39m][plugin:elasticsearch@6.6.2] Status changed from uninitialized to yellow - Waiting for Elasticsearch
e[37m  log  e[39m [22:53:48.518] [e[32minfoe[39m][e[93mstatuse[39m][plugin:opendistro-alerting@0.8.0.0] Status changed from uninitialized to green - Ready
e[37m  log  e[39m [22:53:48.524] [e[32minfoe[39m][e[93mstatuse[39m][plugin:console@6.6.2] Status changed from uninitialized to green - Ready
e[37m  log  e[39m [22:53:48.617] [e[32minfoe[39m][e[93mstatuse[39m][plugin:interpreter@6.6.2] Status changed from uninitialized to green - Ready
e[37m  log  e[39m [22:53:48.628] [e[32minfoe[39m][e[93mstatuse[39m][plugin:metrics@6.6.2] Status changed from uninitialized to green - Ready
e[37m  log  e[39m [22:53:48.783] [e[32minfoe[39m][e[93mstatuse[39m][plugin:timelion@6.6.2] Status changed from uninitialized to green - Ready
e[37m  log  e[39m [22:53:48.820] [e[32minfoe[39m][e[93mstatuse[39m][plugin:elasticsearch@6.6.2] Status changed from yellow to green - Ready
e[37m  log  e[39m [22:53:48.836] [e[32minfoe[39m][e[95mlisteninge[39m] Server running at http://0.0.0.0:5601
e[31m error e[39m [22:54:21.745] [e[31merrore[39m][client][connection] e[31mError: Parse Errore[39m
e[31m error e[39m [22:53:33.603] [e[31merrore[39m][client][connection] e[31mError: Parse Errore[39m
e[31m error e[39m [22:54:02.240] [e[31merrore[39m][client][connection] e[31mError: Parse Errore[39m
e[31m error e[39m [22:54:02.261] [e[31merrore[39m][client][connection] e[31mError: Parse Errore[39m
e[31m error e[39m [22:54:02.263] [e[31merrore[39m][client][connection] e[31mError: Parse Errore[39m
e[31m error e[39m [22:54:02.276] [e[31merrore[39m][client][connection] e[31mError: Parse Errore[39m
e[31m error e[39m [22:54:02.328] [e[31merrore[39m][client][connection] e[31mError: Parse Errore[39m
e[31m error e[39m [22:54:02.373] [e[31merrore[39m][client][connection] e[31mError: Parse Errore[39m
e[31m error e[39m [22:54:02.376] [e[31merrore[39m][client][connection] e[31mError: Parse Errore[39m
e[31m error e[39m [22:54:02.434] [e[31merrore[39m][client][connection] e[31mError: Parse Errore[39m
e[31m error e[39m [22:54:02.483] [e[31merrore[39m][client][connection] e[31mError: Parse Errore[39m
e[31m error e[39m [22:54:03.565] [e[31merrore[39m][client][connection] e[31mError: Parse Errore[39m
e[31m error e[39m [22:54:03.570] [e[31merrore[39m][client][connection] e[31mError: Parse Errore[39m
e[31m error e[39m [22:54:07.548] [e[31merrore[39m][client][connection] e[31mError: Parse Errore[39m
e[31m error e[39m [22:54:27.676] [e[31merrore[39m][client][connection] e[31mError: Parse Errore[39m
events.js:174
      throw er; // Unhandled 'error' event
      ^

Error: read ECONNRESET
    at TCP.onStreamRead (internal/stream_base_commons.js:111:27)
Emitted 'error' event at:
    at emitErrorNT (internal/streams/destroy.js:82:8)
    at emitErrorAndCloseNT (internal/streams/destroy.js:50:3)
    at process._tickCallback (internal/process/next_tick.js:63:19)
e[37m  log  e[39m [22:54:39.577] [e[31mwarninge[39m][plugin] Skipping non-plugin directory at /usr/share/kibana/src/legacy/core_plugins/ems_util
e[37m  log  e[39m [22:54:40.198] [e[32minfoe[39m][e[93mstatuse[39m][plugin:kibana@6.6.2] Status changed from uninitialized to green - Ready
e[37m  log  e[39m [22:54:40.221] [e[32minfoe[39m][e[93mstatuse[39m][plugin:elasticsearch@6.6.2] Status changed from uninitialized to yellow - Waiting for Elasticsearch
e[37m  log  e[39m [22:54:40.239] [e[32minfoe[39m][e[93mstatuse[39m][plugin:opendistro-alerting@0.8.0.0] Status changed from uninitialized to green - Ready
e[37m  log  e[39m [22:54:40.244] [e[32minfoe[39m][e[93mstatuse[39m][plugin:console@6.6.2] Status changed from uninitialized to green - Ready
e[37m  log  e[39m [22:54:40.322] [e[32minfoe[39m][e[93mstatuse[39m][plugin:interpreter@6.6.2] Status changed from uninitialized to green - Ready
e[37m  log  e[39m [22:54:40.330] [e[32minfoe[39m][e[93mstatuse[39m][plugin:metrics@6.6.2] Status changed from uninitialized to green - Ready
e[37m  log  e[39m [22:54:40.446] [e[32minfoe[39m][e[93mstatuse[39m][plugin:timelion@6.6.2] Status changed from uninitialized to green - Ready
e[37m  log  e[39m [22:54:40.486] [e[32minfoe[39m][e[93mstatuse[39m][plugin:elasticsearch@6.6.2] Status changed from yellow to green - Ready
e[37m  log  e[39m [22:54:40.505] [e[32minfoe[39m][e[95mlisteninge[39m] Server running at http://0.0.0.0:5601

Askia_Mohamed_Kadri · June 19, 2019, 2:44pm

You probably have an error you're missing in your kibana.yml

jleezer · June 19, 2019, 2:47pm

Thanks, the kibana.yml is super simple:

server.name: kibana
server.host: "0.0.0.0"
elasticsearch.hosts: ["http://clientnode1:9200","http://clientnode2:9200"]
elasticsearch.ssl.verificationMode: none
elasticsearch.requestHeadersWhitelist: ["securitytenant","Authorization"]

Askia_Mohamed_Kadri · June 19, 2019, 2:50pm

Is this the only parameters you have in you kibana.yml?

jleezer · June 19, 2019, 2:52pm

Yes those are the only parameters.

Askia_Mohamed_Kadri · June 19, 2019, 3:03pm

I suggest you to use the kibana.yml provided in the config repository and simply uncomment parameters you need because here you're missing parameter like server.port without which Kibana can't launch

Askia_Mohamed_Kadri · June 19, 2019, 3:05pm

Here is an example

# 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: "localhost"

# Enables you to specify a path to mount Kibana at if you are running behind a proxy.
# Use the `server.rewriteBasePath` setting to tell Kibana if it should remove the basePath
# from requests it receives, and to prevent a deprecation warning at startup.
# This setting cannot end in a slash.
#server.basePath: ""

# Specifies whether Kibana should rewrite requests that are prefixed with
# `server.basePath` or require that they are rewritten by your reverse proxy.
# This setting was effectively always `false` before Kibana 6.3 and will
# default to `true` starting in Kibana 7.0.
#server.rewriteBasePath: false

# 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://localhost: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"

# The default application to load.
#kibana.defaultAppId: "home"

# 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: "changeme"

# 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: 30000

# Time in milliseconds to wait for Elasticsearch at Kibana startup before retrying.
#elasticsearch.startupTimeout: 5000

# Logs queries sent to Elasticsearch. Requires logging.verbose set to true.
#elasticsearch.logQueries: false

# 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: stdout

# Set the value of this setting to true to suppress all logging output.
#logging.silent: false

# Set the value of this setting to true to suppress all logging output other than error messages.
#logging.quiet: false

# 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

# Specifies locale to be used for all localizable strings, dates and number formats.
#i18n.locale: "en"

jleezer · June 19, 2019, 3:30pm

Will Kibana not use the default server.port (5601) if one isn't specified? The app is running fine the problem is I find it crashed every day or two. The logs seem to imply that its restarting regularly (and it appears that its at the same time). This seems to indicate that there is a job or something that runs at that time that is causing issues. We're just using the basic version and haven't configured any monitoring/reporting. Just simple dashboards fed from elasticsearch.

jleezer · June 19, 2019, 3:31pm

Thanks I'll look through this and see if there is anything that should be added.

system · July 17, 2019, 3:31pm

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.

Topic		Replies	Views
Kibana 6.4.2 keeps crashing Kibana	8	1096	November 15, 2018
Kibana 5.1 keeps crashing Kibana	9	2685	September 4, 2017
Kibana 5.6.6 Crashing After 30s Kibana	14	714	December 23, 2019
Kibana requires a restart daily Kibana	2	359	December 11, 2019
Kibana 6.2.3 Restarts Constantly Kibana	23	3922	May 23, 2018

Kibana Crashes Periodically

Related Topics