1 Answer
- Newest
- Most votes
- Most comments
0
Two things of note:
First, processes can receive a signal that tells them that the system is going into hibernation. How they react to that is up to them but one possible action is that they terminate.
Second, network connections will most likely be broken when a hibernating instance is resumed because the remote end has timed out and not received any keepalives from the instance. This is probably going to be true for local processes that are communicating with each other via the network (even though the connections are internal) - the kernel will (again, probably) drop them due to timeout. This could cause the symptoms you're seeing.
I'm not sure this is a great answer but it's a possibility.
Relevant content
- asked a year ago
- Accepted Answerasked 6 years ago
- asked 5 years ago
- asked a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated 2 years ago