I have completed upgrading Elasticsearch cluster from 7.10.2 to 7.16.2. After completing Kibana upgrade from 7.10.2 to 7.16.2, I am now getting Kibana is not ready yet error. I verified the Elasticsearch cluster is in good health and upgrade completed successfully. I set Kibana logging.verbose = true but it didn't provide much information. Has anyone else been able to resolve this error message?
1 Like
Hi Vince,
Sorry to hear that. Do you have any customizations in kibana.yml? If so, can you share them?
Can you also share the latest logs from Kibana? We may find some helpful information there.
**Hi Nick, **
No customizations in Kibana.
# Kibana is served by a back end server. This setting specifies the port to use.
server.port: 5605
# 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: "0.0.0.0"
# 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 URLs of the Elasticsearch instances to use for all your queries.
Elasticsearch.hosts: ["https://elasticsearchbeta.corp.cdw.com:443"]
# 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: ""
Elasticsearch.password: ""
# 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: true
server.ssl.certificate: D:\Elastic\Kibana\config\elasticsearchbeta.corp.cdw.com.cer
server.ssl.key: D:\Elastic\Kibana\config\elasticsearchbeta.corp.cdw.com.key
server.ssl.supportedProtocols: ["TLSv1.2"]
# 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: [ "D:\Elastic\Kibana\config\CDWRootCA.pem", "D:\Elastic\Kibana\config\CDWCAMM.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: true
# 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"
there are quite few changes happened from 7.10.1 to 7.16
you need to check your kibana.log and it will give you hint on what setting you are missing or what setting is deprecated.
and post everything without comment line. as it is hard to read whole thing.
I am in the same boat as the original poster here. The logs don't seem to indicate anything much obvious.
{"type":"log","@timestamp":"2022-01-22T18:26:07+00:00","tags":["debug","plugins","dataVisualizer"],"pid":13643,"message":"Initializing plugin"}
{"type":"log","@timestamp":"2022-01-22T18:26:07+00:00","tags":["debug","plugins-system","standard"],"pid":13643,"message":"Setting up plugin \"ml\"..."}
{"type":"log","@timestamp":"2022-01-22T18:26:07+00:00","tags":["debug","plugins","ml"],"pid":13643,"message":"Initializing plugin"}
{"type":"log","@timestamp":"2022-01-22T18:26:07+00:00","tags":["debug","plugins-system","standard"],"pid":13643,"message":"Setting up plugin \"uptime\"..."}
{"type":"log","@timestamp":"2022-01-22T18:26:07+00:00","tags":["debug","plugins","uptime"],"pid":13643,"message":"Initializing plugin"}
{"type":"log","@timestamp":"2022-01-22T18:26:07+00:00","tags":["debug","plugins-system","standard"],"pid":13643,"message":"Setting up plugin \"securitySolution\"..."}
{"type":"log","@timestamp":"2022-01-22T18:26:07+00:00","tags":["debug","plugins","securitySolution"],"pid":13643,"message":"Initializing plugin"}
{"type":"log","@timestamp":"2022-01-22T18:26:07+00:00","tags":["debug","plugins","securitySolution"],"pid":13643,"message":"plugin initialized"}
{"type":"log","@timestamp":"2022-01-22T18:26:07+00:00","tags":["debug","plugins","securitySolution"],"pid":13643,"message":"plugin setup"}
{"type":"log","@timestamp":"2022-01-22T18:26:07+00:00","tags":["debug","plugins-system","standard"],"pid":13643,"message":"Setting up plugin \"infra\"..."}
{"type":"log","@timestamp":"2022-01-22T18:26:07+00:00","tags":["debug","plugins","infra"],"pid":13643,"message":"Initializing plugin"}
{"type":"log","@timestamp":"2022-01-22T18:26:07+00:00","tags":["debug","plugins-system","standard"],"pid":13643,"message":"Setting up plugin \"upgradeAssistant\"..."}
{"type":"log","@timestamp":"2022-01-22T18:26:07+00:00","tags":["debug","plugins","upgradeAssistant"],"pid":13643,"message":"Initializing plugin"}
{"type":"log","@timestamp":"2022-01-22T18:26:07+00:00","tags":["debug","plugins-system","standard"],"pid":13643,"message":"Setting up plugin \"monitoring\"..."}
The set-up I have is pretty simple.
Elasticsearch on a GCP VM - Running.
Logstash on the same GCP VM - Running.
Kibana Running on the same GCP VM - Running.
However when I access the GCP VM's http://external-ip:5601 = I get 'Kibana server not ready yet' error.
Version of Kibana: 7.16.3
Elasticsearch.yml output:
{
"name" : "elkserver",
"cluster_name" : "myelk",
"cluster_uuid" : "na",
"version" : {
"number" : "7.16.3",
"build_flavor" : "default",
"build_type" : "deb",
"build_hash" : "4e6e4eab2297e949ec994e688dad46290d018022",
"build_date" : "2022-01-06T23:43:02.825887787Z",
"build_snapshot" : false,
"lucene_version" : "8.10.1",
"minimum_wire_compatibility_version" : "6.8.0",
"minimum_index_compatibility_version" : "6.0.0-beta1"
},
"tagline" : "You Know, for Search"
}
what is your kibana configuration looks like
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.