Can't log into Elastic (self hosted) "Oops! Error. Try again."

Elastic Stack Kibana
1

If I want to log in it just says "Oops! Error. Try again.".
The credentials are definitely right (if I change the password to random it says that the login/password is wrong and doesn't give this error).
I can't find any related errors in kibana.log

Any help would be appreciated.

2

Any errors in elastic logs?

3

Yeah there are a bunch of them. They may have to do with that my disk is pretty full (but not 100%). As seen in my other threat I had to manually enable some index again. The problem is I can't free up disc space, as I have to log in to Kibana to do that.

Here are the logs with | grep error from a few minutes back:

elk_server.json:

elk.log:

4

I correct myself. I found relevant kibana.log error here:

{"type":"log","@timestamp":"2021-05-31T15:04:21+02:00","tags":["error","plugins","taskManager"],"pid":116874,"message":"Failed to poll for work: Error: work has timed out"}
{"type":"log","@timestamp":"2021-05-31T15:04:51+02:00","tags":["error","plugins","taskManager"],"pid":116874,"message":"Failed to poll for work: Error: work has timed out"}
{"type":"log","@timestamp":"2021-05-31T15:05:21+02:00","tags":["error","plugins","taskManager"],"pid":116874,"message":"Failed to poll for work: Error: work has timed out"}
{"type":"log","@timestamp":"2021-05-31T15:05:25+02:00","tags":["error","plugins","security","session","index"],"pid":116874,"message":"Failed to create session value: cluster_block_exception"}
{"type":"log","@timestamp":"2021-05-31T15:05:25+02:00","tags":["error","plugins","security","routes"],"pid":116874,"message":"ResponseError: cluster_block_exception\n    at onBody (/usr/share/kibana/node_modules/@elastic/elasticsearch/lib/Transport.js:333:23)\n    at IncomingMessage.onEnd (/usr/share/kibana/node_modules/@elastic/elasticsearch/lib/Transport.js:260:11)\n    at IncomingMessage.emit (events.js:327:22)\n    at endReadableNT (internal/streams/readable.js:1327:12)\n    at processTicksAndRejections (internal/process/task_queues.js:80:21) {\n  meta: {\n    body: { error: [Object], status: 429 },\n    statusCode: 429,\n    headers: {\n      'content-type': 'application/json; charset=UTF-8',\n      'content-length': '435'\n    },\n    meta: {\n      context: null,\n      request: [Object],\n      name: 'elasticsearch-js',\n      connection: [Object],\n      attempts: 0,\n      aborted: false\n    }\n  }\n}"}
{"type":"error","@timestamp":"2021-05-31T15:05:25+02:00","tags":[],"pid":116874,"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:121:19)\n    at HapiResponseAdapter.toHapiResponse (/usr/share/kibana/src/core/server/http/router/response_adapter.js:75:19)\n    at HapiResponseAdapter.handle (/usr/share/kibana/src/core/server/http/router/response_adapter.js:70:17)\n    at Router.handle (/usr/share/kibana/src/core/server/http/router/router.js:164:34)\n    at runMicrotasks (<anonymous>)\n    at processTicksAndRejections (internal/process/task_queues.js:93:5)\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":"http://192.168.178.83:5601/internal/security/login","message":"Internal Server Error"}
``
5

Solved it by cleaning even more indices. Now it works again.

1 Like
6

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