- 最新
- 投票最多
- 评论最多
I just found this and hope this response helps. Generally instance status check failure usually occurs due to the following reasons:
- Startup configuration
- Exhausted memory
- Corrupted file system
- Incompatible kernel (Operating System itself)
- Some script causing the issue
The error " Could not set DHCPv4 address" is not a cause but a symptom of Connectivity issues and just shows the instance was unable to communicate outbound to renew its dhcp lease. What it does not say is what was blocking the connection. The same blockage would have likely prevented healthchecks from succeeding hence the status check failure.
Most common cause of the issue is an Internal Firewall. From my experience, I have seen a few dhcp lease renewal failures where servers are running Trend DSA. You can verify if there is any security agent installed on the OS.
If the system logs like syslog are still available, I would also recommend checking to see if they contain any errors/logs indicating memory exhaustion?
The Cloudwatch logs might no longer be available due to time, however, checking to see if there was a spike in Network In/Out traffic around the time of the status check failures can also be a good indicator of why status checks failed.
相关内容
- AWS 官方已更新 1 年前