Found "Kibana server is not ready yet" after configured kibana

Elastic Stack Kibana
1

After setup of kibana and configure the yml file in my linux box, I got message "Kibana server is not ready yet" once I access to http://myipaddress:5601

And here is my kibana.yml config file.
Many thanks all. :slight_smile:

#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.0.3.132

# 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

# Specifies the public URL at which Kibana is available for end users. If
# `server.basePath` is configured this URL should end with the same basePath.
#server.publicBaseUrl: ""

# The maximum payload size in bytes for incoming server requests.
#server.maxPayload: 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: http://10.0.3.132:9200

# 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: "kibana_system"
#elasticsearch.password: "pass"

# Kibana can also authenticate to Elasticsearch via "service account tokens".
# If may use this token instead of a username/password.
# elasticsearch.serviceAccountToken: "my_token"



# 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 are used to verify the identity of Kibana to Elasticsearch and are required when
# xpack.security.http.ssl.client_authentication in Elasticsearch is set to required.
#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

# 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: /run/kibana/kibana.pid

# Enables you to 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.
# Supported languages are the following: English - en , by default , Chinese - zh-CN .
#i18n.locale: "en"
2

Hi @fanfan01127 can you check your kibana log see what the messages say? Do you have Elasticsearch running?

3

Yes I did setup the Elasticsearch earlier and I can see the configuration via port 9200.
Since I'm a newbie to use linux and elastic stack, may I ask where I can check the kibana log please?
Thank you.

4

Sure, What version are you using? What linux package did you use?

Depending how you installed you can find the directory paths, click on the one you chose and scroll to the bottom it will show the directories.

Here is also a nice getting started guide:

Those are for version 8.2, but there is a selector to the right if you are using a different version.

5

Hi,
I am currently using kibana version 8.2 as shown below.
image

I can locate the logs in there but unable to view/open it. May I ask how can I see that properly please? :slight_smile: Many thanks.

6

Hi @fanfan01127 , what error do you get when you try to view it? Can you check permissions of the directory and the user currently logged in? Did you provision logging for Kibana? If not, please also add these settings and restart Kibana.

7

Hi @LizaD
Actually I don't see any logs from that folder just like below. May I ask where else I can dig out the log so I can share it in here for further troubleshooting. Many thanks.
image

Sorry about that I am quite a newbie on using Linux.

Kind regards,
fanfan01127

8

Just an update, I just managed to view the log under \var\log\kibana as below.
Many thanks :slight_smile:

