- Newest
- Most votes
- Most comments
I've hit a very similar problem on two of my instances in the last week.
First on instance i-0daac824ee4991919:
Aug 20 17:00:40 process systemd-networkd[62536]: ens5: DHCPv6 address 2600:1f16:216:7c64:ab39:691d:992f:3817/128 timeout preferred 150 valid 450
Aug 20 17:01:50 process systemd-networkd[62536]: ens5: Could not set DHCPv6 address: Connection timed out
Aug 20 17:03:33 process systemd-networkd[62536]: ens5: Failed
And then on instance i-0fbfc3151b977c780:
Aug 23 13:00:10 process systemd-networkd[58373]: ens5: DHCPv6 address 2600:1f16:216:7c80:abdb:db3c:fcfd:20fd/128 timeout preferred 150 valid 450
Aug 23 13:01:37 process systemd-networkd[58373]: ens5: Could not set NDisc route or address: Connection timed out
Aug 23 13:03:59 process systemd-networkd[58373]: ens5: Failed
In both cases, the problem seems to be two fold: The first is that the instance is getting very slow, there seem to be many different things that can trigger this, including running out of CPU credits, running out of EBS burst credits, and possibly either running out of memory or running very close to out of memory.
The second case for me looks at least somewhat like the running out of memory situation, but I have no clue on the first case.
The second part of the problem is that it looks like systemd-networkd never tries to recover from the interface going into a Failed state, this is very confusing to me, and I'd really like to get AWS support to give us an answer on how we can resolve that. I'd also love to get some guidance on getting things like memory pressure in the instance metrics.
Relevant content
- asked 3 years ago
- asked 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago