settings in LVE manager no longer work

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • support
    Junior Member
    Forum Explorer
    • Mar 2021
    • 12

    #1

    settings in LVE manager no longer work

    2.6.18-408.el5.lve1.1.63
  • accounts
    Member
    • Apr 2017
    • 70

    #2
    Running CL 5 with 2.6.18-408.el5.lve1.1.63
    Have noticed that in WHM LVE manager we can no longer make changes to individual LVs. Any changes aren saved and revert to default values. Now, were wondering that because were now using 2.6.18-408.el5.lve1.1.63 we should install the new Beta LVE Manager ? http://www.cloudlinux.com/blog/clnew...its-for-pa.php

    Comment

    • iseletsk
      Senior Member
      • Dec 2017
      • 1199

      #3
      Are you using new lve-utils/lvemanager, or the old one?
      It should work, even with the old one

      Comment

      • accounts
        Member
        • Apr 2017
        • 70

        #4
        Were currently using lve-utils-1.0-12.el5
        Changes to either MEM or Concurrent Connections in any LVE remain the default that we set some months ago.

        Comment

        • azharimad
          Junior Member
          • Mar 2021
          • 4

          #5
          I face same problem
          It didn work with old one, i had to install new lvemanager and run

          #service httpd stop
          #lvectl destroy all
          #service lve restart
          #service httpd start

          Comment

          • accounts
            Member
            • Apr 2017
            • 70

            #6
            Thanks harry a, The new lvemanager works
            Did you create a setting for the # of processes or leave it set to 0 ?

            Comment

            • azharimad
              Junior Member
              • Mar 2021
              • 4

              #7
              @kernow
              Yes i leave it to zero because afaik it not implemented yet.

              Comment

              • iseletsk
                Senior Member
                • Dec 2017
                • 1199

                #8
                New version should fix the issue with old LVE manager

                Comment

                Working...