Kibana 7.8.0 is starting with errors in Windows 10

[MuthiahPrabhakaran]

Hi,

I have downloaded ES 7.8.0 and Kibana 7.8.0 for Windows. ES is starting without an issue. But Kibana is starting with error and when I access Kibana in localhost, It shows "Select your space. You can change your space at anytime. No spaces match search criteria".

JVM Details:
java version "1.8.0_161"
Java(TM) SE Runtime Environment (build 1.8.0_161-b12)
Java HotSpot(TM) 64-Bit Server VM (build 25.161-b12, mixed mode)

OS Details:
OS Name: Microsoft Windows 10 Home
OS Version: 10.0.19041 N/A Build 19041

Provide logs:
Kibana error log.txt

[elasticmachine]

Pinging @elastic/apm-ui (Team:apm)

[TinaHeiligers]

@elastic/apm-ui I added your team label because the errors in the Kibana error log.txt all appear to be generated by the apm plugin.
e.g.

log   [03:42:02.648] [warning][apm][plugins] Could not create index: '.apm-agent-configuration'. Retrying...
log   [03:42:02.683] [warning][apm][plugins] { Error: [cluster_block_exception] index [.apm-agent-configuration] blocked by: [TOO_MANY_REQUESTS/12/index read-only / allow delete (api)];
    at respond (C:\Users\Dallps\Documents\softwares\kibana-7.8.0-windows-x86_64\kibana-7.8.0-windows-x86_64\node_modules\elasticsearch\src\lib\transport.js:349:15)
    at checkRespForFailure (C:\Users\Dallps\Documents\softwares\kibana-7.8.0-windows-x86_64\kibana-7.8.0-windows-x86_64\node_modules\elasticsearch\src\lib\transport.js:306:7)
    at HttpConnector.<anonymous> (C:\Users\Dallps\Documents\softwares\kibana-7.8.0-windows-x86_64\kibana-7.8.0-windows-x86_64\node_modules\elasticsearch\src\lib\connectors\http.js:173:7)
    at IncomingMessage.wrapper (C:\Users\Dallps\Documents\softwares\kibana-7.8.0-windows-x86_64\kibana-7.8.0-windows-x86_64\node_modules\elasticsearch\node_modules\lodash\lodash.js:4929:19)
    at IncomingMessage.emit (events.js:203:15)
    at endReadableNT (_stream_readable.js:1145:12)
    at process._tickCallback (internal/process/next_tick.js:63:19)
  status: 429,
  displayName: 'TooManyRequests',
  message:
   '[cluster_block_exception] index [.apm-agent-configuration] blocked by: [TOO_MANY_REQUESTS/12/index read-only / allow delete (api)];',
  path: '/.apm-agent-configuration/_mapping',
  query: {},
  body:
   { error:
      { root_cause: [Array],
        type: 'cluster_block_exception',
        reason:
         'index [.apm-agent-configuration] blocked by: [TOO_MANY_REQUESTS/12/index read-only / allow delete (api)];' },
     status: 429 },
  statusCode: 429,
  response:
   '{"error":{"root_cause":[{"type":"cluster_block_exception","reason":"index [.apm-agent-configuration] blocked by: [TOO_MANY_REQUESTS/12/index read-only / allow delete (api)];"}],"type":"cluster_block_exception","reason":"index [.apm-agent-configuration] blocked by: [TOO_MANY_REQUESTS/12/index read-only / allow delete (api)];"},"status":429}',
  toString: [Function],
  toJSON: [Function],
  attemptNumber: 1,
  retriesLeft: 10 }

[sorenlouv]

Could this error message be a symptom of a completely separate issue: namely that disk is full? See elastic/elasticsearch#58410

[sorenlouv]

@MuthiahPrabhakaran If you've been running out of disk space the indices are automatically changes to read-only. To re-enable write-mode for an index you can run from Kibana Dev Tools:

PUT .apm-agent-configuration/_settings
{
  "index": {
    "blocks": {
      "read_only_allow_delete": "false"
    }
  }
}

Or perhaps:

PUT _settings
{
  "index": {
    "blocks": {
      "read_only_allow_delete": "false"
    }
  }
}

[MuthiahPrabhakaran]

@sqren Thanks. Let me try this. Meanwhile, I moved the sources to a different drive and tried to start ES and Kibana. It works.
FYI, In the existing drive where I tried to start Kibana, there is 26GB free memory.