Internal server error: /api/kibana/suggestions/values/Default

Elastic Stack Kibana
1

Hi, my Kibana instance seems to be encountering this internal server error from time to time. Does anyone know why?

{
  "type": "error",
  "@timestamp": "2020-09-24T01:37:50Z",
  "tags": [],
  "pid": 846,
  "level": "error",
  "error": {
    "message": "Internal Server Error",
    "name": "Error",
    "stack": "Error: Internal Server Error\n    at HapiResponseAdapter.toError (/usr/share/kibana/src/core/server/http/router/response_adapter.js:132:19)\n    at HapiResponseAdapter.toHapiResponse (/usr/share/kibana/src/core/server/http/router/response_adapter.js:86:19)\n    at HapiResponseAdapter.handle (/usr/share/kibana/src/core/server/http/router/response_adapter.js:81:17)\n    at Router.handle (/usr/share/kibana/src/core/server/http/router/router.js:162:34)\n    at process._tickCallback (internal/process/next_tick.js:68:7)"
  },
  "url": {
    "protocol": null,
    "slashes": null,
    "auth": null,
    "host": null,
    "port": null,
    "hostname": null,
    "hash": null,
    "search": null,
    "query": {},
    "pathname": "/api/kibana/suggestions/values/Default",
    "path": "/api/kibana/suggestions/values/Default",
    "href": "/api/kibana/suggestions/values/Default"
  },
  "message": "Internal Server Error"
}
1 Like
2

This route is fetching the suggestions for the query bar. It is basically doing a terms aggregation. Can you check the Elasticsearch logs whether anything in there correlates with these errors?

3

Hi @flash1293,

Thanks for the response. I don't see much of anything in the logs. This is all it has which seems to be a few days old:

[2020-09-21T16:34:15,529][INFO ][o.e.i.b.HierarchyCircuitBreakerService] [logs1] attempting to trigger G1GC due to high heap usage [6121484288]
[2020-09-21T16:34:15,753][INFO ][o.e.i.b.HierarchyCircuitBreakerService] [logs1] GC did bring memory usage down, before [6121484288], after [2268925952], allocations [136], duration [226]
[2020-09-21T16:34:49,945][INFO ][o.e.i.b.HierarchyCircuitBreakerService] [logs1] attempting to trigger G1GC due to high heap usage [6128232592]
[2020-09-21T16:34:50,071][INFO ][o.e.i.b.HierarchyCircuitBreakerService] [logs1] GC did bring memory usage down, before [6128232592], after [2750156432], allocations [147], duration [125]

But heap seems to be fine on all nodes (60-70%).

4

This doesn't seem related. Which version of Kibana are you running?

5

Both Elasticsearch and Kibana are on version 7.9.0.

6

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