SG / kibana causes chrome to crash

I’ve just installed ES and 6.1.1, as well as the searchguard es and kibana plugins (6.1.1-8). It works fine with firefox and edge, but crashes chrome (v63) right away. I’m able to login, then the next page partially loads and crashes. I’ve tried reinstalling and clearing cache, but no luck. Any ideas what might be going on? Let me know if there’s diagnostic logs that I should provide.

Thanks,

Justin

Which operating system and which exact browser version?

···

On Monday, 8 January 2018 00:34:37 UTC+1, Justin Mitchell wrote:

I’ve just installed ES and 6.1.1, as well as the searchguard es and kibana plugins (6.1.1-8). It works fine with firefox and edge, but crashes chrome (v63) right away. I’m able to login, then the next page partially loads and crashes. I’ve tried reinstalling and clearing cache, but no luck. Any ideas what might be going on? Let me know if there’s diagnostic logs that I should provide.

Thanks,

Justin

Do you have any add-ons installed that might cause the crash? The plugin has been tested on:

Version 63.0.3239.132 (Official Build) (64-bit)

Also, what does “crash” mean? Do you mean the browser crashes or the page does not load?

Is there anything in the Kibana logs, or on the Web Developer Console?

···

On Monday, January 8, 2018 at 12:34:37 AM UTC+1, Justin Mitchell wrote:

I’ve just installed ES and 6.1.1, as well as the searchguard es and kibana plugins (6.1.1-8). It works fine with firefox and edge, but crashes chrome (v63) right away. I’m able to login, then the next page partially loads and crashes. I’ve tried reinstalling and clearing cache, but no luck. Any ideas what might be going on? Let me know if there’s diagnostic logs that I should provide.

Thanks,

Justin

I’m using Amazon Linux 2, with Chrome Version 63.0.3239.132 (Official Build) (64-bit).

I’ve tried disabling all plugins, and it does the same thing. After logging in, it loads the next page, but it becomes unresponsive right away. Eventually Chrome reports that the page is unresponsive and prompts me to close it.

The logs don’t look too interesting, but attaching anyways.

···

[root@ip-10-0-1-137 ~]# /usr/share/kibana/bin/…/node/bin/node --no-warnings /usr/share/kibana/bin/…/src/cli -c /etc/kibana/kibana.yml
log [01:02:51.658] [info][status][plugin:kibana@6.1.1] Status changed from uninitialized to green - Ready
log [01:02:51.706] [info][status][plugin:elasticsearch@6.1.1] Status changed from uninitialized to yellow - Waiting for Elasticsearch
log [01:02:52.533] [info][status][plugin:searchguard@6.1.1] Status changed from uninitialized to yellow - Initialising Search Guard authentication plugin.
log [01:02:52.534] [info][status][plugin:searchguard@6.1.1] Status changed from yellow to yellow - Default cookie password detected, please set a password in kibana.yml by setting ‘searchguard.cookie.password’ (min. 32 characters).
log [01:02:52.534] [info][status][plugin:searchguard@6.1.1] Status changed from yellow to yellow - ‘searchguard.cookie.secure’ is set to false, cookies are transmitted over unsecure HTTP connection. Consider using HTTPS and set this key to ‘true’
log [01:02:52.730] [info][status][plugin:searchguard@6.1.1] Status changed from yellow to yellow - Search Guard session management enabled.
log [01:02:52.731] [info][status][plugin:searchguard@6.1.1] Status changed from yellow to yellow - Search Guard multitenancy disabled
log [01:02:52.732] [info][status][plugin:searchguard@6.1.1] Status changed from yellow to yellow - Search Guard copy JWT params disabled
log [01:02:52.910] [info][status][plugin:searchguard@6.1.1] Status changed from yellow to yellow - Search Guard configuration GUI enabled
log [01:02:52.944] [info][status][plugin:searchguard@6.1.1] Status changed from yellow to yellow - Search Guard system routes registered.
log [01:02:52.945] [info][status][plugin:searchguard@6.1.1] Status changed from yellow to green - Search Guard plugin initialised.
log [01:02:52.957] [info][status][plugin:console@6.1.1] Status changed from uninitialized to green - Ready
log [01:02:52.989] [info][status][plugin:elasticsearch@6.1.1] Status changed from yellow to green - Ready
log [01:02:52.997] [info][status][plugin:metrics@6.1.1] Status changed from uninitialized to green - Ready
log [01:02:53.173] [info][status][plugin:timelion@6.1.1] Status changed from uninitialized to green - Ready
log [01:02:53.178] [info][listening] Server running at http://10.0.1.137:5601

On Monday, 8 January 2018 07:11:35 UTC-5, Jochen Kressin wrote:

Do you have any add-ons installed that might cause the crash? The plugin has been tested on:

Version 63.0.3239.132 (Official Build) (64-bit)

Also, what does “crash” mean? Do you mean the browser crashes or the page does not load?

Is there anything in the Kibana logs, or on the Web Developer Console?

