I just installed Cache Expiration a few hours ago and I'm not attempting to run some module updates via update.php. I'm finding that the update.php process takes an excessive amount of time now and that my server's RAM is getting filled to the point of crashing the server.

I've attempted this now 3 times with the same result over a few hours.

Any ideas why this is happening? Is it trying to rebuild every single thing on the site all at once without dumping what is completed? I have 2GB of RAM which is plenty for my site which is loaded with modules but currently does not have any other users and only a few test nodes in place.

I guess my only recourse is to completely disable this module or disable it during updates which just adds to the already painful and time-consuming task.

Any help would be appreciated!

Well, trying a third time corrupted the database to the point where I got a 500 Internal Server Error even after rebooting the server. I only installed one other module besides HTTPRL (which wasn't the cause of this error), and that other module was Imageinfo Cache and since I'm starting over from a backup db, I'm not sure which it was for sure. OK, it's 5:30am, time to end this madness for the moment.

Comments

Spleshka’s picture

Status: Active » Closed (works as designed)

The Cache Expiration has nothing to do with update.php at all. So I don't think this issue is related somehow to this module.

deanflory’s picture

Yeah, well as my original post states, it does cause something that interferes on my installation. Close it if you want to but the issue is still present.