{"type":"log","@timestamp":"2022-05-09T15:30:31+01:00","tags":["info","plugins-service"],"pid":48672,"message":"Plugin \"metricsEntities\" is disabled."}
{"type":"log","@timestamp":"2022-05-09T15:30:31+01:00","tags":["info","http","server","Preboot"],"pid":48672,"message":"http server running at http://10.0.3.132:5601"}
{"type":"log","@timestamp":"2022-05-09T15:30:31+01:00","tags":["warning","config","deprecation"],"pid":48672,"message":"\"logging.dest\" has been deprecated and will be removed in 8.0. To set the destination moving forward, you can use the \"console\" appender in your logging configuration or define a custom one."}
{"type":"log","@timestamp":"2022-05-09T15:30:31+01:00","tags":["warning","config","deprecation"],"pid":48672,"message":"Starting in 8.0, the Kibana logging format will be changing. This may affect you if you are doing any special handling of your Kibana logs, such as ingesting logs into Elasticsearch for further analysis. If you are using the new logging configuration, you are already receiving logs in both old and new formats, and the old format will simply be going away. If you are not yet using the new logging configuration, the log format will change upon upgrade to 8.0. Beginning in 8.0, the format of JSON logs will be ECS-compatible JSON, and the default pattern log format will be configurable with our new logging system. Please refer to the documentation for more information about the new logging format."}
{"type":"log","@timestamp":"2022-05-09T15:30:31+01:00","tags":["warning","config","deprecation"],"pid":48672,"message":"The default mechanism for Reporting privileges will work differently in future versions, which will affect the behavior of this cluster. Set \"xpack.reporting.roles.enabled\" to \"false\" to adopt the future behavior before upgrading."}
{"type":"log","@timestamp":"2022-05-09T15:30:31+01:00","tags":["warning","config","deprecation"],"pid":48672,"message":"User sessions will automatically time out after 8 hours of inactivity starting in 8.0. Override this value to change the timeout."}
{"type":"log","@timestamp":"2022-05-09T15:30:31+01:00","tags":["warning","config","deprecation"],"pid":48672,"message":"Users are automatically required to log in again after 30 days starting in 8.0. Override this value to change the timeout."}
{"type":"log","@timestamp":"2022-05-09T15:30:31+01:00","tags":["info","plugins-system","standard"],"pid":48672,"message":"Setting up [113] plugins: [translations,licensing,globalSearch,globalSearchProviders,features,licenseApiGuard,code,usageCollection,xpackLegacy,taskManager,telemetryCollectionManager,telemetryCollectionXpack,kibanaUsageCollection,share,embeddable,uiActionsEnhanced,screenshotMode,banners,telemetry,newsfeed,mapsEms,mapsLegacy,kibanaLegacy,fieldFormats,expressions,dataViews,charts,esUiShared,bfetch,data,savedObjects,presentationUtil,expressionShape,expressionRevealImage,expressionRepeatImage,expressionMetric,expressionImage,customIntegrations,home,searchprofiler,painlessLab,grokdebugger,management,watcher,licenseManagement,advancedSettings,spaces,security,savedObjectsTagging,reporting,canvas,lists,ingestPipelines,fileUpload,encryptedSavedObjects,dataEnhanced,cloud,snapshotRestore,eventLog,actions,alerting,triggersActionsUi,transform,stackAlerts,ruleRegistry,visualizations,visTypeXy,visTypeVislib,visTypeVega,visTypeTimelion,visTypeTagcloud,visTypeTable,visTypePie,visTypeMetric,visTypeMarkdown,tileMap,regionMap,expressionTagcloud,expressionMetricVis,console,graph,fleet,indexManagement,remoteClusters,crossClusterReplication,indexLifecycleManagement,dashboard,maps,dashboardMode,dashboardEnhanced,visualize,visTypeTimeseries,rollup,indexPatternFieldEditor,lens,cases,timelines,discover,osquery,observability,discoverEnhanced,dataVisualizer,ml,uptime,securitySolution,infra,upgradeAssistant,monitoring,logstash,enterpriseSearch,apm,savedObjectsManagement,indexPatternManagement]"}
{"type":"log","@timestamp":"2022-05-09T15:30:31+01:00","tags":["info","plugins","taskManager"],"pid":48672,"message":"TaskManager is identified by the Kibana UUID: 88abbb38-16d9-4e2a-b046-544327e21ffc"}
{"type":"log","@timestamp":"2022-05-09T15:30:31+01:00","tags":["warning","plugins","security","config"],"pid":48672,"message":"Generating a random key for xpack.security.encryptionKey. To prevent sessions from being invalidated on restart, please set xpack.security.encryptionKey in the kibana.yml or use the bin/kibana-encryption-keys command."}
{"type":"log","@timestamp":"2022-05-09T15:30:31+01:00","tags":["warning","plugins","security","config"],"pid":48672,"message":"Session cookies will be transmitted over insecure connections. This is not recommended."}
{"type":"log","@timestamp":"2022-05-09T15:30:31+01:00","tags":["warning","plugins","security","config"],"pid":48672,"message":"Generating a random key for xpack.security.encryptionKey. To prevent sessions from being invalidated on restart, please set xpack.security.encryptionKey in the kibana.yml or use the bin/kibana-encryption-keys command."}
{"type":"log","@timestamp":"2022-05-09T15:30:31+01:00","tags":["warning","plugins","security","config"],"pid":48672,"message":"Session cookies will be transmitted over insecure connections. This is not recommended."}
{"type":"log","@timestamp":"2022-05-09T15:30:31+01:00","tags":["warning","plugins","reporting","config"],"pid":48672,"message":"Generating a random key for xpack.reporting.encryptionKey. To prevent sessions from being invalidated on restart, please set xpack.reporting.encryptionKey in the kibana.yml or use the bin/kibana-encryption-keys command."}
{"type":"log","@timestamp":"2022-05-09T15:30:31+01:00","tags":["warning","plugins","encryptedSavedObjects"],"pid":48672,"message":"Saved objects encryption key is not set. This will severely limit Kibana functionality. Please set xpack.encryptedSavedObjects.encryptionKey in the kibana.yml or use the bin/kibana-encryption-keys command."}
{"type":"log","@timestamp":"2022-05-09T15:30:31+01:00","tags":["warning","plugins","actions"],"pid":48672,"message":"APIs are disabled because the Encrypted Saved Objects plugin is missing encryption key. Please set xpack.encryptedSavedObjects.encryptionKey in the kibana.yml or use the bin/kibana-encryption-keys command."}
{"type":"log","@timestamp":"2022-05-09T15:30:31+01:00","tags":["warning","plugins","alerting"],"pid":48672,"message":"APIs are disabled because the Encrypted Saved Objects plugin is missing encryption key. Please set xpack.encryptedSavedObjects.encryptionKey in the kibana.yml or use the bin/kibana-encryption-keys command."}
{"type":"log","@timestamp":"2022-05-09T15:30:31+01:00","tags":["info","plugins","ruleRegistry"],"pid":48672,"message":"Installing common resources shared between all indices"}
{"type":"log","@timestamp":"2022-05-09T15:30:32+01:00","tags":["warning","plugins","reporting","config"],"pid":48672,"message":"Chromium sandbox provides an additional layer of protection, but is not supported for Linux Red Hat Linux 8.2 OS. Automatically setting 'xpack.reporting.capture.browser.chromium.disableSandbox: true'."}
{"type":"log","@timestamp":"2022-05-09T15:30:32+01:00","tags":["error","elasticsearch-service"],"pid":48672,"message":"Unable to retrieve version information from Elasticsearch nodes. self signed certificate in certificate chain"}
{"type":"log","@timestamp":"2022-05-09T15:50:32+01:00","tags":["error","plugins","ruleRegistry"],"pid":48672,"message":"Error: Timeout: it took more than 1200000ms\n    at Timeout._onTimeout (/usr/share/kibana/x-pack/plugins/rule_registry/server/rule_data_plugin_service/resource_installer.js:54:20)\n    at listOnTimeout (node:internal/timers:559:17)\n    at processTimers (node:internal/timers:502:7)"}
{"type":"log","@timestamp":"2022-05-09T15:50:32+01:00","tags":["error","plugins","ruleRegistry"],"pid":48672,"message":"Error: Failure installing common resources shared between all indices. Timeout: it took more than 1200000ms\n    at ResourceInstaller.installWithTimeout (/usr/share/kibana/x-pack/plugins/rule_registry/server/rule_data_plugin_service/resource_installer.js:63:13)\n    at ResourceInstaller.installCommonResources (/usr/share/kibana/x-pack/plugins/rule_registry/server/rule_data_plugin_service/resource_installer.js:77:5)"}
{"type":"log","@timestamp":"2022-05-10T09:13:33+01:00","tags":["info","plugins-system","standard"],"pid":48672,"message":"Stopping all plugins."}
{"type":"log","@timestamp":"2022-05-10T09:13:33+01:00","tags":["info","plugins","monitoring","monitoring","kibana-monitoring"],"pid":48672,"message":"Monitoring stats collection is stopped"}
{"type":"log","@timestamp":"2022-05-10T09:14:03+01:00","tags":["warning","plugins-system","standard"],"pid":48672,"message":"\"eventLog\" plugin didn't stop in 30sec., move on to the next."}
{"type":"log","@timestamp":"2022-05-10T09:14:11+01:00","tags":["info","plugins-service"],"pid":196863,"message":"Plugin \"metricsEntities\" is disabled."}
{"type":"log","@timestamp":"2022-05-10T09:14:11+01:00","tags":["info","http","server","Preboot"],"pid":196863,"message":"http server running at http://10.0.3.132:5601"}
{"type":"log","@timestamp":"2022-05-10T09:14:11+01:00","tags":["warning","config","deprecation"],"pid":196863,"message":"\"logging.dest\" has been deprecated and will be removed in 8.0. To set the destination moving forward, you can use the \"console\" appender in your logging configuration or define a custom one."}
{"type":"log","@timestamp":"2022-05-10T09:14:11+01:00","tags":["warning","config","deprecation"],"pid":196863,"message":"Starting in 8.0, the Kibana logging format will be changing. This may affect you if you are doing any special handling of your Kibana logs, such as ingesting logs into Elasticsearch for further analysis. If you are using the new logging configuration, you are already receiving logs in both old and new formats, and the old format will simply be going away. If you are not yet using the new logging configuration, the log format will change upon upgrade to 8.0. Beginning in 8.0, the format of JSON logs will be ECS-compatible JSON, and the default pattern log format will be configurable with our new logging system. Please refer to the documentation for more information about the new logging format."}
{"type":"log","@timestamp":"2022-05-10T09:14:11+01:00","tags":["warning","config","deprecation"],"pid":196863,"message":"The default mechanism for Reporting privileges will work differently in future versions, which will affect the behavior of this cluster. Set \"xpack.reporting.roles.enabled\" to \"false\" to adopt the future behavior before upgrading."}
{"type":"log","@timestamp":"2022-05-10T09:14:11+01:00","tags":["warning","config","deprecation"],"pid":196863,"message":"User sessions will automatically time out after 8 hours of inactivity starting in 8.0. Override this value to change the timeout."}
{"type":"log","@timestamp":"2022-05-10T09:14:11+01:00","tags":["warning","config","deprecation"],"pid":196863,"message":"Users are automatically required to log in again after 30 days starting in 8.0. Override this value to change the timeout."}
9

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