- Newest
- Most votes
- Most comments
Hello.
How about trying to force a reboot by adding the "-f" option as shown below?
I think the following stackoverflow answers will be helpful.
https://stackoverflow.com/questions/37220723/how-to-cleanly-reboot-core-os-when-failed-to-talk-to-init-daemon-is-seen
sudo reboot -f
Hi,
Amazon linux works with systemd: see FAQ: https://aws.amazon.com/amazon-linux-2/faqs/
Newer Linux versions work with the init daemon: see https://web.yueh.dev/learning/init-vs-systemd-what-is-an-init-daemon
So, probably, there is a component that you added to the EC2 AMI that needs init daemon which is the new system replacing systemd to start services on Linux.
So, since AL v2 is close to EOL and you seem to be starting something new, I'd suggest to go with AL 2023 where you may avoid this issue.
Best,
Didier
Relevant content
- asked 4 years ago
- AWS OFFICIALUpdated 2 months ago
