Browserslist: caniuse-lite is outdated. Please run next command `npm update caniuse-lite browserslist

Elastic Stack Kibana
1

Hi all,

Is the following a bug?

Jul 06 10:38:46 vm1.local.com systemd[1]: Started Kibana.
Jul 06 10:40:42 vm1.local.com kibana[5454]: {"type":"log","@timestamp":"2019-07-06T14:40:42Z","tags":["info","optimize"],"pid":5454,"message":"Optimizing and c
Jul 06 10:40:49 vm1.local.com kibana[5454]: Browserslist: caniuse-lite is outdated. Please run next command `npm update caniuse-lite browserslist`
Jul 06 10:41:15 vm1.local.com kibana[5454]: Browserslist: caniuse-lite is outdated. Please run next command `npm update caniuse-lite browserslist`

Any idea?
I used Kibana RPM 7.2.0

2

What I found is:

When for the first time I have installed Kibana, it worked properly.

Afterward, when I applied certificates to Kibana, I got that error message,
rowserslist: caniuse-lite is outdated. Please run next commandnpm update caniuse-lite browserslist`

Then I removed any certificates related configuration and reverted back to normal traffic (http)... But again I got the same error.

So when I uninstall the rpm package completely and installed again, it worked ( without certificate)... Then again by applying the cert, I got that error

Any idea?

3

This is a warning emitted by one of our dependencies. It should not cause any problems for you in practice and can be safely ignored.

4

Thanks for replying

But it does not let me to open the Kibana. Each time I refresh my Kibana url in my browser, I get that error in logs and nothing shows me in browser.

I used journalctl to capture logs and it shows me that error and nothing else

Can you please help?

5

