search

vatertime / minecraft-spot-pricing

Cloudformation template to deploy a Minecraft server
MIT License
140 stars 84 forks source link

Changing from Running to Stopped erased my world #9

Closed taylorvance closed 3 years ago

taylorvance commented 3 years ago

I updated the CF stack from Running to Stopped to shut down the server for the night. When I changed it back to Running, after connecting to the new EC2 instance, it seemed like a brand new world (with the same seed I'd provided). I had nothing in my inventory, and blocks that I had moved were back to where they were originally.

The EFS resource seems to have been maintained (its creation date shows "yesterday"), but the world was not.

Any ideas?

vatertime commented 3 years ago

Check EFS via the AWS Console and see if there is a listing? Should look like this: image

Not sure if your EFS was created successfully or if it didn't get properly attached to the EC2 instances. Could also check if there were any errors during creation via the Cloudformation > [minecraft-stack] > Events page.

Might have to delete the whole stack and recreate it.

taylorvance commented 3 years ago

No CF errors. The EFS is mounted on /opt/minecraft according to df -hT on the ec2 cmd line. I guess I'll try recreating.

vatertime commented 3 years ago

Smart - and if the folder/file structure is there I'm not sure what went awry. Poke around in the Docker logs? At any rate, LMK what happens after the proverbial 'turn it off/turn it on'.

taylorvance commented 3 years ago

That worked. SMH