Announcement

Collapse
No announcement yet.

LVE limits and CageFS

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • LVE limits and CageFS

    Whether CageFS is reuired for activationg LVE limits

  • #2
    Hello,

    Here is situation. We have users on CloudLinux+cPanel 11.52 server - shared server.
    All users have some certain CloudLinux hosting limits, i.e. vMem, pMem, EP, IO
    When users were out of CageFS - there are no problem - all sites running okay.
    But, once CageFS is enabled - things go worse - sites are down 2/3 of time and very slow.
    So we have a question:

    Could it be that CloudLinux limits are too low and when accounts not in CageFS - lve limits not applied?
    And, once an account is put in cagefs (cagefsctl --disable $USERNAME) - lve limits are enabled for the $USERNAME thus the slowness (because of too low limits).

    For example, with cagefs enabled for user accounts shows 500 (memory problems) and once cagefs disabled - the 500 error is gone and vice-versa.

    The point is that our customer has set LVE limits per his own consideration (for instance 256 MB limit for vMem in a package) and says, that he had such limits for years without any problems. And this could be true, because he did not have CageFS enabled for all users on a shared server.
    But, once CageFS enabled - problems begins...

    Would you please clarify whether CageFS should be enabled to have LVE limits active or this is some kind of bug/feature?

    Thank you.

    Comment


    • #3
      Hello,

      LVE limits are working with and without CageFS, no matter if it is enabled or disabled. You could check lvetop with disabled CageFS to see some processes are inside LVE.

      Well, just enabling cagefs should not cause increased resource usage. The only one reason when it could do it - if problematic customer use alternate PHP version. If so it could start loading different php modules and could require more memory. However 256Mb vmem is to low, our default value is 1Gb. However the best practice is to set vmem unlimited and start using pmem (where 256Mb could be Ok as a starting point).

      Comment

      Working...
      X