Hi,
I'm a bit at a los here, today i upgrade my 7.10.0 dev-cluster to 7.11.0 and when i go to fleet in kibana i get en nice red box "Unable to initialize Fleet - An internal server error occurred".
Lets rewind a bit, i started playing with ingest manager on 7.9.2 and fiddled arround a bit and let it rest due to time constraints. When 7.10 came out i upgraded the cluster and remember it working under the new name fleet, fast forward a month or so and i noticed the red box all of the sudden and again let is be for future me to solve. Enter 7.11 thinking maybe it would solve the issue but nevertheless still got the same init failure.
So now i deciced to investigate;
Kibana gives me ample logs from just the request done by me in the browser to a a message about a transform to a timeout and a clear error, nothing in between..
{"type":"response","@timestamp":"2021-02-15T22:23:47+01:00","tags":["access:fleet-read"],"pid":6159,"method":"get","statusCode":200,"req":{"url":"/api/fleet/agents/setup","method":"get","headers":{"host":"kib01.tld.local:5601","connection":"keep-alive","kbn-version":"7.11.0","user-agent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/88.0.4324.150 Safari/537.36","content-type":"application/json","accept":"*/*","sec-fetch-site":"same-origin","sec-fetch-mode":"cors","sec-fetch-dest":"empty","referer":"https://kib01.tld.local:5601/app/fleet","accept-encoding":"gzip, deflate, br","accept-language":"nl-NL,nl;q=0.9,en-US;q=0.8,en;q=0.7"},"remoteAddress":"10.40.31.75","userAgent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/88.0.4324.150 Safari/537.36","referer":"https://kib01.tld.local:5601/app/fleet"},"res":{"statusCode":200,"responseTime":53,"contentLength":9},"message":"GET /api/fleet/agents/setup 200 53ms - 9.0B"}
{"type":"log","@timestamp":"2021-02-15T22:23:47+01:00","tags":["debug","plugins","security","basic","basic"],"pid":6159,"message":"Trying to authenticate user request to /api/fleet/setup."}
{"type":"log","@timestamp":"2021-02-15T22:23:47+01:00","tags":["debug","plugins","security","basic","basic"],"pid":6159,"message":"Trying to authenticate via state."}
{"type":"log","@timestamp":"2021-02-15T22:23:47+01:00","tags":["debug","plugins","security","basic","basic"],"pid":6159,"message":"Request has been authenticated via state."}
{"type":"log","@timestamp":"2021-02-15T22:23:47+01:00","tags":["debug","plugins","security","api-authorization"],"pid":6159,"message":"User authorized for \"/api/fleet/setup\""}
The transform log message
{"type":"log","@timestamp":"2021-02-15T22:23:57+01:00","tags":["info","plugins","fleet"],"pid":6159,"message":"Found previous transform references:\n [{\"id\":\"endpoint.metadata_current-default-0.16.1\",\"type\":\"transform\"}]"}
{"type":"log","@timestamp":"2021-02-15T22:23:57+01:00","tags":["info","plugins","fleet"],"pid":6159,"message":"Deleting currently installed transform ids endpoint.metadata_current-default-0.16.1"}
And finally the time-out and error
{"type":"log","@timestamp":"2021-02-15T22:24:27+01:00","tags":["error","plugins","fleet"],"pid":6159,"message":"Request Timeout after 30000ms"}
{"type":"log","@timestamp":"2021-02-15T22:24:27+01:00","tags":["error","http"],"pid":6159,"message":"Error: options.statusCode is expected to be set. given options: undefined\n at Object.customError (/usr/share/kibana/src/core/server/http/router/response.js:136:13)\n at defaultIngestErrorHandler (/usr/share/kibana/x-pack/plugins/fleet/server/errors/handlers.js:117:19)\n at FleetSetupHandler (/usr/share/kibana/x-pack/plugins/fleet/server/routes/setup/handlers.js:111:50)\n at processTicksAndRejections (internal/process/task_queues.js:93:5)\n at Router.handle (/usr/share/kibana/src/core/server/http/router/router.js:163:30)\n at handler (/usr/share/kibana/src/core/server/http/router/router.js:124:50)\n at module.exports.internals.Manager.execute (/usr/share/kibana/node_modules/@hapi/hapi/lib/toolkit.js:45: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:312:32)\n at Request._execute (/usr/share/kibana/node_modules/@hapi/hapi/lib/request.js:221:9)"}
{"type":"error","@timestamp":"2021-02-15T22:23:47+01:00","tags":[],"pid":6159,"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:58:19)\n at Router.handle (/usr/share/kibana/src/core/server/http/router/router.js:177:34)\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 module.exports.internals.Manager.execute (/usr/share/kibana/node_modules/@hapi/hapi/lib/toolkit.js:45: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:312:32)\n at Request._execute (/usr/share/kibana/node_modules/@hapi/hapi/lib/request.js:221:9)"},"url":"https://kib01.tld.local:5601/api/fleet/setup","message":"Internal Server Error"}
- epr.elastic.co i can reach from the kibana server and get reponse on the API. Also logs don't show that its timing out on package registry.
At first i tought it was the same as this issue.
But it didnt match 100% with its server logs and other evidence, still i cannot get rid of that transform job, or it dissapeared when 7.11 was installed. Also cant stop or start it because elastic says it has started.
Its an old job what i'm guessing (as you can see from last year) was the same issue in the link when on 7.10 but now got stuck in some twilight zone on 7.11.
- Is my assumption correct linking fleet not starting on this?
- Any ideas on how can i correct this?
- Or can it be a different reason why fleet is not starting anymore?
Just throwing a small bit of spagetti, thanks in advance!