095 RC2 Too many forward attempts issue

I recently upgraded a site from 0921 to 095 RC2 rev 1942 and have discovered a problem with the "events_log" table quickly filling up with large batches of "parser errors" - up to several thousand rows each time! They all seem to be the same error:

"Event Id: 0 Source: Parser
Date: 14-Nov-2006 11:04 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."

I also just noticed that it appears that only the last error in the batch has a username listed (my admin user).

This is happening in bursts and resulting in the "events_log" table quickly reaching 100-200 MB or more in size.

Can anyone please shed some light on this?

Thanks,
Anton

Quote from: rthrash at Nov 14, 2006, 01:40 PM

How did you upgrade, and does your config.inc.php file include the following starting around line 32?

    if (!defined('MODX_BASE_PATH')) define('MODX_BASE_PATH', $base_path);
    if (!defined('MODX_BASE_URL')) define('MODX_BASE_URL', $base_url);
    if (!defined('MODX_SITE_URL')) define('MODX_SITE_URL', $site_url);

I renamed the old "public_html" folder, uploaded and extracted the 095 files into a new "public_html" folder, moved the images across from the old "assets/images" folder, adjusted the usual file permissions, and ran the installer, configured friendly URLs, renamed "ht.access" to ".htaccess", deleted install folder, and lowered permissions for config.inc.php to 644.

Yes, those 3 lines appear in the config.inc.php file starting at line 32.

Thanks,
Anton

Quote from: AntonL at Nov 14, 2006, 06:18 AM

I recently upgraded a site from 0921 to 095 RC2 rev 1942 and have discovered a problem with the "events_log" table quickly filling up with large batches of "parser errors" - up to several thousand rows each time! They all seem to be the same 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."

This is happening in bursts and resulting in the "events_log" table quickly reaching 100-200 MB or more in size.

Anton, a few other questions for you...one, do you have an error page and/or unauthorized page configured that is invalid or unpublished or otherwise inaccessible? Two, did you make sure you copied any files from assets/plugins, assets/modules, or assets/snippets for any custom components you have installed for your site? Are you sure all the files were transferred properly and a file isn’t corrupted? This is one I definitely want to resolve before release.

Quote from: OpenGeek at Nov 14, 2006, 05:46 PM

Anton, a few other questions for you...one, do you have an error page and/or unauthorized page configured that is invalid or unpublished or otherwise inaccessible?

Hi Jason,

It appears that this was the problem. I didn’t notice that the upgrade had resulted in new IDs being set for those config fields.

Thanks,
Anton

The upgrade should not have reset those fields though I don’t think... do you?

Quote from: rthrash at Nov 14, 2006, 07:49 PM

The upgrade should not have reset those fields though I don’t think... do you?

This assumption was based on the fact that the site was working fine before the upgrade and I hadn’t altered those settings myself. However, there is still the possibility that the problem was pre-existing and I just hadn’t noticed it!

Anton

Which brings up the point that we should add a config check I think, to go along with the new register_globals set to on check .

Hello

Well... I had the same problem... reading taht thread, I thnik this was beacause the "unauthorized page" was wrong as I don’t use such feature... I will see tomorrow if my problem is solved.

But I write here because I think there is another problem with that message : all right, i (may) have a problem of configuration ...
but I had 50 pages of error log filled with that error... (at least for the very first page) all messages went out at the same time ..
isn’t it in bit too much May be there is an infinit loop here ?
I’m sorry I’ve first deleted every old history for not having risk of hanging of the site - so I can’t give you much more details... but I think it can easily be reproduced.

Agree, a check to see if this warning is already in the logs would be sensible.

Quote from: piwaille at Nov 17, 2006, 04:19 AM

But I write here because I think there is another problem with that message : all right, i (may) have a problem of configuration ...
but I had 50 pages of error log filled with that error... (at least for the very first page) all messages went out at the same time ..
isn’t it in bit too much May be there is an infinit loop here ?

This is a new feature and the reason you get that message is to prevent an infinite loop. There is something in the manager though that is calling it improperly from what I gather, but I have yet to make it happen. If anyone can reproduce it, please enter a bug report with as much detail as possible.