Announcement

Collapse
No announcement yet.

LVE hanging

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

  • LVE hanging

    physical memory hanging on customers cpanel

  • #2
    Customers Physical Memory Usage is hanging. It have been for weeks now.
    We have tried killing the processes for the user and restarted lve without any luck at all.

    Any idea or command we can run to kill it or fix it?

    Comment


    • #3
      Do you mean that physical memory usage is there, even though there is no users processes?
      That is because of user caches (disk caches) are accounted as well. You really don want to purge it. System knows better when to purge it.
      It will not cause any issues for user, as it will get pushed out by users processes if he starts to run out of memory.

      Comment


      • #4
        Correct. Physical memory:
        Virtual Memory Usage16.2 / 7168 MB
        Physical Memory Usage1,833.7 / 5120 MB
        Entry Processes2 / 20

        It seems like there is always 1 process. Is there anyway to find what that process is and doing?

        Comment


        • #5
          Sure, just run:
          lveps -p

          It will show you processes per LVE.

          Comment


          • #6
            Igor, is there a doc that explains what the column headings are?

            I used lveps -h for help but it does not mention the abbreviations.

            - Scott

            Comment


            • #7
              Thanks.
              But didnt tell me much:
              username 2 2 --- 2 --- 56962 18 13907996 N/A
              --- --- lsphp --- 402087 0 5 N/A N/A
              --- --- lsphp --- 400278 1 7 N/A N/A

              So I shouldnt do anything about this?
              We had a similar problem last year, and if I dont remeber wrong you had to reinstall lve or something because it hanged like this...

              Comment


              • #8
                lsphp tends to keep processes alive so that it can quickly respond when request comes it. Seems normal -- I wouldn do anything.

                As long as they are not getting memory faults -- do nothing. This is their usage, so that their site would be fast.

                Comment

                Working...
                X