Trending on MSDN: Kernel Panic - Not Syncing: Out of Memory and no Killable Processes

Micah McKittrick 946 Reputation points Microsoft Employee
2019-10-29T19:58:09.26+00:00

I have a recently created VM. It's an Ubuntu VM, and I've not done anything to it besides installing Docker.

I'm running two Docker containers:

  1. Portainer
  2. A small dotnet core application

After setting this up, I had a look in HTOP to see the memory and CPU usage, and I found they were both low.

Today I could not reach the VM over SSH, so I looked at the log under the "Serial console" tab in Azure Portal. I can see that it for some reason it ran out of memory and started killing off all the processes, until it finally says, "Kernel panic - not syncing: Out of memory and no killable processes".

Any ideas what this might be?

Sourced from MSDN

Azure Virtual Machines
Azure Virtual Machines
An Azure service that is used to provision Windows and Linux virtual machines.
7,370 questions
0 comments No comments
{count} votes

Accepted answer
  1. olufemia-MSFT 2,861 Reputation points
    2019-10-29T20:29:44.73+00:00

    Welcome to the Microsoft Q&A (Preview) platform. Happy to answer your question.

    Usually to fix a kernel panic error you can simply restart the VM. One common reason for kernel panic in Azure VMs can be host updates.

    However it is difficult to say if that is the root cause for your specific issue.

    Your VM might have encountered a memory preserving update on the Azure backend and it resulted in this.

    I would suggest you restart the VM to check that the error goes away. If the issue does not come back, we can be certain it was an issue related to something on the Azure backend such as a host update.

    If the issue continues to persist after a restart it would warrant further investigation.

    Sourced from MSDN

    0 comments No comments

2 additional answers

Sort by: Most helpful
  1. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  2. third one 1 Reputation point
    2023-01-22T09:21:56.91+00:00

    Today I was unable to arrive at the VM over SSH, so I took a gander at the log under the "Sequential control center" tab in Purplish blue Entry. I can see that it for reasons unknown it ran out of memory and gotten killing going every one of the cycles, until it at last says, "Bit alarm - not matching up: Out of memory and no killable cycles".

    0 comments No comments