Unable to stop GCP VM instance, automatically starts
I've recently taken over a GCP project, created snapshots to restore in case of mistakes, and now I need to restore one of them.
Part of the process includes stopping the currently-running VM instance.
Whenever I do this, the instance automatically starts back up immediately. In the notifications panel, there is only "Stop VM instance "...."", with no errors or the re-starting reported.
I know this doesn't happen with regular VMs, so the previous owner must have done something to automatically start it back up if it goes down.
Does anyone know where I should go looking to safely disable that feature for a while? Or if there's a way to force it to stop for a bit longer?
google-cloud-platform virtual-machine google-compute-engine
edited Nov 23 '18 at 8:29
Maxim
1,498210
asked Nov 22 '18 at 23:39
Larry CaiLarry Cai
438
add a comment |
I've recently taken over a GCP project, created snapshots to restore in case of mistakes, and now I need to restore one of them.
Part of the process includes stopping the currently-running VM instance.
Whenever I do this, the instance automatically starts back up immediately. In the notifications panel, there is only "Stop VM instance "...."", with no errors or the re-starting reported.
I know this doesn't happen with regular VMs, so the previous owner must have done something to automatically start it back up if it goes down.
Does anyone know where I should go looking to safely disable that feature for a while? Or if there's a way to force it to stop for a bit longer?
google-cloud-platform virtual-machine google-compute-engine
edited Nov 23 '18 at 8:29
Maxim
1,498210
asked Nov 22 '18 at 23:39
Larry CaiLarry Cai
438
1
Beware that the instance is not necessarily starting back up immediately. Rather, it may be that a new instance is being created.
– jhfrontz
Jan 16 at 23:47
add a comment |
I've recently taken over a GCP project, created snapshots to restore in case of mistakes, and now I need to restore one of them.
Part of the process includes stopping the currently-running VM instance.
Whenever I do this, the instance automatically starts back up immediately. In the notifications panel, there is only "Stop VM instance "...."", with no errors or the re-starting reported.
I know this doesn't happen with regular VMs, so the previous owner must have done something to automatically start it back up if it goes down.
Does anyone know where I should go looking to safely disable that feature for a while? Or if there's a way to force it to stop for a bit longer?
google-cloud-platform virtual-machine google-compute-engine
edited Nov 23 '18 at 8:29
Maxim
1,498210
asked Nov 22 '18 at 23:39
Larry CaiLarry Cai
438
I've recently taken over a GCP project, created snapshots to restore in case of mistakes, and now I need to restore one of them.
Part of the process includes stopping the currently-running VM instance.
Whenever I do this, the instance automatically starts back up immediately. In the notifications panel, there is only "Stop VM instance "...."", with no errors or the re-starting reported.
I know this doesn't happen with regular VMs, so the previous owner must have done something to automatically start it back up if it goes down.
Does anyone know where I should go looking to safely disable that feature for a while? Or if there's a way to force it to stop for a bit longer?
google-cloud-platform virtual-machine google-compute-engine
google-cloud-platform virtual-machine google-compute-engine
edited Nov 23 '18 at 8:29
Maxim
1,498210
asked Nov 22 '18 at 23:39
Larry CaiLarry Cai
438
edited Nov 23 '18 at 8:29
Maxim
1,498210
asked Nov 22 '18 at 23:39
Larry CaiLarry Cai
438
edited Nov 23 '18 at 8:29
Maxim
1,498210
edited Nov 23 '18 at 8:29
Maxim
1,498210
edited Nov 23 '18 at 8:29
Maxim
1,498210
1,498210
asked Nov 22 '18 at 23:39
Larry CaiLarry Cai
438
asked Nov 22 '18 at 23:39
Larry CaiLarry Cai
438
asked Nov 22 '18 at 23:39
Larry CaiLarry Cai
438
438
1
Beware that the instance is not necessarily starting back up immediately. Rather, it may be that a new instance is being created.
– jhfrontz
Jan 16 at 23:47
add a comment |
1
Beware that the instance is not necessarily starting back up immediately. Rather, it may be that a new instance is being created.
– jhfrontz
Jan 16 at 23:47
1
1
Beware that the instance is not necessarily starting back up immediately. Rather, it may be that a new instance is being created.
– jhfrontz
Jan 16 at 23:47
Beware that the instance is not necessarily starting back up immediately. Rather, it may be that a new instance is being created.
– jhfrontz
Jan 16 at 23:47
add a comment |
1 Answer
1
active
oldest
votes
Your instance is probably being managed. Go to the Google Cloud Console:
Go to Compute Engine -> Instance Groups. Is this instance listed here?
Go to Kubernetes Engine. Do you have a cluster running? Is this instance part of a cluster?
Go to Cloud Functions. Look at each function. Are any of the functions watching or monitoring VM instances?
Go to Load Balancers -> Backend instances. Check here also.
If your instance is part of an Instance Group, Kubernetes cluster, load balancer back-end, etc. than you do not manage the instance yourself. It is being managed for you. If you shutdown or delete an instance it will be recreated (depending on configuration).
For most of these types of services, the VM instances are stateless, which means that they are recreated from an image, container, etc. Creating snapshots won't help you in this case. Figure out first how your systems are configured before trying to manage them.
answered Nov 23 '18 at 0:53
John HanleyJohn Hanley
15.6k2629
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53439128%2funable-to-stop-gcp-vm-instance-automatically-starts%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Your instance is probably being managed. Go to the Google Cloud Console:
Go to Compute Engine -> Instance Groups. Is this instance listed here?
Go to Kubernetes Engine. Do you have a cluster running? Is this instance part of a cluster?
Go to Cloud Functions. Look at each function. Are any of the functions watching or monitoring VM instances?
Go to Load Balancers -> Backend instances. Check here also.
If your instance is part of an Instance Group, Kubernetes cluster, load balancer back-end, etc. than you do not manage the instance yourself. It is being managed for you. If you shutdown or delete an instance it will be recreated (depending on configuration).
For most of these types of services, the VM instances are stateless, which means that they are recreated from an image, container, etc. Creating snapshots won't help you in this case. Figure out first how your systems are configured before trying to manage them.
answered Nov 23 '18 at 0:53
John HanleyJohn Hanley
15.6k2629
add a comment |
Your instance is probably being managed. Go to the Google Cloud Console:
Go to Compute Engine -> Instance Groups. Is this instance listed here?
Go to Kubernetes Engine. Do you have a cluster running? Is this instance part of a cluster?
Go to Cloud Functions. Look at each function. Are any of the functions watching or monitoring VM instances?
Go to Load Balancers -> Backend instances. Check here also.
If your instance is part of an Instance Group, Kubernetes cluster, load balancer back-end, etc. than you do not manage the instance yourself. It is being managed for you. If you shutdown or delete an instance it will be recreated (depending on configuration).
For most of these types of services, the VM instances are stateless, which means that they are recreated from an image, container, etc. Creating snapshots won't help you in this case. Figure out first how your systems are configured before trying to manage them.
answered Nov 23 '18 at 0:53
John HanleyJohn Hanley
15.6k2629
add a comment |
Your instance is probably being managed. Go to the Google Cloud Console:
Go to Compute Engine -> Instance Groups. Is this instance listed here?
Go to Kubernetes Engine. Do you have a cluster running? Is this instance part of a cluster?
Go to Cloud Functions. Look at each function. Are any of the functions watching or monitoring VM instances?
Go to Load Balancers -> Backend instances. Check here also.
If your instance is part of an Instance Group, Kubernetes cluster, load balancer back-end, etc. than you do not manage the instance yourself. It is being managed for you. If you shutdown or delete an instance it will be recreated (depending on configuration).
For most of these types of services, the VM instances are stateless, which means that they are recreated from an image, container, etc. Creating snapshots won't help you in this case. Figure out first how your systems are configured before trying to manage them.
answered Nov 23 '18 at 0:53
John HanleyJohn Hanley
15.6k2629
Your instance is probably being managed. Go to the Google Cloud Console:
Go to Compute Engine -> Instance Groups. Is this instance listed here?
Go to Kubernetes Engine. Do you have a cluster running? Is this instance part of a cluster?
Go to Cloud Functions. Look at each function. Are any of the functions watching or monitoring VM instances?
Go to Load Balancers -> Backend instances. Check here also.
If your instance is part of an Instance Group, Kubernetes cluster, load balancer back-end, etc. than you do not manage the instance yourself. It is being managed for you. If you shutdown or delete an instance it will be recreated (depending on configuration).
For most of these types of services, the VM instances are stateless, which means that they are recreated from an image, container, etc. Creating snapshots won't help you in this case. Figure out first how your systems are configured before trying to manage them.
answered Nov 23 '18 at 0:53
John HanleyJohn Hanley
15.6k2629
answered Nov 23 '18 at 0:53
John HanleyJohn Hanley
15.6k2629
answered Nov 23 '18 at 0:53
John HanleyJohn Hanley
15.6k2629
answered Nov 23 '18 at 0:53
John HanleyJohn Hanley
15.6k2629
15.6k2629
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53439128%2funable-to-stop-gcp-vm-instance-automatically-starts%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
Beware that the instance is not necessarily starting back up immediately. Rather, it may be that a new instance is being created.
– jhfrontz
Jan 16 at 23:47