1. Error reporting
Recently, when elasticsearch and kibana of 7.15.2 were used on the windows platform, kibana failed to start after opening the ES CMD window and reported an error.
log [09:03:50.365] [error][savedobjects-service] [.kibana] Action failed with 'Request timed out'. Retrying attempt 1 in 2 seconds. log [09:03:50.371] [info][savedobjects-service] [.kibana] UPDATE_TARGET_MAPPINGS -> UPDATE_TARGET_MAPPINGS. took: 120043ms. log [09:03:50.410] [error][savedobjects-service] [.kibana_task_manager] Action failed with 'Request timed out'. Retrying attempt 1 in 2 seconds. log [09:03:50.412] [info][savedobjects-service] [.kibana_task_manager] UPDATE_TARGET_MAPPINGS -> UPDATE_TARGET_MAPPINGS. took: 120059ms. log [09:05:52.415] [error][savedobjects-service] [.kibana] Action failed with 'Request timed out'. Retrying attempt 2 in 4 seconds. log [09:05:52.416] [info][savedobjects-service] [.kibana] UPDATE_TARGET_MAPPINGS -> UPDATE_TARGET_MAPPINGS. took: 122050ms. log [09:05:52.462] [error][savedobjects-service] [.kibana_task_manager] Action failed with 'Request timed out'. Retrying attempt 2 in 4 seconds. log [09:05:52.463] [info][savedobjects-service] [.kibana_task_manager] UPDATE_TARGET_MAPPINGS -> UPDATE_TARGET_MAPPINGS. took: 122052ms. log [09:07:56.471] [error][savedobjects-service] [.kibana] Action failed with 'Request timed out'. Retrying attempt 3 in 8 seconds. log [09:07:56.472] [info][savedobjects-service] [.kibana] UPDATE_TARGET_MAPPINGS -> UPDATE_TARGET_MAPPINGS. took: 124055ms. log [09:07:56.517] [error][savedobjects-service] [.kibana_task_manager] Action failed with 'Request timed out'. Retrying attempt 3 in 8 seconds. log [09:07:56.518] [info][savedobjects-service] [.kibana_task_manager] UPDATE_TARGET_MAPPINGS -> UPDATE_TARGET_MAPPINGS. took: 124055ms.
2. Cause
In fact, the reason is very simple. If you accidentally select any string in the CMD window started by es, the output of es will be blocked, resulting in kibana startup failure. As shown in the figure below.
3. Solution
The simplest way is to cancel the selection, press enter and ESC, and then restart kibana. Of course, it is more recommended to build es into the system service of windows to avoid similar problems. Here is the official screenshot of ES, and the operation is as follows.
Similar Posts:
- Kibana Connect Error: Kibana server is not ready yet [How to Solve]
- Solution of kibana starting error reporting server is not ready yet
- [Solved] Kibana Start Error: Unable to write Kibana UUID file, please check the uuid.server configuration value in kibana.yml
- How to Solve network error: software caused connection abort (Step-by-step Tutorial)
- [Solved] Kibana 7.14.0 error: server.publicBaseUrl is missing and should be configured when running in a production environment.
- [Solved] Nginx proxy Timeout: upstream timed out (110: Connection timed out)
- [Solved] Python urlib2gaierror: [Errno 11004] getaddrinfo failed
- How to Solve Windows setup encountered HResult: 0x80070422 Error
- idea Failed to clean project Failed to delete target
- Android Studio starts the emulator and appears “Timed out after 300seconds waiting for emulator to come online” solution