Skip to content
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 #82534

Open
ThomasCassimon opened this issue Sep 10, 2019 · 0 comments

Comments

@ThomasCassimon
Copy link

commented Sep 10, 2019

What happened:
When dockers are running on the server, the following errors are generated by dmesg.

[319003.331580] SLUB: Unable to allocate memory on node -1 (gfp=0x2088020)
[319003.331587]   cache: mnt_cache(9946:ea4c61d01895b46bf04a9b8c54602a4a6fff12ca7341b3b21f879414c120da79), object size: 384, buffer size: 384, default order: 2, min order: 0
[319003.331591]   node 0: slabs: 20, objs: 776, free: 0
[319003.331594]   node 1: slabs: 14, objs: 556, free: 0
[319940.222707] SLUB: Unable to allocate memory on node -1 (gfp=0x2088020)
[319940.222714]   cache: blkdev_ioc(9946:ea4c61d01895b46bf04a9b8c54602a4a6fff12ca7341b3b21f879414c120da79), object size: 104, buffer size: 104, default order: 0, min order: 0
[319940.222718]   node 0: slabs: 2, objs: 78, free: 0
[319940.222721]   node 1: slabs: 4, objs: 156, free: 0
[320001.028578] SLUB: Unable to allocate memory on node -1 (gfp=0x2080020)
[320001.028582]   cache: kmalloc-128(9946:ea4c61d01895b46bf04a9b8c54602a4a6fff12ca7341b3b21f879414c120da79), object size: 128, buffer size: 128, default order: 1, min order: 0
[320001.028585]   node 0: slabs: 19, objs: 1216, free: 0
[320001.028587]   node 1: slabs: 18, objs: 1152, free: 0
[320004.629230] SLUB: Unable to allocate memory on node -1 (gfp=0x2088020)
[320004.629236]   cache: mnt_cache(9946:ea4c61d01895b46bf04a9b8c54602a4a6fff12ca7341b3b21f879414c120da79), object size: 384, buffer size: 384, default order: 2, min order: 0
[320004.629239]   node 0: slabs: 24, objs: 912, free: 0
[320004.629241]   node 1: slabs: 18, objs: 692, free: 0

What you expected to happen:
K8s/Docker works without a hitch on Ubuntu 16.04.

How to reproduce it (as minimally and precisely as possible):
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.

Anything else we need to know?:
Related problems I found:
https://pingcap.com/blog/try-to-fix-two-linux-kernel-bugs-while-testing-tidb-operator-in-k8s/
opencontainers/runc#1725
#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.

We also filed a bug report(s) with Docker:
docker/for-linux#774
docker/distribution#3005

Environment:

  • Kubernetes version (use kubectl version): 1.14.6
  • Cloud provider or hardware configuration: Rancher 2.2.7 on Dell PowerEdge 430
  • OS (e.g: cat /etc/os-release): Ubuntu 16.04.6 LTS (Xenial Xerus)
  • Kernel (e.g. uname -a): 4.4.0-142-generic
  • Install tools: Rancher 2.2.7
  • Network plugin and version (if this is a network-related bug):
  • Others: /

/sig cluster-lifecycle

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.