Skip to main content

Fresh server start after instance degraded

So the issue was, amazon issued an warning regarding the server to be terminated, before i could think of making an backup the instance stopped.

The troubleshoot operations like reboot, stop and start didn't worked.
Simple Steps to start a fresh instance with the previous content on server.


Firstly create a fresh instance with the required environment or use the ami of the instance if present.
Keep all your content in ebs volumes, this will make sure you never lose data.

you can create a snapshot of the instance and keep it for future use.
Also ami's can be created to launch the instance directly.

Micro instances can go down at any point and even amazon cannot gaurantee. When they get cpu spike of around 100% 2-3 times, possibility is it will stop responding.Right click on the instance on aws console and check the logs to get a better idea of the commands being executed.

There is also a option which says launch more like this but that will launch the instance with the prev data and not the current instance .

Note: This post will be updated soon with a better tutorial and data.

Comments

Popular posts from this blog

Cannot allocate memory error while computing files - Setup Swap space

ActionView::Template::Error (Cannot allocate memory - nodejs /tmp/execjs20131021-26716-fckzo3.js 2>&1
Nodejs is used to compile javascript at runtime. In RoR applications, this error comes when server is started in production mode which compiles the assets or while running rake assets:precompile.
check for swap space and allocate