v0.9.6.3 : modx_event_log overload

Hello,

Thousands of modx_event_log records are added up daily. It takes server resources and slows down the backup process drastically.

I have made sure to un-check "Log visits (stats)" for each document and in Tools -> Configuration.

All records are similar in content (other then record id and creation time stamp):
eventid: 0
type: 3
user: 0
usertype: 0
source: Parser
description: blank

Installed modules on this site are: Doc Manager and Sitemap Generator

Installed plugins are:
* Core and Manager
o Bottom Button Bar (1) - Adds a set of buttons to the bottom of all manager pages
o Forgot Manager Login (2) - Resets your manager login when you forget your password.
o Inherit Parent Template (3) - New docs automatically select template of parent folder
o QuickEdit (4) - Front-end Content Editor. (Locked)
o TinyMCE (5) - 3.2.0.1: TinyMCE RichText Editor Plugin
* Search
o Search Highlighting (6) - 1.3 - Show search terms highlighted on page linked from search results.
* uncategorized
o Image TV Preview (7) - 1.2.0.4 - Show preview of any images loaded into image Template Variables

Could you please help me figure out how to prevent writing to modx_event_log?

Many thanks.

The event log is logging errors in parsing and processing snippets and plugins. Figure out what the errors are and fix the errors; there should ideally never be any entries in that table.

Thanks for your reply, sottwell. However, shouldn’t there be some info in the generated records that tell us about the problem and its source?

Well it is telling you there’s an error, but it can’t always tell what exactly the error is. Try making a test template with just basic HTML and a test resource with some basic lorem ipsum content, and after clearing the event log load that page several times in your browser; it shouldn’t generate any events. If it does, then your plugins would be suspect, particularly the search_highlighting plugin. Check your server error logs and access logs, and if you have a php error log check that as well. It might be a good idea to configure your PHP to log its errors to a file. This could be a ’bot hitting some known old MODx vulnerability, or at any rate trying to, thus causing the unknown errors.

Thank you very much. Disabling Search Highlighting didn’t help.

I’ll start going through the rest of your recommended checklist and post the cause once found.

I’d also strongly suggest upgrading from 0963, as the latest Evo release contains a ton of security and performance fixes, as well as general bugfixes. This might fix the error log too.