From the logs you posted, it appears the Optimization process is still running. This can take several minutes depending on the resources available on your machine (it's quite memory and CPU intensive).

This process only needs to run if you install or disable any plugins. Once it's been run it will not need to run again unless you install or disable additional plugins.

nothing shows me in browser

Do you see the Kibana loading screen or is it a blank page? If it's a blank page, can you run this and post the results:

$ curl -v http://localhost:5601
6

Hi,

Here are the steps I did:

  1. Creating ca, with pem:
    ./elasticsearch-certutil ca --pem
  2. Creating certs for two instances:
    ./elasticsearch-certutil cert --ca-cert /appRPM/elastic-stack-ca/ca/ca.crt --ca-key /appRPM/elastic-stack-ca/ca/ca.key --multiple --pem
    Here is my inputs during cert creation by above command:

Enter instance name: vm1.local.com
Enter name for directories and files of vm1.local.com [vm1.local.com]:
Enter IP Addresses for instance (comma-separated if more than one) :
Enter DNS names for instance (comma-separated if more than one) : vm1.local.com
Would you like to specify another instance? Press 'y' to continue entering instance information: y
Enter instance name: vm2.local.com
Enter name for directories and files of vm2.local.com [vm2.local.com]:
Enter IP Addresses for instance (comma-separated if more than one) :
Enter DNS names for instance (comma-separated if more than one) : vm2.local.com
Would you like to specify another instance? Press 'y' to continue entering instance information:
Please enter the desired output file [certificate-bundle.zip]:

Certificates written to /usr/share/elasticsearch/certificate-bundle.zip

  1. Here is elasticsearch and kibana yaml files:

vm1.local.com -----------------------------------------------------
elasticsearch.yml

 cluster.name: logging-qa-rpm
 node.name: node-1
    node.master: true
    node.data: true
    node.ingest: true
    path.data: /appRPM/data/elasticsearch
    path.logs: /appRPM/log/elasticsearch
    bootstrap.memory_lock: true
    network.host: 192.168.0.71
    http.port: 9200
    discovery.seed_hosts: ["192.168.0.71", "192.168.0.72"]
    cluster.initial_master_nodes: ["node-1", "node-2"]

    xpack.security.enabled: true

    xpack.security.transport.ssl.enabled: true
    xpack.security.transport.ssl.verification_mode: certificate
    xpack.security.transport.ssl.key: /etc/elasticsearch/certs/vm1.local.com.key
    xpack.security.transport.ssl.certificate: /etc/elasticsearch/certs/vm1.local.com.crt
    xpack.security.transport.ssl.certificate_authorities: [ "/etc/elasticsearch/certs/ca.crt" ]

    xpack.security.http.ssl.enabled: true
    xpack.security.http.ssl.key:  /etc/elasticsearch/certs/vm1.local.com.key
    xpack.security.http.ssl.certificate: /etc/elasticsearch/certs/vm1.local.com.crt
    xpack.security.http.ssl.certificate_authorities: [ "/etc/elasticsearch/certs/ca.crt" ]

kibana.yml

server.port: 5601
server.host: 192.168.0.71
elasticsearch.hosts: ["https://192.168.0.71:9200", "https://192.168.0.72:9200"]
elasticsearch.username: "kibana"
elasticsearch.password: "xxxxxxx"
elasticsearch.pingTimeout: 15000
elasticsearch.requestTimeout: 30000
elasticsearch.startupTimeout: 50000
server.ssl.enabled: true
server.ssl.key: /appRPM/certs_kibana/vm1.local.com.key
server.ssl.certificate: /appRPM/certs_kibana/vm1.local.com.crt
elasticsearch.ssl.certificateAuthorities: [ "/appRPM/certs_kibana/ca.crt" ]
elasticsearch.ssl.verificationMode: full

vm2.local.com ------------------------------------------------------------------------------------
elasticsearch.yml

cluster.name: logging-qa-rpm
    node.name: node-2
    node.master: true
    node.data: true
    node.ingest: true
    path.data: /appRPM/data/elasticsearch
    path.logs: /appRPM/log/elasticsearch
    bootstrap.memory_lock: true
    network.host: 192.168.0.72
    http.port: 9200
    discovery.seed_hosts: ["192.168.0.71", "192.168.0.72"]
    cluster.initial_master_nodes: ["node-1", "node-2"]

    xpack.security.enabled: true

    xpack.security.transport.ssl.enabled: true
    xpack.security.transport.ssl.verification_mode: certificate
    xpack.security.transport.ssl.key: /etc/elasticsearch/certs/vm2.local.com.key
    xpack.security.transport.ssl.certificate: /etc/elasticsearch/certs/vm2.local.com.crt
    xpack.security.transport.ssl.certificate_authorities: [ "/etc/elasticsearch/certs/ca.crt" ]

    xpack.security.http.ssl.enabled: true
    xpack.security.http.ssl.key:  /etc/elasticsearch/certs/vm2.local.com.key
    xpack.security.http.ssl.certificate: /etc/elasticsearch/certs/vm2.local.com.crt
    xpack.security.http.ssl.certificate_authorities: [ "/etc/elasticsearch/certs/ca.crt" ]
  1. encryption between elasticsearch nodes work fine.

But on Kibana ( vm1.local.com ) , I get the following: ((Browser shows: Kibana server is not ready yet )

error:

Jul 06 18:07:45 vm1.local.com systemd[1]: Started Kibana.
    Jul 06 18:12:56 vm1.local.com kibana[11146]: {"type":"log","@timestamp":"2019-07-06T22:12:56Z","tags":["info","optimize"],"pid":11146,"message":"Optimizing and caching bundles for graph, monitoring, space_selector, login, overwritten_session, logout, logged_out, ml, dashboardViewer, apm, code, maps, canvas, infra, siem, uptime, kibana, stateSessionStorageRedirect, status_page and timelion. This may take a few minutes"}
    Jul 06 18:14:04 vm1.local.com kibana[11146]: Browserslist: caniuse-lite is outdated. Please run next command `npm update caniuse-lite browserslist`
    Jul 06 18:14:25 vm1.local.com kibana[11146]: {"type":"error","@timestamp":"2019-07-06T22:14:23Z","tags":["connection","client","error"],"pid":11146,"level":"error","error":{"message":"139634049566592:error:14094416:SSL routines:ssl3_read_bytes:sslv3 alert certificate unknown:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:1407:SSL alert number 46\n","name":"Error","stack":"Error: 139634049566592:error:14094416:SSL routines:ssl3_read_bytes:sslv3 alert certificate unknown:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:1407:SSL alert number 46\n"},"message":"139634049566592:error:14094416:SSL routines:ssl3_read_bytes:sslv3 alert certificate unknown:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:1407:SSL alert number 46\n"}

Can you please advise.

7

Hey @mhsh64, thanks for the detailed steps!

Unfortunately these TLS errors are rather cryptic, so we might have to try a few things.

It looks like you generated the certs without specifying IP addresses. Can you try specifying your elasticsearch.hosts using the DNS names you specified when you created the certs? (vm1.local.com, vm2.local.com).

I see you specified a single CA when generating all of these certs - that's great! Can you verify that the CA specified in Kibana's elasticsearch.ssl.certificateAuthorities is the same identical CA that you're specifying in Elasticsearch's xpack.security.http.ssl.certificate_authorities?

8

Hi and thanks for your response

I made the following changes in kibana.yml file and restarted the service:

elasticsearch.hosts: ["https://vm1.local.com:9200", "https://vm2.local.host:9200"]

Can you verify that the CA specified in Kibana's elasticsearch.ssl.certificateAuthorities is the same identical CA that you're specifying in Elasticsearch's xpack.security.http.ssl.certificate_authorities

Yes they are same.

Even using the pem format for the ca certificate, did not work. Same error

elasticsearch.ssl.certificateAuthorities: [ "/appRPM/certs_kibana/ca.pem" ]

Now, when I opened kibana in my browser, I have the same following error:

image
image643×564 15.8 KB

Jul 06 18:58:36 vm1.local.com kibana[11898]: {"type":"error","@timestamp":"2019-07-06T22:58:36Z","tags":["connection","client","error"],"pid":11898,"level":"error","error":{"message":"139889893156736:error:14094416:SSL routines:ssl3_read_bytes:sslv3 alert certificate unknown:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:1407:SSL alert number 46\n","name":"Error","stack":"Error: 139889893156736:error:14094416:SSL routines:ssl3_read_bytes:sslv3 alert certificate unknown:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:1407:SSL alert number 46\n"},"message":"139889893156736:error:14094416:SSL routines:ssl3_read_bytes:sslv3 alert certificate unknown:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:1407:SSL alert number 46\n"}

9

And also, here is the Kibana certificate (vm1.local.com) and ca certificate details:

Kibana certificate (vm1.local.com.crt)

Certificate:
        Data:
            Version: 3 (0x2)
            Serial Number:
                8e:17:ed:81:ef:e4:05:04:46:a5:a1:0b:9c:a3:94:ea:5a:ce:58:93
        Signature Algorithm: sha256WithRSAEncryption
            Issuer: CN=Elastic Certificate Tool Autogenerated CA
            Validity
                Not Before: Jul  4 08:24:52 2019 GMT
                Not After : Jul  3 08:24:52 2022 GMT
            Subject: CN=vm1.local.com
            Subject Public Key Info:
                Public Key Algorithm: rsaEncryption
                    Public-Key: (2048 bit)
                    Modulus:
                        XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
                    Exponent: 65537 (0x10001)
            X509v3 extensions:
                X509v3 Subject Key Identifier:
                    FE:1A:18:BB:3A:8A:03:C6:15:33:43:10:F6:74:39:38:7E:B6:EF:B3
                X509v3 Authority Key Identifier:
                    keyid:5A:23:21:92:24:F9:6E:A5:00:5B:B6:12:F2:1D:15:CF:05:7C:07:80
                X509v3 Subject Alternative Name:
                    DNS:**vm1.local.com**
                X509v3 Basic Constraints:
                    CA:FALSE
        Signature Algorithm: sha256WithRSAEncryption
             XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

ca

Certificate:
        Data:
            Version: 3 (0x2)
            Serial Number:
                e7:21:57:3c:90:de:0e:b9:6b:71:90:21:27:c6:7d:97:6c:b9:68:a2
        Signature Algorithm: sha256WithRSAEncryption
            Issuer: CN=Elastic Certificate Tool Autogenerated CA
            Validity
                Not Before: Jul  4 07:48:41 2019 GMT
                Not After : Jul  3 07:48:41 2022 GMT
            Subject: CN=Elastic Certificate Tool Autogenerated CA
            Subject Public Key Info:
                Public Key Algorithm: rsaEncryption
                    Public-Key: (2048 bit)
                    Modulus:
                        XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
                    Exponent: 65537 (0x10001)
            X509v3 extensions:
                X509v3 Subject Key Identifier:
                    5A:23:21:92:24:F9:6E:A5:00:5B:B6:12:F2:1D:15:CF:05:7C:07:80
                X509v3 Authority Key Identifier:
                    keyid:5A:23:21:92:24:F9:6E:A5:00:5B:B6:12:F2:1D:15:CF:05:7C:07:80
                X509v3 Basic Constraints: critical
                    CA:TRUE
        Signature Algorithm: sha256WithRSAEncryption
             XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
10

Interesting, thanks for the confirmation, and again for the detailed response.

Can you try changing elasticsearch.ssl.verificationMode from full to certificate in your kibana.yml, and let me know if that changes anything? I'm trying to narrow down the scope a bit.

11

Hi

Thanks. I did but unfortunately I got the same error. Any other modifications I need to do?

12

Can you reduce elasticsearch.hosts to just one entry? Try each one on its own.

13

I did:

kibana.yml (on vm1)

server.port: 5601
server.host: 192.168.0.71
elasticsearch.hosts: ["https://vm1.local.com:9200"]
elasticsearch.username: "kibana"
elasticsearch.password: "xxxxxxx"
elasticsearch.pingTimeout: 15000
elasticsearch.requestTimeout: 30000
elasticsearch.startupTimeout: 50000
server.ssl.enabled: true
server.ssl.key: /appRPM/certs_kibana/vm1.local.com.key
server.ssl.certificate: /appRPM/certs_kibana/vm1.local.com.crt
elasticsearch.ssl.certificateAuthorities: [ "/appRPM/certs_kibana/ca.pem" ]
elasticsearch.ssl.verificationMode: certificate

even with elasticsearch.ssl.verificationMode: full

again bellow error:

Jul 06 23:34:15 vm1.local.com kibana[16884]: {"type":"error","@timestamp":"2019-07-07T03:34:15Z","tags":["connection","client","error"],"pid":16884,"level":"error","error":{"message":"139681949030272:error:14094416:SSL routines:ssl3_read_bytes:sslv3 alert certificate unknown:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:1407:SSL alert number 46\n","name":"Error","stack":"Error: 139681949030272:error:14094416:SSL routines:ssl3_read_bytes:sslv3 alert certificate unknown:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:1407:SSL alert number 46\n"},"message":"139681949030272:error:14094416:SSL routines:ssl3_read_bytes:sslv3 alert certificate unknown:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:1407:SSL alert number 46\n"}

This error shows communication problem between ELASTICSEARCH and KIBANA , right?

Please let me know for other changes if I need to apply.

14

Is this error shows encrypted communication problem between BROWSER and KIBANA, or between ELASTICSEARCH and KIBANA ?

My current thinking is that the problem is between Kibana and Elasticsearch, because you're able to receive traffic from Browser <-> Kibana, but Kibana is reporting that the server isn't ready yet. Can you set (in kibana) logging.verbose: true, restart Kibana, and post the full log file?

15 
[root@vm1 bin]# sudo journalctl -f --unit=kibana
-- Logs begin at Sat 2019-07-06 09:25:28 EDT. --
Jul 06 23:37:57 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:37:57Z","tags":["debug","plugins-discovery"],"pid":17182,"message":"Discovering plugins..."}
Jul 06 23:37:57 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:37:57Z","tags":["debug","plugins-discovery"],"pid":17182,"message":"Scanning \"/src/plugins\" for plugin sub-directories..."}
Jul 06 23:37:57 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:37:57Z","tags":["debug","plugins-discovery"],"pid":17182,"message":"Scanning \"/plugins\" for plugin sub-directories..."}
Jul 06 23:37:57 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:37:57Z","tags":["debug","plugins-discovery"],"pid":17182,"message":"Scanning \"/kibana-extra\" for plugin sub-directories..."}
Jul 06 23:37:57 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:37:57Z","tags":["debug","plugins-service"],"pid":17182,"message":"Discovered 0 plugins."}
Jul 06 23:37:57 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:37:57Z","tags":["debug","root"],"pid":17182,"message":"starting root"}
Jul 06 23:37:57 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:37:57Z","tags":["debug","http","server"],"pid":17182,"message":"starting http server"}
Jul 06 23:37:57 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:37:57Z","tags":["debug","http","server"],"pid":17182,"message":"http server running at https://192.168.0.71:5601"}
Jul 06 23:37:57 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:37:57Z","tags":["debug","plugins-service"],"pid":17182,"message":"Plugins service starts plugins"}
Jul 06 23:37:57 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:37:57Z","tags":["debug","legacy-service"],"pid":17182,"message":"starting legacy service"}
Jul 06 23:43:45 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:43:45Z","tags":["plugin","debug"],"pid":17182,"path":"/usr/share/kibana/x-pack","message":"Found plugin at /usr/share/kibana/x-pack"}
Jul 06 23:43:46 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:43:46Z","tags":["debug","legacy-proxy"],"pid":17182,"message":"Event is being forwarded: connection"}
Jul 06 23:43:46 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:43:46Z","tags":["debug","legacy-proxy"],"pid":17182,"message":"Event is being forwarded: connection"}
Jul 06 23:43:46 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:43:46Z","tags":["debug","legacy-proxy"],"pid":17182,"message":"Event is being forwarded: connection"}
Jul 06 23:43:46 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:43:46Z","tags":["debug","legacy-proxy"],"pid":17182,"message":"Event is being forwarded: connection"}
Jul 06 23:43:47 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:43:47Z","tags":["plugin","debug"],"pid":17182,"path":"/usr/share/kibana/src/legacy/core_plugins/apm_oss","message":"Found plugin at /usr/share/kibana/src/legacy/core_plugins/apm_oss"}
Jul 06 23:43:47 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:43:47Z","tags":["plugin","debug"],"pid":17182,"path":"/usr/share/kibana/src/legacy/core_plugins/console","message":"Found plugin at /usr/share/kibana/src/legacy/core_plugins/console"}
Jul 06 23:43:47 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:43:47Z","tags":["plugin","debug"],"pid":17182,"path":"/usr/share/kibana/src/legacy/core_plugins/inspector_views","message":"Found plugin at /usr/share/kibana/src/legacy/core_plugins/inspector_views"}
Jul 06 23:43:47 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:43:47Z","tags":["plugin","debug"],"pid":17182,"path":"/usr/share/kibana/src/legacy/core_plugins/interpreter","message":"Found plugin at /usr/share/kibana/src/legacy/core_plugins/interpreter"}
Jul 06 23:43:47 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:43:47Z","tags":["plugin","debug"],"pid":17182,"path":"/usr/share/kibana/src/legacy/core_plugins/kbn_doc_views","message":"Found plugin at /usr/share/kibana/src/legacy/core_plugins/kbn_doc_views"}
Jul 06 23:43:47 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:43:47Z","tags":["plugin","debug"],"pid":17182,"path":"/usr/share/kibana/src/legacy/core_plugins/kbn_vislib_vis_types","message":"Found plugin at /usr/share/kibana/src/legacy/core_plugins/kbn_vislib_vis_types"}
Jul 06 23:43:52 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:43:52Z","tags":["plugin","debug"],"pid":17182,"path":"/usr/share/kibana/src/legacy/core_plugins/kibana","message":"Found plugin at /usr/share/kibana/src/legacy/core_plugins/kibana"}
Jul 06 23:43:52 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:43:52Z","tags":["plugin","debug"],"pid":17182,"path":"/usr/share/kibana/src/legacy/core_plugins/region_map","message":"Found plugin at /usr/share/kibana/src/legacy/core_plugins/region_map"}
Jul 06 23:43:52 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:43:52Z","tags":["plugin","debug"],"pid":17182,"path":"/usr/share/kibana/src/legacy/core_plugins/state_session_storage_redirect","message":"Found plugin at /usr/share/kibana/src/legacy/core_plugins/state_session_storage_redirect"}
Jul 06 23:43:52 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:43:52Z","tags":["plugin","debug"],"pid":17182,"path":"/usr/share/kibana/src/legacy/core_plugins/status_page","message":"Found plugin at /usr/share/kibana/src/legacy/core_plugins/status_page"}
16 
Jul 06 23:43:52 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:43:52Z","tags":["plugin","debug"],"pid":17182,"path":"/usr/share/kibana/src/legacy/core_plugins/table_vis","message":"Found plugin at /usr/share/kibana/src/legacy/core_plugins/table_vis"}
Jul 06 23:43:52 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:43:52Z","tags":["plugin","debug"],"pid":17182,"path":"/usr/share/kibana/src/legacy/core_plugins/tagcloud","message":"Found plugin at /usr/share/kibana/src/legacy/core_plugins/tagcloud"}
Jul 06 23:43:53 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:43:53Z","tags":["plugin","debug"],"pid":17182,"path":"/usr/share/kibana/src/legacy/core_plugins/tile_map","message":"Found plugin at /usr/share/kibana/src/legacy/core_plugins/tile_map"}
Jul 06 23:43:53 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:43:53Z","tags":["plugin","debug"],"pid":17182,"path":"/usr/share/kibana/src/legacy/core_plugins/timelion","message":"Found plugin at /usr/share/kibana/src/legacy/core_plugins/timelion"}
Jul 06 23:43:53 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:43:53Z","tags":["plugin","debug"],"pid":17182,"path":"/usr/share/kibana/src/legacy/core_plugins/ui_metric","message":"Found plugin at /usr/share/kibana/src/legacy/core_plugins/ui_metric"}
Jul 06 23:43:53 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:43:53Z","tags":["plugin","debug"],"pid":17182,"path":"/usr/share/kibana/src/legacy/core_plugins/vega","message":"Found plugin at /usr/share/kibana/src/legacy/core_plugins/vega"}
Jul 06 23:43:53 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:43:53Z","tags":["plugin","debug"],"pid":17182,"path":"/usr/share/kibana/src/legacy/core_plugins/data","message":"Found plugin at /usr/share/kibana/src/legacy/core_plugins/data"}
Jul 06 23:43:53 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:43:53Z","tags":["plugin","debug"],"pid":17182,"path":"/usr/share/kibana/src/legacy/core_plugins/elasticsearch","message":"Found plugin at /usr/share/kibana/src/legacy/core_plugins/elasticsearch"}
Jul 06 23:43:53 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:43:53Z","tags":["plugin","debug"],"pid":17182,"path":"/usr/share/kibana/src/legacy/core_plugins/input_control_vis","message":"Found plugin at /usr/share/kibana/src/legacy/core_plugins/input_control_vis"}
Jul 06 23:43:53 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:43:53Z","tags":["plugin","debug"],"pid":17182,"path":"/usr/share/kibana/src/legacy/core_plugins/markdown_vis","message":"Found plugin at /usr/share/kibana/src/legacy/core_plugins/markdown_vis"}
Jul 06 23:43:54 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:43:53Z","tags":["plugin","debug"],"pid":17182,"path":"/usr/share/kibana/src/legacy/core_plugins/metric_vis","message":"Found plugin at /usr/share/kibana/src/legacy/core_plugins/metric_vis"}
Jul 06 23:43:57 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:43:57Z","tags":["plugin","debug"],"pid":17182,"path":"/usr/share/kibana/src/legacy/core_plugins/metrics","message":"Found plugin at /usr/share/kibana/src/legacy/core_plugins/metrics"}
Jul 06 23:44:09 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:44:09Z","tags":["debug","legacy-service"],"pid":17182,"message":"Kibana server is not ready yet GET:/."}
Jul 06 23:44:09 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:44:09Z","tags":["debug","legacy-proxy"],"pid":17182,"message":"Event is being forwarded: clientError"}
Jul 06 23:44:09 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:44:09Z","tags":["debug","connection","econnreset"],"pid":17182,"message":"ECONNRESET: Socket was closed by the client (probably the browser) before it could be read completely"}
Jul 06 23:44:09 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:44:09Z","tags":["debug","legacy-proxy"],"pid":17182,"message":"Event is being forwarded: clientError"}
Jul 06 23:44:09 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:44:09Z","tags":["debug","connection","econnreset"],"pid":17182,"message":"ECONNRESET: Socket was closed by the client (probably the browser) before it could be read completely"}
Jul 06 23:44:10 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:44:10Z","tags":["debug","legacy-service"],"pid":17182,"message":"Kibana server is not ready yet GET:/favicon.ico."}
Jul 06 23:44:10 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:44:10Z","tags":["info","optimize"],"pid":17182,"message":"Optimizing and caching bundles for graph, monitoring, space_selector, login, overwritten_session, logout, logged_out, ml, dashboardViewer, apm, code, maps, canvas, infra, siem, uptime, kibana, stateSessionStorageRedirect, status_page and timelion. This may take a few minutes"}
Jul 06 23:44:38 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:44:37Z","tags":["debug","legacy-service"],"pid":17182,"message":"Kibana server is not ready yet GET:/."}
Jul 06 23:44:40 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:44:39Z","tags":["debug","legacy-proxy"],"pid":17182,"message":"Event is being forwarded: connection"}
Jul 06 23:44:44 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:44:44Z","tags":["debug","legacy-service"],"pid":17182,"message":"Kibana server is not ready yet GET:/favicon.ico."}
Jul 06 23:45:25 vm1.local.com kibana[17182]: Browserslist: caniuse-lite is outdated. Please run next command `npm update caniuse-lite browserslist`
Jul 06 23:45:54 vm1.local.com kibana[17182]: Browserslist: caniuse-lite is outdated. Please run next command `npm update caniuse-lite browserslist`
Jul 06 23:45:59 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:45:59Z","tags":["debug","legacy-service"],"pid":17182,"message":"Kibana server is not ready yet GET:/."}
Jul 06 23:45:59 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:45:59Z","tags":["debug","legacy-proxy"],"pid":17182,"message":"Event is being forwarded: connection"}
^C
17 
[root@vm1 bin]# sudo journalctl -f --unit=kibana
-- Logs begin at Sat 2019-07-06 09:25:28 EDT. --
Jul 06 23:44:09 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:44:09Z","tags":["debug","connection","econnreset"],"pid":17182,"message":"ECONNRESET: Socket was closed by the client (probably the browser) before it could be read completely"}
Jul 06 23:44:10 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:44:10Z","tags":["debug","legacy-service"],"pid":17182,"message":"Kibana server is not ready yet GET:/favicon.ico."}
Jul 06 23:44:10 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:44:10Z","tags":["info","optimize"],"pid":17182,"message":"Optimizing and caching bundles for graph, monitoring, space_selector, login, overwritten_session, logout, logged_out, ml, dashboardViewer, apm, code, maps, canvas, infra, siem, uptime, kibana, stateSessionStorageRedirect, status_page and timelion. This may take a few minutes"}
Jul 06 23:44:38 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:44:37Z","tags":["debug","legacy-service"],"pid":17182,"message":"Kibana server is not ready yet GET:/."}
Jul 06 23:44:40 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:44:39Z","tags":["debug","legacy-proxy"],"pid":17182,"message":"Event is being forwarded: connection"}
Jul 06 23:44:44 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:44:44Z","tags":["debug","legacy-service"],"pid":17182,"message":"Kibana server is not ready yet GET:/favicon.ico."}
Jul 06 23:45:25 vm1.local.com kibana[17182]: Browserslist: caniuse-lite is outdated. Please run next command `npm update caniuse-lite browserslist`
Jul 06 23:45:54 vm1.local.com kibana[17182]: Browserslist: caniuse-lite is outdated. Please run next command `npm update caniuse-lite browserslist`
Jul 06 23:45:59 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:45:59Z","tags":["debug","legacy-service"],"pid":17182,"message":"Kibana server is not ready yet GET:/."}
Jul 06 23:45:59 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:45:59Z","tags":["debug","legacy-proxy"],"pid":17182,"message":"Event is being forwarded: connection"}
Jul 06 23:47:39 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:47:38Z","tags":["debug","legacy-service"],"pid":17182,"message":"Kibana server is not ready yet GET:/favicon.ico."}
Jul 06 23:47:39 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:47:39Z","tags":["debug","legacy-service"],"pid":17182,"message":"Kibana server is not ready yet GET:/."}
Jul 06 23:47:39 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:47:39Z","tags":["debug","legacy-proxy"],"pid":17182,"message":"Event is being forwarded: connection"}
Jul 06 23:47:43 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:47:43Z","tags":["debug","legacy-service"],"pid":17182,"message":"Kibana server is not ready yet GET:/favicon.ico."}
Jul 06 23:49:41 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:49:40Z","tags":["debug","legacy-service"],"pid":17182,"message":"Kibana server is not ready yet GET:/."}
Jul 06 23:49:42 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:49:42Z","tags":["debug","legacy-proxy"],"pid":17182,"message":"Event is being forwarded: connection"}
Jul 06 23:49:50 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:49:49Z","tags":["debug","legacy-service"],"pid":17182,"message":"Kibana server is not ready yet GET:/favicon.ico."}
Jul 06 23:49:52 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:49:52Z","tags":["debug","legacy-proxy"],"pid":17182,"message":"Event is being forwarded: clientError"}
Jul 06 23:49:52 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:49:52Z","tags":["debug","connection","econnreset"],"pid":17182,"message":"ECONNRESET: Socket was closed by the client (probably the browser) before it could be read completely"}
Jul 06 23:51:08 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:51:07Z","tags":["debug","legacy-service"],"pid":17182,"message":"Kibana server is not ready yet GET:/."}
Jul 06 23:51:08 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:51:08Z","tags":["debug","legacy-proxy"],"pid":17182,"message":"Event is being forwarded: connection"}
Jul 06 23:51:16 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:51:16Z","tags":["debug","legacy-service"],"pid":17182,"message":"Kibana server is not ready yet GET:/favicon.ico."}
Jul 06 23:51:16 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:51:16Z","tags":["debug","legacy-proxy"],"pid":17182,"message":"Event is being forwarded: clientError"}
Jul 06 23:51:16 vm1.local.com kibana[17182]: {"type":"log","@timestamp":"2019-07-07T03:51:16Z","tags":["debug","connection","econnreset"],"pid":17182,"message":"ECONNRESET: Socket was closed by the client (probably the browser) before it could be read completely"}
18

This line should eventually have a corresponding entry similar to:

Optimization of graph, monitoring, space_selector, login, overwritten_session, logout, logged_out, ml, dashboardViewer, apm, code, maps, canvas, infra, siem, uptime, kibana, stateSessionStorageRedirect, status_page and timelion complete in 100 seconds.

Are you seeing that anywhere? This optimization step shouldn't in any way be tied to your TLS setup, which is interesting..

19

If you set xpack.security.http.ssl.enabled to false, and connect to Elasticsearch over http instead of https, does Kibana startup successfully?

20

I recall I saw that message. Since I do not access to the system now, I will restart the service again and will share you the entire log tonight (Eastern time)

Thanks.