search

elastic / kibana

Your window into the Elastic Stack
https://www.elastic.co/products/kibana
Other
19.63k stars 8.22k forks source link

Internal Server Error\n at HapiResponseAdapter.toInternalError - seen in the Kibana logs. #102231

Open rashmivkulkarni opened 3 years ago

rashmivkulkarni commented 3 years ago

Kibana- 8.0 snapshot build

While running our end to end integration tests, while I grep for errors in the logs, I do catch this exception

{"type":"error","@timestamp":"2021-06-14T23:00:39+00:00","tags":[],"pid":11651,"level":"error","error":{"message":"Internal Server Error","name":"Error","stack":"Error: Internal Server Error\n at HapiResponseAdapter.toInternalError (/usr/share/kibana/src/core/server/http/router/response_adapter.js:61:19)\n at Router.handle (/usr/share/kibana/src/core/server/http/router/router.js:177:34)\n at handler (/usr/share/kibana/src/core/server/http/router/router.js:124:50)\n at exports.Manager.execute (/usr/share/kibana/node_modules/@hapi/hapi/lib/toolkit.js:60:28)\n at Object.internals.handler (/usr/share/kibana/node_modules/@hapi/hapi/lib/handler.js:46:20)\n at exports.execute (/usr/share/kibana/node_modules/@hapi/hapi/lib/handler.js:31:20)\n at Request._lifecycle (/usr/share/kibana/node_modules/@hapi/hapi/lib/request.js:370:32)\n at Request._execute (/usr/share/kibana/node_modules/@hapi/hapi/lib/request.js:279:9)"},"url":"https://localhost:5601/api/actions/connector/453966b4-7ada-4f3d-a3d3-bad40bba1781/_execute","message":"Internal Server Error"}

This exception should be caught and handled appropriately in the code.

cc @LeeDr

part of : https://github.com/elastic/integration-test/issues/474

elasticmachine commented 3 years ago

Pinging @elastic/kibana-core (Team:Core)

pmuellr commented 3 years ago

I assume this is a problem with the actions plugin - though it's not quite clear - it could be a core problem in the http handling - my guess is it's the actions plugin though.

@rashmivkulkarni do you happen to know what it might have been doing at this point? This could be from the web ui using the "test" functionality of the connector edit view. Or it could be an explicit http request to Kibana to execute a connector. Could I poke through the logs, maybe I'll see something ...

pmuellr commented 3 years ago

Ah, just realized this is coming from the tests, not a typical deployment. Do we know what test?

elasticmachine commented 3 years ago

Pinging @elastic/kibana-alerting-services (Team:Alerting Services)

pmuellr commented 3 years ago

There's a Team:Core label on this issue right now, but really seems like an alerting issue, so will remove that label ...