Kibana Dashboard - net::ERR_ABORTED 400

Elastic Stack Kibana
1

Hey,

We are facing a very random issue, the most of the time the Kibana Dashboard loads properly but when not, we got this error messages:

image-20230609-153606
image-20230609-1536061920×703 141 KB

Here the Kibana logs (a piece of it, these are the only relevant records on the log):

45.18.32.237 - - [09/Jun/2023:15:19:46 +0000] "GET / ki-dashboard/plugins/timelion/index.css HTTP/1.1" 400 0 "https://data.panzura.com/ki-dashboard/app/kibana?time_filter=true&cluster_id=some_cluster_id" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.36"

45.18.32.237 - - [09/Jun/2023:15:19:46 +0000] "GET / ki-dashboard/plugins/my_login/app.css HTTP/1.1" 400 0 "https://data.panzura.com/ki-dashboard/app/kibana?time_filter=true&cluster_id=some_cluster_id" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.36"

45.18.32.237 - - [09/Jun/2023:15:19:46 +0000] "GET / ki-dashboard/plugins/console/index.css HTTP/1.1" 400 0 "https://data.panzura.com/ki-dashboard/app/kibana?time_filter=true&cluster_id=some_cluster_id" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.36"

45.18.32.237 - - [09/Jun/2023:15:19:46 +0000] "GET / ki-dashboard/plugins/vega/index.css HTTP/1.1" 400 0 "https://data.panzura.com/ki-dashboard/app/kibana?time_filter=true&cluster_id=some_cluster_id" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.36"

45.18.32.237 - - [09/Jun/2023:15:19:46 +0000] "GET / ki-dashboard/plugins/tile_map/index.css HTTP/1.1" 400 0 "https://data.panzura.com/ki-dashboard/app/kibana?time_filter=true&cluster_id=some_cluster_id" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.36"

The proxy, reverse proxy and load balancer does not show any blocker action for this files.

Any idea on why this is happening?

Regards

Diego Duarte

2

Hi @duartera,

Can you confirm which version of Elasticsearch/ Kibana you are using? Are you using a self-managed installation?

3

Hi @carly.richmond

Elasticsearch/Kibana version: 6.5.4

We are using a self-managed installation.

Regards

4

Hi @duartera,

Thanks for confirming. You are using a very old version that is no longer supported as per the support matrix. Are you able to upgrade to try and remediate the issue?

5

Understood, currently we can not to upgrade the version we are using.

Is there any documentation I can read about this error?

Regards

6

I've had a quick scan through our docs and Kibana GitHub issues but can't find anything relevant. The error is pretty generic, so I think more information is required to find the true cause.

I would recommend trying out some of the suggestions in the below resources to try and get more information:

  1. How to Fix a 400 Bad Request Error (Causes and Fixes) | Kinsta
  2. Kibana Troubleshooting v6.5.x
  3. Kibana Troubleshooting v.8.8.x- warning that the logs steps may be different, but I can't seem to find equivalent resources for your version

Hope that helps!

7

Thanks Carly, let me try to gather more data and I'll get back to you.

Very appreciated.

Regards.

8

I do not see any indices within the ELK clusters that have the monitoring names like the document in the 2nd point describe, any idea on how to get/enable/activate that Monitor feature?

Regards

9

I didn't see any in the v6 documentation for the second link sadly, so it was a bit of a long shot. Any luck with the steps in the first link?

10

Hi @carly.richmond

No luck with the steps in the first link, the issue is completely random and these days I haven't be able to reproduce the error again.

  1. URL String Syntax Error: The URL Strings are ok
  2. Corrupted Browser Cache & Cookies: No cache or cookies corrupted
  3. DNS Lookup Cache: We flush the cache
  4. File Size Too Large: The file size is not that large
  5. Generic Server Error: No errors in the server side

Anything else I can try to identify this issue?

We are worried because some clients are facing this error in our prod environment.

Regards

11

Hi @duartera,

I understand these errors are concerning. I've not tried with v6.x, so I'm not 100% sure it will work. But you could have a look at the tracing using either APM or Chrome DevTools as per the steps in these blogs to try and find more information on the erroring calls. Otherwise I would strongly recommend an upgrade.

Hope that helps!

12

Hi @carly.richmond

I'll try to setup the APM service to see more detailed logs in the future. Hopefully this will point to us the root cause of our current problem.

Regards !

1 Like
13

Hey @carly.richmond

Any guidance on how can I setup the APM service in a self-managed Kibana app?

Regards

14

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