1. Start kibana and report an error, as shown below:
1 [elsearch@master kibana-7.2.1-linux-x86_64]$ ./bin/kibana 2 log [03:09:30.348] [info][status][plugin:[email protected]] Status changed from uninitialized to green - Ready 3 log [03:09:30.362] [info][status][plugin:[email protected]] Status changed from uninitialized to yellow - Waiting for Elasticsearch 4 log [03:09:30.368] [info][status][plugin:[email protected]] Status changed from uninitialized to yellow - Waiting for Elasticsearch 5 log [03:09:30.406] [info][status][plugin:[email protected]] Status changed from uninitialized to yellow - Waiting for Elasticsearch 6 log [03:09:30.436] [info][status][plugin:[email protected]] Status changed from uninitialized to green - Ready 7 log [03:09:30.440] [info][status][plugin:[email protected]] Status changed from uninitialized to yellow - Waiting for Elasticsearch 8 log [03:09:30.451] [warning][security] Generating a random key for xpack.security.encryptionKey. To prevent sessions from being invalidated on restart, please set xpack.security.encryptionKey in kibana.yml 9 log [03:09:30.457] [warning][security] Session cookies will be transmitted over insecure connections. This is not recommended. 10 log [03:09:30.492] [info][status][plugin:[email protected]] Status changed from uninitialized to green - Ready 11 log [03:09:30.499] [info][status][plugin:[email protected]] Status changed from uninitialized to yellow - Waiting for Elasticsearch 12 log [03:09:30.503] [info][status][plugin:[email protected]] Status changed from uninitialized to yellow - Waiting for Elasticsearch 13 log [03:09:30.586] [info][status][plugin:[email protected]] Status changed from uninitialized to yellow - Waiting for Elasticsearch 14 log [03:09:30.588] [info][status][plugin:[email protected]] Status changed from uninitialized to yellow - Waiting for Elasticsearch 15 log [03:09:30.607] [info][status][plugin:[email protected]] Status changed from uninitialized to yellow - Waiting for Elasticsearch 16 log [03:09:30.619] [info][status][plugin:[email protected]] Status changed from uninitialized to green - Ready 17 log [03:09:30.621] [info][status][plugin:[email protected]] Status changed from uninitialized to yellow - Waiting for Elasticsearch 18 log [03:09:30.632] [info][status][plugin:[email protected]] Status changed from uninitialized to yellow - Waiting for Elasticsearch 19 log [03:09:30.657] [info][status][plugin:[email protected]] Status changed from uninitialized to green - Ready 20 log [03:09:30.675] [info][status][plugin:[email protected]] Status changed from uninitialized to green - Ready 21 log [03:09:30.678] [info][status][plugin:[email protected]] Status changed from uninitialized to green - Ready 22 log [03:09:30.681] [info][status][plugin:[email protected]] Status changed from uninitialized to green - Ready 23 log [03:09:30.684] [info][status][plugin:[email protected]] Status changed from uninitialized to green - Ready 24 log [03:09:30.695] [info][status][plugin:[email protected]] Status changed from uninitialized to yellow - Waiting for Elasticsearch 25 log [03:09:30.719] [info][status][plugin:[email protected]] Status changed from uninitialized to green - Ready 26 log [03:09:30.757] [info][status][plugin:[email protected]] Status changed from uninitialized to green - Ready 27 log [03:09:30.766] [info][status][plugin:[email protected]] Status changed from uninitialized to green - Ready 28 log [03:09:30.768] [info][status][plugin:[email protected]] Status changed from uninitialized to green - Ready 29 log [03:09:30.772] [info][status][plugin:[email protected]] Status changed from uninitialized to yellow - Waiting for Elasticsearch 30 log [03:09:30.797] [info][status][plugin:[email protected]] Status changed from uninitialized to green - Ready 31 log [03:09:30.806] [info][status][plugin:[email protected]] Status changed from uninitialized to green - Ready 32 log [03:09:30.813] [info][status][plugin:[email protected]] Status changed from uninitialized to green - Ready 33 log [03:09:30.815] [info][status][plugin:[email protected]] Status changed from uninitialized to yellow - Waiting for Elasticsearch 34 log [03:09:30.837] [info][status][plugin:[email protected]] Status changed from uninitialized to green - Ready 35 log [03:09:30.879] [info][status][plugin:[email protected]] Status changed from uninitialized to green - Ready 36 log [03:09:30.881] [info][status][plugin:[email protected]] Status changed from uninitialized to yellow - Waiting for Elasticsearch 37 log [03:09:30.897] [info][siem] Plugin initializing 38 log [03:09:30.940] [info][siem] Plugin done initializing 39 log [03:09:30.941] [info][status][plugin:[email protected]] Status changed from uninitialized to green - Ready 40 log [03:09:30.945] [info][status][plugin:[email protected]] Status changed from uninitialized to yellow - Waiting for Elasticsearch 41 log [03:09:30.957] [info][status][plugin:[email protected]] Status changed from uninitialized to yellow - Waiting for Elasticsearch 42 log [03:09:30.972] [info][status][plugin:[email protected]] Status changed from uninitialized to green - Ready 43 log [03:09:30.988] [info][status][plugin:[email protected]] Status changed from uninitialized to green - Ready 44 log [03:09:31.008] [info][status][plugin:[email protected]] Status changed from uninitialized to green - Ready 45 log [03:09:31.012] [info][status][plugin:[email protected]] Status changed from uninitialized to green - Ready 46 log [03:09:31.016] [warning][encrypted_saved_objects] Generating a random key for xpack.encrypted_saved_objects.encryptionKey. To be able to decrypt encrypted saved objects attributes after restart, please set xpack.encrypted_saved_objects.encryptionKey in kibana.yml 47 log [03:09:31.017] [info][status][plugin:[email protected]] Status changed from uninitialized to green - Ready 48 log [03:09:31.035] [info][status][plugin:[email protected]] Status changed from uninitialized to yellow - Waiting for Elasticsearch 49 log [03:09:31.043] [info][status][plugin:[email protected]] Status changed from uninitialized to green - Ready 50 log [03:09:31.258] [info][status][plugin:[email protected]] Status changed from uninitialized to green - Ready 51 log [03:09:31.263] [info][status][plugin:[email protected]] Status changed from uninitialized to green - Ready 52 log [03:09:32.365] [info][status][plugin:[email protected]] Status changed from yellow to green - Ready 53 log [03:09:32.909] [info][license][xpack] Imported license information from Elasticsearch for the [data] cluster: mode: basic | status: active 54 log [03:09:32.964] [info][status][plugin:[email protected]] Status changed from yellow to green - Ready 55 log [03:09:32.965] [info][status][plugin:[email protected]] Status changed from yellow to green - Ready 56 log [03:09:32.970] [info][status][plugin:[email protected]] Status changed from yellow to green - Ready 57 log [03:09:32.976] [info][status][plugin:[email protected]] Status changed from yellow to green - Ready 58 log [03:09:32.979] [info][status][plugin:[email protected]] Status changed from yellow to green - Ready 59 log [03:09:32.986] [info][status][plugin:[email protected]] Status changed from yellow to green - Ready 60 log [03:09:32.988] [info][status][plugin:[email protected]] Status changed from yellow to green - Ready 61 log [03:09:32.989] [info][status][plugin:[email protected]] Status changed from yellow to green - Ready 62 log [03:09:32.991] [info][status][plugin:[email protected]] Status changed from yellow to green - Ready 63 log [03:09:32.992] [info][status][plugin:[email protected]] Status changed from yellow to green - Ready 64 log [03:09:32.993] [info][status][plugin:[email protected]] Status changed from yellow to green - Ready 65 log [03:09:32.994] [info][status][plugin:[email protected]] Status changed from yellow to green - Ready 66 log [03:09:32.996] [info][status][plugin:[email protected]] Status changed from yellow to green - Ready 67 log [03:09:32.997] [info][status][plugin:[email protected]] Status changed from yellow to green - Ready 68 log [03:09:32.998] [info][status][plugin:[email protected]] Status changed from yellow to green - Ready 69 log [03:09:33.000] [info][kibana-monitoring][monitoring] Starting monitoring stats collection 70 log [03:09:33.029] [info][status][plugin:[email protected]] Status changed from yellow to green - Ready 71 log [03:09:36.580] [warning][browser-driver][reporting] Enabling the Chromium sandbox provides an additional layer of protection. 72 log [03:09:36.627] [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 73 log [03:09:36.696] [info][status][plugin:[email protected]] Status changed from uninitialized to green - Ready 74 error [03:10:02.387] [warning][process] UnhandledPromiseRejectionWarning: Error: Request Timeout after 30000ms 75 at /data/kibana-7.2.1-linux-x86_64/node_modules/elasticsearch/src/lib/transport.js:362:15 76 at Timeout.<anonymous> (/data/kibana-7.2.1-linux-x86_64/node_modules/elasticsearch/src/lib/transport.js:391:7) 77 at ontimeout (timers.js:436:11) 78 at tryOnTimeout (timers.js:300:5) 79 at listOnTimeout (timers.js:263:5) 80 at Timer.processTimers (timers.js:223:10) 81 at emitWarning (internal/process/promises.js:81:15) 82 at emitPromiseRejectionWarnings (internal/process/promises.js:120:9) 83 at process._tickCallback (internal/process/next_tick.js:69:34) 84 error [03:10:02.393] [warning][process] Error: Request Timeout after 30000ms 85 at /data/kibana-7.2.1-linux-x86_64/node_modules/elasticsearch/src/lib/transport.js:362:15 86 at Timeout.<anonymous> (/data/kibana-7.2.1-linux-x86_64/node_modules/elasticsearch/src/lib/transport.js:391:7) 87 at ontimeout (timers.js:436:11) 88 at tryOnTimeout (timers.js:300:5) 89 at listOnTimeout (timers.js:263:5) 90 at Timer.processTimers (timers.js:223:10) 91 log [03:10:06.696] [warning][reporting] Reporting plugin self-check failed. Please check the Kibana Reporting settings. Error: Request Timeout after 30000ms 92 log [03:10:06.784] [warning][task_manager] PollError Request Timeout after 30000ms 93 log [03:10:06.787] [warning][maps] Error scheduling telemetry task, received NotInitialized: Tasks cannot be scheduled until after task manager is initialized! 94 log [03:10:06.790] [warning][telemetry] Error scheduling task, received NotInitialized: Tasks cannot be scheduled until after task manager is initialized! 95 log [03:10:36.807] [error][status][plugin:[email protected]] Status changed from yellow to red - Request Timeout after 30000ms 96 log [03:10:36.813] [fatal][root] { Error: Request Timeout after 30000ms 97 at /data/kibana-7.2.1-linux-x86_64/node_modules/elasticsearch/src/lib/transport.js:362:15 98 at Timeout.<anonymous> (/data/kibana-7.2.1-linux-x86_64/node_modules/elasticsearch/src/lib/transport.js:391:7) 99 at ontimeout (timers.js:436:11) 100 at tryOnTimeout (timers.js:300:5) 101 at listOnTimeout (timers.js:263:5) 102 at Timer.processTimers (timers.js:223:10) 103 status: undefined, 104 displayName: 'RequestTimeout', 105 message: 'Request Timeout after 30000ms', 106 body: undefined, 107 isBoom: true, 108 isServer: true, 109 data: null, 110 output: 111 { statusCode: 503, 112 payload: 113 { statusCode: 503, 114 error: 'Service Unavailable', 115 message: 'Request Timeout after 30000ms' }, 116 headers: {} }, 117 reformat: [Function], 118 [Symbol(SavedObjectsClientErrorCode)]: 'SavedObjectsClient/esUnavailable' } 119 120 FATAL Error: Request Timeout after 30000ms
2. Solution.
2.1. The first solution is to increase the request duration of kibana’s request to es, as shown below:
1 elasticsearch.requestTimeout: 50000
2.2. Adjust the jvm parameter of /data/elasticsearch-7.2.1/config/jvm.options. Increase the memory size as follows:
The default is 1gb. If you want to change your virtual machine to 2gb, you need at least 3gb for the virtual machine. My memory is 4gb. Then if you give 2gb memory and adjust these two parameters to 2gb, start it directly Report insufficient memory error.
1 ################################################################ 2 3 # Xms represents the initial size of total heap space 4 # Xmx represents the maximum size of total heap space 5 6 -Xms2g 7 -Xmx2g 8 9 ################################################################
Similar Posts:
- [Solved] K8s EFK Install Error: Cluster is not yet ready (request params: “wait_for_status=green&timeout=1s”)
- [Solved] Kibana 7.14.0 error: server.publicBaseUrl is missing and should be configured when running in a production environment.
- Elasticsearch + kibana set user name and password to log in
- Kibana Connect Error: Kibana server is not ready yet [How to Solve]
- Solution of kibana starting error reporting server is not ready yet
- Elasticsearch configuration cluster + elk error Summary and Solution
- [Solved] Error encountered uploading license: Cannot install a [PLATINUM] license unless TLS is configured or security is disabled
- [Solved] Kibana Start Error: Unable to write Kibana UUID file, please check the uuid.server configuration value in kibana.yml
- [ Elasticsearch-PHP] No alive nodes found in your cluster in
- [Solved] Kibana 7.15.x [error][savedobjects-service] [.kibana] Action failed with ‘Request timed out’. Retrying attempt