We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 1343 ☆ A M B ☆
    • 2,213 Posts
    The problems you are describing directly related to CloudLinux and it's impact on the hosting environment. What CloudLinux does is create a LVE which your site lives within - think VPS server. Your host can then set the resource limits for your account (typically your hosting plan), and when you hit those limits you are cut off.

    The logic behind systems such as CloudLinux is improving server stability allowing increased server density. If every site has limited resources they cannot exceed, it's easier to increase the number of accounts to a server. They also don't need to monitor the server for resource abuse as heavily, as you can no longer abuse the resources.

    My recommendation would be to decrease your php memory limit, if you allow it to use up to 256MB of ram and your account limit is 512MB for example, you can only have two PHP processes running at the same time. In theory your site could have three visitors, the first two would see the site and the third would get an internal server error. Decreasing the limit reduces the likelihood of that occurring, granted you might hit PHP errors due to insufficient memory in some cases.

    I would suggest setting the limit to 64MB and see if that helps the situation. I will also recommend sticking with MODX Evolution, as Revolution uses more memory and will have more problems.
      Patrick | Server Wrangler
      About Me: Website | Tweets |  MODX Hosting
      • 21417
      • 486 Posts
      Thanks for the info AMDbuilder - that was interesting to read.

      I will try reducing the memory limit when the issue happens again (the host recently reset the cloud linux so its not happening at the moment)

      Cheers.

      Evo all the way.
        Web design Adelaide
        http://gocreate.com.au