Skip to content
This repository has been archived by the owner on Nov 3, 2021. It is now read-only.

ghe-backup-volume could not be mounted again after a failure/termination or stop #75

Closed
rashamalek opened this issue Aug 11, 2017 · 1 comment
Closed

ghe-backup-volume could not be mounted again after a failure/termination or stop #75

rashamalek opened this issue Aug 11, 2017 · 1 comment

Comments

@rashamalek
Copy link
Contributor

If ec2 instance is stopped or terminates, autoscalinggroup spins up a new instance, but
ghe-backup-volume will not be mounted, and taupage scripts fail.
@rashamalek rashamalek changed the title ghe-backup-volume could not be mounted again ghe-backup-volume could not be mounted again after a failure/termination or stop Aug 11, 2017
@lotharschulz
Copy link
Contributor

Turned out taupage volume scanning needs more memory than t2.small provides. Upgrading to t2.medium solved the issue.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@lotharschulz @rashamalek