Cron failing due to DBA after move to PHP5
rkdesantos - April 25, 2008 - 04:50
| Project: | Database Administration |
| Version: | 5.x-1.x-dev |
| Component: | PHP 5 Support |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | duplicate |
Jump to:
Description
I recently moved to PHP5 (and since Drupal has been running under it) cron is failing due to a dba module error:
Fatal error: Allowed memory size of 52428800 bytes exhausted (tried to allocate 19447163 bytes) in /home/afana/public_html/drupal5/modules/dba/dba.module on line 1430
Based on reading old issues here this may have something to do with backing up a large table... but which one? How do I figure out what is going on? The problem has only occurred since the PHP change so it is also related to the way PHP5 controls memory allocation... different from PHP4 so I am told.
#1
I added every large table except for the node data to the list of tables for which only the schema are backed up and the error still occurs. The choke point appears to be the node_revisions table but that's only a guess. I can't use the DBA module until I can get around this.
#2
This is related to this item: http://drupal.org/node/103911
After applying the patch in the referenced item manually AND increasing the timeout interval for cron AND screening out all of the largest tables (in particular the old_revisions) the backup ran successfully. There are obviously still some major memory and timeout issues that need addressed.