-
Notifications
You must be signed in to change notification settings - Fork 86
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SLUB: Unable to allocate memory on node -1 #774
Comments
ping @kolyshkin PTAL - could this be a bug in the Ubuntu kernel as well? |
We've encountered the same problem on Ubuntu 16.04.6 LTS:
|
Also having this issue with
on |
This seems to be related to kernel version 4.4.X, from what I've been able to google try upgrading the kernel, perhaps |
Have the similar issue
Hi, @Vesyrak We have the similar problem:
Above problem happens on the same server during past 3 months, we have to reboot the server then fix the file system to recover it. Attachd the dmesg log. Belowing is the setup info:
|
Expected behavior
K8s/Docker works without a hitch on Ubuntu 16.04.
Actual behavior
When dockers are running on the server, the following errors are generated by dmesg.
Eventually, the server crashes (after about 3-4 days since first docker boot) and the last thing that can be seen in the kern.log are the SLUB errors.
Related problems I found:
https://pingcap.com/blog/try-to-fix-two-linux-kernel-bugs-while-testing-tidb-operator-in-k8s/
opencontainers/runc#1725
kubernetes/kubernetes#61937 (comment)
However, these issues are related to CentOS and not Ubuntu.
Additionally, these issues claim tasks are blocked, which doesn't happen according to our dmesg.
Steps to reproduce the behavior
Deploy a Docker + K8s + Rancher setup
Output of
docker version
:Output of
docker info
:The servers are Dell Poweredges R430. One has been configured as a master, the other as a slave, both have the problem. These are new servers on which a clean 16.04 image was installed.
Any idea on what could be the cause would be greatly appreciated
The text was updated successfully, but these errors were encountered: