By jbc on

I've upgraded from drupal 442 to 4.5 on my localhost server (using WAMP) everything runs ok.

When I uploaded the upgraded instalation and database to the server, it worked ok for a while, (though some strange things were happening with the themes) then crashed, with what I think was the same error message as below.

I completely re-uploaded the instal into a fresh folder on the server and then changed that folder to become my public_html folder, only to consistently received this error message:

Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 65219 bytes) in /home/sites/eternalpurpose.org.uk/public_html/includes/database.mysql.inc on line 65

Can anyone advise on this and what may be causing it?

Thank you.

Comments

killes@www.drop.org’s picture

killes@www.drop.org commented

Which url did you try to access? How many modules do you have installed? Can you try to disable some?

--
If you have troubles with a particular contrib project, please consider to file a support request. Thanks.

--
Drupal services
My Drupal services

jbc’s picture

jbc commented

The last time this occurred, I could access various pages, but attempting open the modules page caused the crash, with a similar error message only referring to the blogapi.module rather than database.mysql. Going back a page allowed me to continue for a while, but finally, attempting to switch on clean url's caused the whole thing to break down irrevocably again.

I have 54 modules, 49 installed including the 'out of the box' modules.

Yes, I can disable some - would that mean uninstalling or simply disabling temporarily? I'll try the latter and then upload the d/b (about 5mb) again.

Is that likely to be a short-term fix or am I simply running too many modules?

Thanks for advice...

Shalom!
John

killes@www.drop.org’s picture

killes@www.drop.org commented

On that particular page all of the 54 modules will get actually included. This drives Drupal over the (not huge) 8MB limit your hoster allowed PHP processes to have. Unless you can increase this limit you should consider removing several modules. You don't really need all 54 of them, or do you?

--
If you have troubles with a particular contrib project, please consider to file a support request. Thanks.

--
Drupal services
My Drupal services

jbc’s picture

jbc commented

thanks for your further input, Killes

I find it reassuring, understanding what the error message is telling me. Your're right, in one sense, few of the 22 additional modules are completely indespensable... (there are 32 modules in an 'out of the box' instal) but each one add a little enhancement to the site : feedback, flexinode, print, title, weblink, subscriptions... etc. I'd miss them! And actually it's no more than I was using without difficulty before... although I notice that the number of tables in the d/b has increased by about 50% to support the upgraded modules.

I'd have thought, like you imply, that the 8mb limit was probably a bit severe and will definitely ask my host to up the limit. They had a runaway sql problem a fortnight ago and may have battened down the hatches a little to stop it occurring again. (I got similar error messages by the bundle then and spent hours trying to debug before realising it wasn't to do with my site, as such.)

Shalom!
John

jbc’s picture

jbc commented

My host has arranged for me to be able to set my own variable for php limit, but placing a php.ini file within my directory. Could you advise on the minimum content such a file would need? I don't believe it needs to set all the variables, it just needs to include the variables I am going to override...

thanks...

Shalom!
John