|
Running sync utility didn't help to get powercycle on Windows more stable. We are still getting ssh connection issues after server crash:
https://spruce.mongodb.com/version/6047551c32f41751df136ccd/tasks
Meanwhile found the steps to repro ssh connection issue:
- Spawn windows host
- Download notmyfault
- Run notmyfaultc64.exe -accepteula crash 1 command that we use in powercycle
- After a while I couldn't connect into the host:
$ ssh Administrator@ec2-18-203-134-37.eu-west-1.compute.amazonaws.com
|
ssh: connect to host ec2-18-203-134-37.eu-west-1.compute.amazonaws.com port 22: Connection refused
|
Also tried to run shutdown /r /f /t 0 command instead of notmyfault and got the same result.
Most likely in some cases setup script (or aws user data script) is not running on server startup after server crash/shutdown.
From aws docs:
By default, the user data scripts are run one time when you launch the instance. To run the user data scripts every time you reboot or start the instance, add <persist>true</persist> to the user data.
|
We have this in our user data, but it's still not running sometimes.
|