On Monday, January 8, 2018 at 12:34:37 AM UTC+1, Justin Mitchell wrote:

I’ve just installed ES and 6.1.1, as well as the searchguard es and kibana plugins (6.1.1-8). It works fine with firefox and edge, but crashes chrome (v63) right away. I’m able to login, then the next page partially loads and crashes. I’ve tried reinstalling and clearing cache, but no luck. Any ideas what might be going on? Let me know if there’s diagnostic logs that I should provide.

Thanks,

Justin

Just to make sure

  • you are running ES and KI on one machine?

  • without the SG plugin everything works fine?

  • after you press the login button, are you redirected to /app/kibana and it is this page becomes unresponsive OR

  • is it the login page itself that the Chrome reports unresponsive?

With the Developer Tools of Chrome, could you please record the network traffic during the login process?

  • Open the login page

  • Open the Developer tools and select the “Network” tab.

  • Choose “Preserver log” and log in

Is there any long running network activity? Can you select all entries on the “Network” tab, right-click, choose “Save as HAR with content” and attach it? Would be helpful for debugging.

Thanks!

···

On Tuesday, January 9, 2018 at 2:06:48 AM UTC+1, Justin Mitchell wrote:

I’m using Amazon Linux 2, with Chrome Version 63.0.3239.132 (Official Build) (64-bit).

I’ve tried disabling all plugins, and it does the same thing. After logging in, it loads the next page, but it becomes unresponsive right away. Eventually Chrome reports that the page is unresponsive and prompts me to close it.

The logs don’t look too interesting, but attaching anyways.

[root@ip-10-0-1-137 ~]# /usr/share/kibana/bin/…/node/bin/node --no-warnings /usr/share/kibana/bin/…/src/cli -c /etc/kibana/kibana.yml
log [01:02:51.658] [info][status][plugin:kibana@6.1.1] Status changed from uninitialized to green - Ready
log [01:02:51.706] [info][status][plugin:elasticsearch@6.1.1] Status changed from uninitialized to yellow - Waiting for Elasticsearch
log [01:02:52.533] [info][status][plugin:searchguard@6.1.1] Status changed from uninitialized to yellow - Initialising Search Guard authentication plugin.
log [01:02:52.534] [info][status][plugin:searchguard@6.1.1] Status changed from yellow to yellow - Default cookie password detected, please set a password in kibana.yml by setting ‘searchguard.cookie.password’ (min. 32 characters).
log [01:02:52.534] [info][status][plugin:searchguard@6.1.1] Status changed from yellow to yellow - ‘searchguard.cookie.secure’ is set to false, cookies are transmitted over unsecure HTTP connection. Consider using HTTPS and set this key to ‘true’
log [01:02:52.730] [info][status][plugin:searchguard@6.1.1] Status changed from yellow to yellow - Search Guard session management enabled.
log [01:02:52.731] [info][status][plugin:searchguard@6.1.1] Status changed from yellow to yellow - Search Guard multitenancy disabled
log [01:02:52.732] [info][status][plugin:searchguard@6.1.1] Status changed from yellow to yellow - Search Guard copy JWT params disabled
log [01:02:52.910] [info][status][plugin:searchguard@6.1.1] Status changed from yellow to yellow - Search Guard configuration GUI enabled
log [01:02:52.944] [info][status][plugin:searchguard@6.1.1] Status changed from yellow to yellow - Search Guard system routes registered.
log [01:02:52.945] [info][status][plugin:searchguard@6.1.1] Status changed from yellow to green - Search Guard plugin initialised.
log [01:02:52.957] [info][status][plugin:console@6.1.1] Status changed from uninitialized to green - Ready
log [01:02:52.989] [info][status][plugin:elasticsearch@6.1.1] Status changed from yellow to green - Ready
log [01:02:52.997] [info][status][plugin:metrics@6.1.1] Status changed from uninitialized to green - Ready
log [01:02:53.173] [info][status][plugin:timelion@6.1.1] Status changed from uninitialized to green - Ready
log [01:02:53.178] [info][listening] Server running at http://10.0.1.137:5601

On Monday, 8 January 2018 07:11:35 UTC-5, Jochen Kressin wrote:

Do you have any add-ons installed that might cause the crash? The plugin has been tested on:

Version 63.0.3239.132 (Official Build) (64-bit)

Also, what does “crash” mean? Do you mean the browser crashes or the page does not load?

Is there anything in the Kibana logs, or on the Web Developer Console?

On Monday, January 8, 2018 at 12:34:37 AM UTC+1, Justin Mitchell wrote:

I’ve just installed ES and 6.1.1, as well as the searchguard es and kibana plugins (6.1.1-8). It works fine with firefox and edge, but crashes chrome (v63) right away. I’m able to login, then the next page partially loads and crashes. I’ve tried reinstalling and clearing cache, but no luck. Any ideas what might be going on? Let me know if there’s diagnostic logs that I should provide.

Thanks,

Justin