Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

garbage collector: Garbage Collector and Logrotate causing problems with Crontrigger (Trac #3420) #3420

Closed
elgg-gitbot opened this issue Feb 16, 2013 · 1 comment

Comments

@elgg-gitbot
Copy link

Original ticket http://trac.elgg.org/ticket/3420 on 41342450-07-04 by trac user juho.jaakkola, assigned to unknown.

Elgg version: 1.7

It seems that Garbage Collector and Logrotate may cause the site to break if triggered by Crontrigger.

Noticed this when users complained that they cannot log in. There was visible text printed by Garbage Collector on the page ("Cleaning up unlinked metastrings:"). After disabling gc the users were able to login again.

Later I tested crontasks with trigger_plugin_hook() and it seems that logrotate also breaks the site:

exception 'DatabaseException' with message 'Table 'elgg_system_log_1304578402' already exists

QUERY: CREATE TABLE elgg_system_log_1304578402 as SELECT * from elgg_system_log WHERE time_created<1302159202' in .../engine/lib/database.php:187

Stack trace:
#0 .../engine/lib/database.php(387): execute_query('CREATE TABLE elgg...', Resource id #45)
#1 .../engine/lib/system_log.php(251): update_data('CREATE TABLE elgg...')
#2 .../mod/logrotate/start.php(48): archive_log(2419200)

Tested with Elgg 1.7.8

@elgg-gitbot
Copy link
Author

cash wrote on 41343294-08-07

Please disable crontrigger and set up a cron job. crontrigger has some problems and is not supported by the core team. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

1 participant