uwe_keim reports that their Ubuntu EC2 instance became unreachable after a Discourse upgrade, with no SSH or HTTP access. Despite multiple reboots, the system remained unresponsive, though it eventually recovered on its own. neounix suggests checking disk space, which uwe_keim later confirms was not the issue, as the root filesystem had 67G free. The user also shares a follow-up question on AskUbuntu for further troubleshooting. neounix expresses relief at the recovery.
Using AWS EC2 Linux/Ubuntu instances successfully for years, I am facing an issue today, that I’m unable to resolve:
I did an upgrade of Discourse through the /admin/upgrade URL. This seemed to have run through successfully.
Unfortunately after that, the machine is dead.
No HTTP access, not SSH access.
I already tried to switch it on and off via AWS EC2 web GUI. No success.
It is currently impossible to connect via SSH to the machine, not via Putty and also not via the web based AWS EC2 instance connection terminal window.
I’m really clueless and already did wait for several hours.
The EC2 monitoring also shows no high server load to me:
When this happened in the past weeks/months (approximately 2 or 3 times in total), rebooting the machine through the EC2 GUI always did make the machine come alive again, but not this time.
My question
Any hints on how to make the machine accessible via SSH again?
(I know that this is most likely not a Discourse issue, but since it has occurred directly after a Discourse upgrade, maybe other users already had this very same behaviour and have some hints for me)