High RAM usage.

sammy95

New Member
May 8, 2024
4
1
3
Hi,
I have a node with Intel(R) Xeon(R) E-2274G CPU and 32GB RAM. I´m using Proxmox 8.2.2 and I have only 2 lxc , one is off.
I have high RAM usage , now at 22 out of 32 and its keep increasing daily till it will crash my system.
I don´t use ZFS and its a fresh install. Any suggestion ?

Screenshot 2024-05-08 132410.pngScreenshot 2024-05-08 132657.png
 
Last edited:
Hi,
Yes I have 2 HDD 12TB Raid1 made with mdadm.
I don´t see any process that is using so much ram.

Screenshot 2024-05-09 095948.png
 
This is the output of cat /proc/meminfo.

root@n3:~# cat /proc/meminfo
MemTotal: 32598704 kB
MemFree: 6692952 kB
MemAvailable: 14806536 kB
Buffers: 1968584 kB
Cached: 6474208 kB
SwapCached: 0 kB
Active: 2119448 kB
Inactive: 7680692 kB
Active(anon): 1531240 kB
Inactive(anon): 0 kB
Active(file): 588208 kB
Inactive(file): 7680692 kB
Unevictable: 148316 kB
Mlocked: 146440 kB
SwapTotal: 2097144 kB
SwapFree: 2097144 kB
Zswap: 0 kB
Zswapped: 0 kB
Dirty: 532 kB
Writeback: 0 kB
AnonPages: 1505732 kB
Mapped: 388724 kB
Shmem: 161916 kB
KReclaimable: 313464 kB
Slab: 436928 kB
SReclaimable: 313464 kB
SUnreclaim: 123464 kB
KernelStack: 7280 kB
PageTables: 19364 kB
SecPageTables: 0 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 18396496 kB
Committed_AS: 6709316 kB
VmallocTotal: 34359738367 kB
VmallocUsed: 94528 kB
VmallocChunk: 0 kB
Percpu: 8128 kB
HardwareCorrupted: 0 kB
AnonHugePages: 0 kB
ShmemHugePages: 0 kB
ShmemPmdMapped: 0 kB
FileHugePages: 0 kB
FilePmdMapped: 0 kB
Unaccepted: 0 kB
HugePages_Total: 0
HugePages_Free: 0
HugePages_Rsvd: 0
HugePages_Surp: 0
Hugepagesize: 2048 kB
Hugetlb: 0 kB
DirectMap4k: 218360 kB
DirectMap2M: 7899136 kB
DirectMap1G: 25165824 kB
 
This is the output of cat /proc/meminfo.

root@n3:~# cat /proc/meminfo
MemTotal: 32598704 kB
MemFree: 6692952 kB
MemAvailable: 14806536 kB
Buffers: 1968584 kB
Cached: 6474208 kB
SwapCached: 0 kB
Active: 2119448 kB
Inactive: 7680692 kB
Active(anon): 1531240 kB
Inactive(anon): 0 kB
Active(file): 588208 kB
Inactive(file): 7680692 kB
Unevictable: 148316 kB
Mlocked: 146440 kB
SwapTotal: 2097144 kB
SwapFree: 2097144 kB
Zswap: 0 kB
Zswapped: 0 kB
Dirty: 532 kB
Writeback: 0 kB
AnonPages: 1505732 kB
Mapped: 388724 kB
Shmem: 161916 kB
KReclaimable: 313464 kB
Slab: 436928 kB
SReclaimable: 313464 kB
SUnreclaim: 123464 kB
KernelStack: 7280 kB
PageTables: 19364 kB
SecPageTables: 0 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 18396496 kB
Committed_AS: 6709316 kB
VmallocTotal: 34359738367 kB
VmallocUsed: 94528 kB
VmallocChunk: 0 kB
Percpu: 8128 kB
HardwareCorrupted: 0 kB
AnonHugePages: 0 kB
ShmemHugePages: 0 kB
ShmemPmdMapped: 0 kB
FileHugePages: 0 kB
FilePmdMapped: 0 kB
Unaccepted: 0 kB
HugePages_Total: 0
HugePages_Free: 0
HugePages_Rsvd: 0
HugePages_Surp: 0
Hugepagesize: 2048 kB
Hugetlb: 0 kB
DirectMap4k: 218360 kB
DirectMap2M: 7899136 kB
DirectMap1G: 25165824 kB
Might be related to this https://forum.proxmox.com/threads/memory-leak-on-6-8-4-2-3-pve-8-2.146649/. Can you check if the issue is also present with the kernel v6.5?
 
You know, at this point I kind of think Proxmox should be releasing an official announcement that kernel 6.8 was released too early, and make the 6.5 the default kernel. I've never seen this many widespread reports of kernel issues without something official being done, it would make sense to walk it back to a more stable release.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!