We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 31559
    • 20 Posts
    Could really use some help on this one. For some reason my DB has grown to a whopping 580MB......is this normal? There really isn’t that much to the site so I’m not understanding how it has managed to get so large. What should I be looking for in the DB that is taking up sooo much space. Is there any way to trim this? I can only assume that something has gone wrong somewhere.
      • 18397
      • 3,250 Posts
      You should go to the backup manager and empty the log tables.
        • 31559
        • 20 Posts
        thanks for the note, had just been picking through the db tables only to find the event log table was over 500MB..........what a numpty. I’ll keep an eye on it now.
          • 28042 ☆ A M B ☆
          • 24,524 Posts
          That’s not an unusual issue, there are a few posts for different causes and fixes.
            Studying MODX in the desert - http://sottwell.com
            Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
            Join the Slack Community - http://modx.org
            • 25663 MODX Staff
            • 12,272 Posts
            I suspect you’re running 0921 or 0922 with visitor logging on... if so, disable that as it can cause horrid problems. Also if you’ve got the template switcher plugin installed, delete it.
              Ryan Thrash, MODX Co-Founder
              Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
              • 31559
              • 20 Posts
              Disabled logging, deleted template switcher. Looking this morning, the log is full again with the following:

              « MODx Parse Error »
              MODx encountered the following error while attempting to parse the requested resource:
              « Too many forward attempts. »
              SQL: The request could not be completed due to too many unsuccessful forward attempts.
              [Copy SQL to ClipBoard]

              Parser timing
              MySQL: [^qt^] ([^q^] Requests)
              PHP: [^p^]
              Total: [^t^]
                • 28042 ☆ A M B ☆
                • 24,524 Posts
                This can be from several different causes; a missing include, a misconfigured 404 page, there have been a number of discussions on the forum about this. I tracked it down on my sites by comparing the server logs with the MODx event error log for the exact same time, and found some missing files.
                  Studying MODX in the desert - http://sottwell.com
                  Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
                  Join the Slack Community - http://modx.org
                  • 31559
                  • 20 Posts
                  misconfigured 404 is looking most likely at the moment......going to give it a day now to see what happens and I’ll report back. Thanks for all the help.