Kibana 7.1启动报错Status changed from yellow to red 求指导

log   [02:03:07.098] [error][status][plugin:xpack_main@7.1.1] Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.
  log   [02:03:07.098] [error][status][plugin:graph@7.1.1] Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.
  log   [02:03:07.099] [error][status][plugin:spaces@7.1.1] Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.
  log   [02:03:07.099] [error][status][plugin:security@7.1.1] Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.
  log   [02:03:07.099] [error][status][plugin:searchprofiler@7.1.1] Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.
  log   [02:03:07.099] [error][status][plugin:ml@7.1.1] Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.
  log   [02:03:07.100] [error][status][plugin:tilemap@7.1.1] Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.
  log   [02:03:07.100] [error][status][plugin:watcher@7.1.1] Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.
  log   [02:03:07.100] [error][status][plugin:grokdebugger@7.1.1] Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.
  log   [02:03:07.100] [error][status][plugin:logstash@7.1.1] Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.
  log   [02:03:07.101] [error][status][plugin:beats_management@7.1.1] Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.
  log   [02:03:07.102] [error][status][plugin:maps@7.1.1] Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.
  log   [02:03:07.102] [error][status][plugin:index_management@7.1.1] Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.
  log   [02:03:07.102] [error][status][plugin:index_lifecycle_management@7.1.1] Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.
  log   [02:03:07.102] [error][status][plugin:rollup@7.1.1] Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.
  log   [02:03:07.103] [error][status][plugin:remote_clusters@7.1.1] Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.
  log   [02:03:07.103] [error][status][plugin:cross_cluster_replication@7.1.1] Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.
  log   [02:03:07.492] [warning][reporting] Generating a random key for xpack.reporting.encryptionKey. To prevent pending reports from failing on restart, please set xpack.reporting.encryptionKey in kibana.yml
  log   [02:03:07.513] [error][status][plugin:reporting@7.1.1] Status changed from uninitialized to red - [data] Elasticsearch cluster did not respond with license information.
  log   [02:03:07.549] [warning][reporting] The Reporting plugin encountered issues launching Chromium in a self-test. You may have trouble generating reports: Error: Failed to launch chrome!
[0822/100307.516367:WARNING:resource_bundle.cc(358)] locale_file_path.empty() for locale 
[0822/100307.516714:ERROR:zygote_host_impl_linux.cc(89)] Running as root without --no-sandbox is not supported. See https://crbug.com/638180.


TROUBLESHOOTING: https://github.com/GoogleChrom ... ng.md

  log   [02:03:07.550] [warning][reporting] See Chromium's log output at "/elksys/es/kibana/kibana-7.1.1-linux-x86_64/data/headless_shell-linux/chrome_debug.log"
 error  [02:03:37.081] [warning][process] UnhandledPromiseRejectionWarning: Error: Request Timeout after 30000ms
    at /elksys/es/kibana/kibana-7.1.1-linux-x86_64/node_modules/elasticsearch/src/lib/transport.js:355:15
    at Timeout.<anonymous> (/elksys/es/kibana/kibana-7.1.1-linux-x86_64/node_modules/elasticsearch/src/lib/transport.js:384:7)
    at ontimeout (timers.js:436:11)
    at tryOnTimeout (timers.js:300:5)
    at listOnTimeout (timers.js:263:5)
    at Timer.processTimers (timers.js:223:10)
    at emitWarning (internal/process/promises.js:81:15)
    at emitPromiseRejectionWarnings (internal/process/promises.js:120:9)
    at process._tickCallback (internal/process/next_tick.js:69:34)
 error  [02:03:37.082] [warning][process] Error: Request Timeout after 30000ms
    at /elksys/es/kibana/kibana-7.1.1-linux-x86_64/node_modules/elasticsearch/src/lib/transport.js:355:15
    at Timeout.<anonymous> (/elksys/es/kibana/kibana-7.1.1-linux-x86_64/node_modules/elasticsearch/src/lib/transport.js:384:7)
    at ontimeout (timers.js:436:11)
    at tryOnTimeout (timers.js:300:5)
    at listOnTimeout (timers.js:263:5)
    at Timer.processTimers (timers.js:223:10)
  log   [02:03:37.497] [warning][reporting] Could not retrieve cluster settings, because of Request Timeout after 30000ms
  log   [02:03:37.545] [warning][task_manager] PollError Request Timeout after 30000ms
  log   [02:03:37.546] [warning][maps] Error scheduling telemetry task, received NotInitialized: Tasks cannot be scheduled until after task manager is initialized!
  log   [02:03:37.546] [warning][telemetry] Error scheduling task, received NotInitialized: Tasks cannot be scheduled until after task manager is initialized!
  log   [02:04:07.553] [fatal][root] { Error: Request Timeout after 30000ms
    at /elksys/es/kibana/kibana-7.1.1-linux-x86_64/node_modules/elasticsearch/src/lib/transport.js:355:15
    at Timeout.<anonymous> (/elksys/es/kibana/kibana-7.1.1-linux-x86_64/node_modules/elasticsearch/src/lib/transport.js:384:7)
    at ontimeout (timers.js:436:11)
    at tryOnTimeout (timers.js:300:5)
    at listOnTimeout (timers.js:263:5)
    at Timer.processTimers (timers.js:223:10)
  status: undefined,
  displayName: 'RequestTimeout',
  message: 'Request Timeout after 30000ms',
  body: undefined,
  isBoom: true,
  isServer: true,
  data: null,
  output:
   { statusCode: 503,
     payload:
      { statusCode: 503,
        error: 'Service Unavailable',
        message: 'Request Timeout after 30000ms' },
     headers: {} },
  reformat: [Function],
  [Symbol(SavedObjectsClientErrorCode)]: 'SavedObjectsClient/esUnavailable' }

 FATAL  Error: Request Timeout after 30000ms