We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 3749
    • 24,544 Posts
    Are you on a shared server? Possibly it’s overloaded.

    Check the server status in cPanel.

    It’s also possible that your site has been hacked and some inserted program is hogging the memory.

    512M should be more than enough (unless it’s 512K -- that would be a different story).

    Have you looked in PhpInfo() to see if you’re actually getting the 512M?
      Did I help you? Buy me a beer
      Get my Book: MODX:The Official Guide
      MODX info for everyone: http://bobsguides.com/modx.html
      My MODX Extras
      Bob's Guides is now hosted at A2 MODX Hosting
      • 1343 ☆ A M B ☆
      • 2,213 Posts
      Quote from: Billy_Koch at Sep 05, 2010, 09:44 PM

      Okay I am really really stumped.. I can install modx with no issues - but whenever I go into the manager and then lets say add a template then the server crashes on me. I just dont get it. It has NEVER done this before. So Im assuming that I need something bigger than the 512 MB site. I dont even run emails on this server since I use google apps. Any ideas what else I should look at?


      The default install still has email services running regardless if you have google apps. You can ask support to remove them and clamav from the server to free up memory.

      If you haven’t you may want to ask support to setup phpsuexec on the server, that should help prevent the server crashes.

      If you want I can discuss things with you more via chat some time, compare notes and see if we can’t figure out why you’re having issues.
        Patrick | Server Wrangler
        About Me: Website | Tweets |  MODX Hosting
        • 26903
        • 1,336 Posts
        You need a bit more info, firstly I would remove revo completely and measure your server under its normal pre-revo state, use sar, free, top or any other tools to do this. Install revo, don’t login or enter the manager, take the same measurements as above, login, take the same measurements again, then do whatever it is you do to cause the crash condition, whist top or sar is running in a terminal. If it fails see what these told you last.

        The oom killer logs are a bit late, especially if they give you only a portion of it, you should have a single entry at the top that says why the oom killer was triggered and what it killed first, also you need the output of dmesg, tail this whilst you are performing your tests.

        Also look at your swap space, if run out of this you will eventually kill your machine.
          Use MODx, or the cat gets it!
          • 6955 ☆ A M B ☆
          • 147 Posts
          Disabled SpamAssassin and ClamAV that freed up 200 MB - so now it seems to be running pretty smooth. No crashes yet tonight. Activating some other sites on the server and see see. I would have thought that a 512 MB server could handle at least 10-15 sites (not heavily active). Im just happy to get it up and running now.

            Billy Koch
            Follow me on Twitter: @DefKoch
            Skype: billyk0ch