BTW, I used this guide to install v7.8 from RAW disk. I started and was happy to see that it was enabled. After no shutdown after 30 seconds I issued it again. So I went to the console and issued a Force Terminate. However at about 2m30s in the countdown was still going and AWS had not terminated the instance. Router was rebooted without proper shutdown The instance will shutdown between 3 and 4 minutes.

* On console in Instance state, it will be showing Stopping.ģ) Connect to CHR using your favorite client, to enable the container: If anyone has managed to recreate these steps, I would love a breakdown of how you managed it! Even using the force option listed in here. AWS support have advised that a 'dirty shutdown' is not possible. I am struggling with the same issue here. I also tried to add arbitrary sleeps between start and stop, tried with and without '-force' - it just shows 'Stopping' for 5-10 seconds and stops, without giving me a chance to input anything to terminal.Įdv4ld0, could you share more detail how you did that? Used the AWS CloudShell to minimize the lag.

And I'm doing that just a month later so I doubt AWS changed something. Unfortunately, I couldn't replicate this on my setup.

And idea presumably is to make the machine 'swallow' ACPI command sending that immediately after start. AWS first sends the ACPI shutdown, and in few minutes, if the instance is still up will cold-stop it. Aws ec2 start-instances -instance-ids i-?Īws ec2 stop-instances -force -instance-ids i-?

Routeros x86