Azure VM stops/deallocates at random times. Any ideas?
I have a Linux VM running on Azure. It's funded via a MSDN account, though I don't think that is relevant to my question.
Since creating it ~1 week ago, I've had four separate times where I've found it's state is suddenly "Stopped - Deallocating". If I look in resource health, I see:
"This virtual machine is stopping and deallocating as requested by an authorized user or process"
This is not true. I am the only person with access to my account, and I have no automation or anything like that which might cause a command to be sent.
I'm a bit baffled. If I look inside the VM, all I see in the log entry in syslog that looks like this:
Jan 14 11:02:08 HOSTNAME kernel: [81679.063027] hv_utils: Shutdown request received - graceful shutdown initiated
Any ideas what could be triggering this? My intent is to have the VM up 24x7. If I go into the portal and click Start, it fires right up and works great, but obviously this isn't what I was hoping for.
Thanks!
azure
asked Jan 14 at 20:59
raindog308raindog308
1581310
add a comment |
I have a Linux VM running on Azure. It's funded via a MSDN account, though I don't think that is relevant to my question.
Since creating it ~1 week ago, I've had four separate times where I've found it's state is suddenly "Stopped - Deallocating". If I look in resource health, I see:
"This virtual machine is stopping and deallocating as requested by an authorized user or process"
This is not true. I am the only person with access to my account, and I have no automation or anything like that which might cause a command to be sent.
I'm a bit baffled. If I look inside the VM, all I see in the log entry in syslog that looks like this:
Jan 14 11:02:08 HOSTNAME kernel: [81679.063027] hv_utils: Shutdown request received - graceful shutdown initiated
Any ideas what could be triggering this? My intent is to have the VM up 24x7. If I go into the portal and click Start, it fires right up and works great, but obviously this isn't what I was hoping for.
Thanks!
azure
asked Jan 14 at 20:59
raindog308raindog308
1581310
Googlinghv_utils: Shutdown request receivedgives many social.msdn.microsoft.com results of people with similar problems. It seems that the VMs can be reboot for a multitude of reasons, and some may be out of your control. One way to avoid this is configuring them for high availability.
– MC10
Jan 14 at 21:32
4 times has become 12 in ~10 days. I can't imagine Azure is engineered for this. Additionally, in the last two years, I've experienced 1 reboot across six other VMs, so I'm thinking that 12 in 10 days for one indicates an issue. I will try to redeploy.
– raindog308
Jan 16 at 21:12
Redeploy made no difference, and I've had another 48 (wow!) stop/alloc in the last 10 days. Microsoft is clueless so I think it's time to just find another platform. Azure may be ready for prime time, but neither its interface nor its support is because neither can diagnose this elementary issue. Alternatively, dozens of failures a week is normal performance.
– raindog308
Jan 26 at 19:57
1
And just to wrap up, I did finally locate the issue - I think. There is an auto shutdown option in Azure (amazing, MSFT support knew nothing about it, even though it's in the panel). It's designed to shut down VMs at a particular time (e.g., 1700 UTC every day or something), but apparently it malfunctions as I saw many shutdowns per day. Turning it off has, over the last 24 hours, resolved the issue. If you search in the (current, Jan 2019 version of the) Azure panel for auto shutdown, you'll find the option.
– raindog308
Jan 27 at 15:44
add a comment |
I have a Linux VM running on Azure. It's funded via a MSDN account, though I don't think that is relevant to my question.
Since creating it ~1 week ago, I've had four separate times where I've found it's state is suddenly "Stopped - Deallocating". If I look in resource health, I see:
"This virtual machine is stopping and deallocating as requested by an authorized user or process"
This is not true. I am the only person with access to my account, and I have no automation or anything like that which might cause a command to be sent.
I'm a bit baffled. If I look inside the VM, all I see in the log entry in syslog that looks like this:
Jan 14 11:02:08 HOSTNAME kernel: [81679.063027] hv_utils: Shutdown request received - graceful shutdown initiated
Any ideas what could be triggering this? My intent is to have the VM up 24x7. If I go into the portal and click Start, it fires right up and works great, but obviously this isn't what I was hoping for.
Thanks!
azure
asked Jan 14 at 20:59
raindog308raindog308
1581310
I have a Linux VM running on Azure. It's funded via a MSDN account, though I don't think that is relevant to my question.
Since creating it ~1 week ago, I've had four separate times where I've found it's state is suddenly "Stopped - Deallocating". If I look in resource health, I see:
"This virtual machine is stopping and deallocating as requested by an authorized user or process"
This is not true. I am the only person with access to my account, and I have no automation or anything like that which might cause a command to be sent.
I'm a bit baffled. If I look inside the VM, all I see in the log entry in syslog that looks like this:
Jan 14 11:02:08 HOSTNAME kernel: [81679.063027] hv_utils: Shutdown request received - graceful shutdown initiated
Any ideas what could be triggering this? My intent is to have the VM up 24x7. If I go into the portal and click Start, it fires right up and works great, but obviously this isn't what I was hoping for.
Thanks!
azure
azure
asked Jan 14 at 20:59
raindog308raindog308
1581310
asked Jan 14 at 20:59
raindog308raindog308
1581310
asked Jan 14 at 20:59
raindog308raindog308
1581310
asked Jan 14 at 20:59
raindog308raindog308
1581310
asked Jan 14 at 20:59
raindog308raindog308
1581310
1581310
Googlinghv_utils: Shutdown request receivedgives many social.msdn.microsoft.com results of people with similar problems. It seems that the VMs can be reboot for a multitude of reasons, and some may be out of your control. One way to avoid this is configuring them for high availability.
– MC10
Jan 14 at 21:32
4 times has become 12 in ~10 days. I can't imagine Azure is engineered for this. Additionally, in the last two years, I've experienced 1 reboot across six other VMs, so I'm thinking that 12 in 10 days for one indicates an issue. I will try to redeploy.
– raindog308
Jan 16 at 21:12
Redeploy made no difference, and I've had another 48 (wow!) stop/alloc in the last 10 days. Microsoft is clueless so I think it's time to just find another platform. Azure may be ready for prime time, but neither its interface nor its support is because neither can diagnose this elementary issue. Alternatively, dozens of failures a week is normal performance.
– raindog308
Jan 26 at 19:57
1
And just to wrap up, I did finally locate the issue - I think. There is an auto shutdown option in Azure (amazing, MSFT support knew nothing about it, even though it's in the panel). It's designed to shut down VMs at a particular time (e.g., 1700 UTC every day or something), but apparently it malfunctions as I saw many shutdowns per day. Turning it off has, over the last 24 hours, resolved the issue. If you search in the (current, Jan 2019 version of the) Azure panel for auto shutdown, you'll find the option.
– raindog308
Jan 27 at 15:44
add a comment |
Googlinghv_utils: Shutdown request receivedgives many social.msdn.microsoft.com results of people with similar problems. It seems that the VMs can be reboot for a multitude of reasons, and some may be out of your control. One way to avoid this is configuring them for high availability.
– MC10
Jan 14 at 21:32
4 times has become 12 in ~10 days. I can't imagine Azure is engineered for this. Additionally, in the last two years, I've experienced 1 reboot across six other VMs, so I'm thinking that 12 in 10 days for one indicates an issue. I will try to redeploy.
– raindog308
Jan 16 at 21:12
Redeploy made no difference, and I've had another 48 (wow!) stop/alloc in the last 10 days. Microsoft is clueless so I think it's time to just find another platform. Azure may be ready for prime time, but neither its interface nor its support is because neither can diagnose this elementary issue. Alternatively, dozens of failures a week is normal performance.
– raindog308
Jan 26 at 19:57
1
And just to wrap up, I did finally locate the issue - I think. There is an auto shutdown option in Azure (amazing, MSFT support knew nothing about it, even though it's in the panel). It's designed to shut down VMs at a particular time (e.g., 1700 UTC every day or something), but apparently it malfunctions as I saw many shutdowns per day. Turning it off has, over the last 24 hours, resolved the issue. If you search in the (current, Jan 2019 version of the) Azure panel for auto shutdown, you'll find the option.
– raindog308
Jan 27 at 15:44
Googling
hv_utils: Shutdown request received gives many social.msdn.microsoft.com results of people with similar problems. It seems that the VMs can be reboot for a multitude of reasons, and some may be out of your control. One way to avoid this is configuring them for high availability.– MC10
Jan 14 at 21:32
Googling
hv_utils: Shutdown request received gives many social.msdn.microsoft.com results of people with similar problems. It seems that the VMs can be reboot for a multitude of reasons, and some may be out of your control. One way to avoid this is configuring them for high availability.– MC10
Jan 14 at 21:32
4 times has become 12 in ~10 days. I can't imagine Azure is engineered for this. Additionally, in the last two years, I've experienced 1 reboot across six other VMs, so I'm thinking that 12 in 10 days for one indicates an issue. I will try to redeploy.
– raindog308
Jan 16 at 21:12
4 times has become 12 in ~10 days. I can't imagine Azure is engineered for this. Additionally, in the last two years, I've experienced 1 reboot across six other VMs, so I'm thinking that 12 in 10 days for one indicates an issue. I will try to redeploy.
– raindog308
Jan 16 at 21:12
Redeploy made no difference, and I've had another 48 (wow!) stop/alloc in the last 10 days. Microsoft is clueless so I think it's time to just find another platform. Azure may be ready for prime time, but neither its interface nor its support is because neither can diagnose this elementary issue. Alternatively, dozens of failures a week is normal performance.
– raindog308
Jan 26 at 19:57
Redeploy made no difference, and I've had another 48 (wow!) stop/alloc in the last 10 days. Microsoft is clueless so I think it's time to just find another platform. Azure may be ready for prime time, but neither its interface nor its support is because neither can diagnose this elementary issue. Alternatively, dozens of failures a week is normal performance.
– raindog308
Jan 26 at 19:57
1
1
And just to wrap up, I did finally locate the issue - I think. There is an auto shutdown option in Azure (amazing, MSFT support knew nothing about it, even though it's in the panel). It's designed to shut down VMs at a particular time (e.g., 1700 UTC every day or something), but apparently it malfunctions as I saw many shutdowns per day. Turning it off has, over the last 24 hours, resolved the issue. If you search in the (current, Jan 2019 version of the) Azure panel for auto shutdown, you'll find the option.
– raindog308
Jan 27 at 15:44
And just to wrap up, I did finally locate the issue - I think. There is an auto shutdown option in Azure (amazing, MSFT support knew nothing about it, even though it's in the panel). It's designed to shut down VMs at a particular time (e.g., 1700 UTC every day or something), but apparently it malfunctions as I saw many shutdowns per day. Turning it off has, over the last 24 hours, resolved the issue. If you search in the (current, Jan 2019 version of the) Azure panel for auto shutdown, you'll find the option.
– raindog308
Jan 27 at 15:44
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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%2fsuperuser.com%2fquestions%2f1394259%2fazure-vm-stops-deallocates-at-random-times-any-ideas%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Super User!
- 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%2fsuperuser.com%2fquestions%2f1394259%2fazure-vm-stops-deallocates-at-random-times-any-ideas%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
Googling
hv_utils: Shutdown request receivedgives many social.msdn.microsoft.com results of people with similar problems. It seems that the VMs can be reboot for a multitude of reasons, and some may be out of your control. One way to avoid this is configuring them for high availability.– MC10
Jan 14 at 21:32
4 times has become 12 in ~10 days. I can't imagine Azure is engineered for this. Additionally, in the last two years, I've experienced 1 reboot across six other VMs, so I'm thinking that 12 in 10 days for one indicates an issue. I will try to redeploy.
– raindog308
Jan 16 at 21:12
Redeploy made no difference, and I've had another 48 (wow!) stop/alloc in the last 10 days. Microsoft is clueless so I think it's time to just find another platform. Azure may be ready for prime time, but neither its interface nor its support is because neither can diagnose this elementary issue. Alternatively, dozens of failures a week is normal performance.
– raindog308
Jan 26 at 19:57
1
And just to wrap up, I did finally locate the issue - I think. There is an auto shutdown option in Azure (amazing, MSFT support knew nothing about it, even though it's in the panel). It's designed to shut down VMs at a particular time (e.g., 1700 UTC every day or something), but apparently it malfunctions as I saw many shutdowns per day. Turning it off has, over the last 24 hours, resolved the issue. If you search in the (current, Jan 2019 version of the) Azure panel for auto shutdown, you'll find the option.
– raindog308
Jan 27 at 15:44