We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 7768
    • 8 Posts
    I have just received a message from my hosting company that the modx_event_log table on my modx size is too big. The table grew to 185GB, yes that’s right 185GB and have to be truncated. when i checked the table after that it has quickly grew to 300MB and I had to remove all the entries again. I have searched through the forums and the following thread (http://modxcms.com/forums/index.php?topic=25758.0) suggested that it might have something to do with the PHx plugin and the plugin can be disabled to prevent the modx_event_log table from becoming too big. Well I can’t find the PHx plugin in manager of a folder in Plugins on the server so how do I disable it. Or perhaps even better how do i disable event logging for MODx. I have several websites running MODX 0.9.5 and 0.9.6 and can’t find an option to disable logging on both.

    Can anyone help? I need to sort this house ASAP else the hosting company will close down my sites.
      • 7231
      • 4,205 Posts
      I don’t think that there is an option to disable logging (I could be wrong though). If you are not using PHx then that would no be the cause. Have you looked at the log table to see what it is logging? Usually i see manager actions in the log (editing and adding pages and manager related stuff like that). For it to get to 300mb that is a lot of activity, you may have something going on that you are not aware of (some endless loop).
        [font=Verdana]Shane Sponagle | [wiki] Snippet Call Anatomy | MODx Developer Blog | [nettuts] Working With a Content Management Framework: MODx

        Something is happening here, but you don't know what it is.
        Do you, Mr. Jones? - [bob dylan]
        • 7768
        • 8 Posts
        Between posting on the forum and now. The table has gone up to 57MB now. I have looked at the log and they all seems to be generated by something called Parser. I view the individual logs and got this:

        Event Id: 0 Source: Parser

        Date: 09-Oct-2008 12:59 PM User:



        « 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^]


        Can anyone tell me what’s going on here?
          • 7768
          • 8 Posts
          now found the problem. the client that the site was developed for got somebody else to include a booking script that seems to be causing the error that was being logged. When i removed the script the error was no longer being logged and then i inserted the script again and voila, the table was filling up like mad. I have now removed it and contacted the client.
            • 7231
            • 4,205 Posts
            I am sorry I misunderstood, I thought it was the manager actions log not the system event log. The system event log will fill up with script issues. Whenever I install a new snippet I check the log to see if anything gets triggered. This is specially true with modules since they will record all undeclared variables as errors and can quickly get out of hand in the log.

            Glad you spotted the problem script. grin
              [font=Verdana]Shane Sponagle | [wiki] Snippet Call Anatomy | MODx Developer Blog | [nettuts] Working With a Content Management Framework: MODx

              Something is happening here, but you don't know what it is.
              Do you, Mr. Jones? - [bob dylan]