[SOLVED] Bad htop memory display with LXC

Discussion in 'Proxmox VE: Installation and configuration' started by BoringASK, Aug 9, 2018.

  1. BoringASK

    BoringASK New Member

    Joined:
    Aug 9, 2018
    Messages:
    12
    Likes Received:
    0
    Hello all,

    I have a problem with my LXC platform, indeed the RAM displayed in htop is incorrect: obviously it seems to include memory and shared memory.

    For example, a memory consumption of 4.75G/4G is displayed.

    Proxmox Version : 5.2-1
    Lxcfs : 3.0.0

    Obviously it's a known bug but obviously not fixed.
     
  2. eider

    eider New Member

    Joined:
    Aug 9, 2018
    Messages:
    1
    Likes Received:
    0
    This has been already fixed in upstream month ago in this commit dd43c518918cce7f347d78214052b229b4a72f3f however there was no release of lxcfs since then. Proxmox Team may consider manually applying this patch to current version.
     
  3. BoringASK

    BoringASK New Member

    Joined:
    Aug 9, 2018
    Messages:
    12
    Likes Received:
    0
    Can you send me the commit link ? I can't find him.
     
  4. Ali Zowghi

    Ali Zowghi New Member

    Joined:
    May 1, 2018
    Messages:
    2
    Likes Received:
    0
    Hi
    /github.com/lxc/lxcfs/commit/dd43c518918cce7f347d78214052b229b4a72f3f
     
  5. BoringASK

    BoringASK New Member

    Joined:
    Aug 9, 2018
    Messages:
    12
    Likes Received:
    0
    Yes it's work.

    Thanks !
     
  6. hazertyck

    hazertyck New Member

    Joined:
    Aug 20, 2018
    Messages:
    1
    Likes Received:
    0
    Obviously I have the same problem. I do not understand how you solved it from this commit. What exactly did you do?
    Should we clone the entire Git repo and recompile lxcfs entirely?

    I'm using proxmox for production, I'm not comfortable with the idea of using tools that I will not find in official proxmox / debian updates
     
  7. Ali Zowghi

    Ali Zowghi New Member

    Joined:
    May 1, 2018
    Messages:
    2
    Likes Received:
    0
    Hi
    In the last update the problem is solved ...
     
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice