Hi, in our production environment, the kibana dashboard is now showing Kibana did not load properly. Check the server output for more information.
When checking the browser developer Console we obtain:
Content Security Policy: Directive ‘child-src’ has been deprecated. Please use directive ‘worker-src’ to control workers, or directive ‘frame-src’ to control frames respectively.
**Content Security Policy: The page’s settings blocked the loading of a resource at inline (“script-src”). kibana:186:1**
^ A single error about an inline script not firing due to content security policy is expected! bootstrap.js:10:20
This page uses the non standard property “zoom”. Consider using calc() in the relevant property values, or using “transform” along with “transform-origin: 0 0”. kibana
Loading failed for the <script> with source “https://kibana.test.ourcompanydomain/built_assets/dlls/vendors.bundle.dll.js”. kibana:1:1
Looking at kibana service status seems fine:
service kibana status
● kibana.service - Kibana
Loaded: loaded (/etc/systemd/system/kibana.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2019-08-23 13:09:21 CEST; 6 months 23 days ago
Main PID: 5069 (node)
Tasks: 11 (limit: 4915)
CGroup: /system.slice/kibana.service
└─5069 /usr/share/kibana/bin/../node/bin/node --no-warnings --max-http-header->size=65536 /usr/share/kibana/bin/../src/cli -c /etc/kibana/kibana.yml
From the logs we only see this message repeating: Mar 16 07:49:23 monitor01 kibana[5069]: {"type":"response","@timestamp":"2020-03-16T06:49:23Z","tags":[],"pid":5069,"method":"get","statusCode":302,"req":{"url":"/","method":"get","headers":{"host":"kibana","connection":"close"},"remoteAddress":"127.0.0.1","userAgent":"127.0.0.1"},"res":{"statusCode":302,"responseTime":4,"contentLength":9},"message":"GET / 302 4ms - 9.0B"}
More specifically, what is The page’s settings blocked the loading of a resource at inline (“script-src”). kibana:186:1 pointing to ?
We tried to restart the service with no impact on the reported error
That is our CSP warning and your setup seems to be violating it.
Which version of the stack you are on and what is your set up? What do you see in elasticsearch logs?
How to get Kibana version effectively from the CLI ? I am getting a Empty reply from server after trying curl -vvv -XGET -U myusername:myurlencodedpassword 'localhost:9200' - I am double checking if this may be related to wrong credentials or missconfigured stack.
As regard the elasticsearch_access.log we see as today:
[2020-03-16T17:53:47,675][WARN ][tech.beshu.ror.es.SSLNetty4HttpServerTransport] [OJLMpVY] io.netty.handler.ssl.NotSslRecordException: not an SSL/TLS record: 474554202f20485454502f312e310d0a486f73743a206c6f63616c686f73743a393230300d0a557365722d4167656e743a206375726c2f372e35322e310d0a4163636570743a202a2f2a0d0a0d0a connecting from: /0:0:0:0:0:0:0:1:46226
[2020-03-16T17:56:36,947][WARN ][tech.beshu.ror.es.SSLNetty4HttpServerTransport] [OJLMpVY] io.netty.handler.ssl.NotSslRecordException: not an SSL/TLS record: 474554202f20485454502f312e310d0a486f73743a206c6f63616c686f73743a393230300d0a557365722d4167656e743a206375726c2f372e35322e310d0a4163636570743a202a2f2a0d0a0d0a connecting from: /0:0:0:0:0:0:0:1:47802
[2020-03-16T17:58:56,995][WARN ][tech.beshu.ror.es.SSLNetty4HttpServerTransport] [OJLMpVY] io.netty.handler.ssl.NotSslRecordException: not an SSL/TLS record: 474554202f20485454502f312e310d0a486f73743a206c6f63616c686f73743a393230300d0a557365722d4167656e743a206375726c2f372e35322e310d0a4163636570743a202a2f2a0d0a0d0a connecting from: /0:0:0:0:0:0:0:1:49084
[2020-03-16T18:01:36,709][WARN ][tech.beshu.ror.es.SSLNetty4HttpServerTransport] [OJLMpVY] io.netty.handler.ssl.NotSslRecordException: not an SSL/TLS record: 474554202f20485454502f312e310d0a486f73743a206c6f63616c686f73743a393230300d0a557365722d4167656e743a206375726c2f372e35322e3
In elasticsearch_deprecation.log:
[2020-03-13T18:06:24,150][WARN ][o.e.d.i.m.MapperService ] [OJLMpVY] [default] mapping is deprecated since it is not useful anymore now that indexes cannot have more than one type
[2020-03-13T18:06:24,189][WARN ][o.e.d.a.a.i.t.p.PutIndexTemplateRequest] [OJLMpVY] Deprecated field [template] used, replaced by [index_patterns]
[2020-03-13T18:06:24,191][WARN ][o.e.d.i.m.MapperService ] [OJLMpVY] [default] mapping is deprecated since it is not useful anymore now that indexes cannot have more than one type
[2020-03-13T18:06:28,518][WARN ][o.e.d.a.a.i.t.p.PutIndexTemplateRequest] [OJLMpVY] Deprecated field [template] used, replaced by [index_patterns]
[2020-03-13T18:06:28,520][WARN ][o.e.d.i.m.MapperService ] [OJLMpVY] [default] mapping is deprecated since it is not useful anymore now that indexes cannot have more than one type
[2020-03-13T18:07:30,023][WARN ][o.e.d.a.a.i.t.p.PutIndexTemplateRequest] [OJLMpVY] Deprecated field [template] used, replaced by [index_patterns]
[2020-03-13T18:07:30,025][WARN ][o.e.d.i.m.MapperService ] [OJLMpVY] [default] mapping is deprecated since it is not useful anymore now that indexes cannot have more than one type
[2020-03-13T18:07:42,324][WARN ][o.e.d.a.a.i.t.p.PutIndexTemplateRequest] [OJLMpVY] Deprecated field [template] used, replaced by [index_patterns]
[2020-03-13T18:07:42,327][WARN ][o.e.d.i.m.MapperService ] [OJLMpVY] [default] mapping is deprecated since it is not useful anymore now that indexes cannot have more than one type
[2020-03-13T18:07:46,882][WARN ][o.e.d.a.a.i.t.p.PutIndexTemplateRequest] [OJLMpVY] Deprecated field [template] used, replaced by [index
Our elasticsearch.log file is empty and I see nothing new in the older next (which is 3 days older).
As regard our setup we have the ELK and graphana installed on a physical server (Debian Node).
Name: Firefox
Version: 74.0
Build ID: 20200309095159
Update Channel: release
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:74.0) Gecko/20100101 Firefox/74.0
OS: Darwin 19.3.0
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.