By rsellwood on

Hi All

Drupal version: 6.2
Memory allocated: 32mb

I'm receiving the following error on all pages and my site is effectively down:

The requested page could not be found

This was caused by an error received when enabling some modules:

Allowed memory size of 33554432 bytes exhausted (tried to allocate 71 bytes)

The solution to the problem has been found by others here http://drupal.org/node/247757.

It seems that I have to increase the memory allocation until the problem stops.

The problem I have is that changing the php.ini to increase the memory (to say 64mb)
doesn't have any effect. My Host company say that I need to put the php.ini file in the
same folder as the script that's causing the error. Unfortunately though I can't determine where the error is coming from.

Does anyone know which script would cause this error, or have another solution?

Thanks
Richard

⋅ Categories: Drupal 6.x

Comments

vm’s picture

vm commented

put it where index.php of drupal is. Drupal is the script.

_____________________________________________________________________
My posts & comments are usually dripping with sarcasm.
If you ask nicely I'll give you a towel : )

rsellwood’s picture

rsellwood commented

Thanks for your reply.

I've updated the php.ini with a new memory allocation of 64mb. The php.ini sits in the Drupal root. I think that's where you mean so, in this instance that hasn't worked

vm’s picture

vm commented

have you run a phpinfo() to insure the memory setting isn't taking effect ?

have you tried using the php.ini in the public root ?

could you post here exact what you have in your php.ini file ?

_____________________________________________________________________
My posts & comments are usually dripping with sarcasm.
If you ask nicely I'll give you a towel : )

rsellwood’s picture

rsellwood commented

Sorry for delay in response.

1. no, good point, will do
2. no, good idea
3. memory_limit = 64m

Unfortunately, I presently haven't got access to site for an hour or so (firewall blocking) so can't check these things, but will do asap and post back.

Cheers

vm’s picture

vm commented

not sure it if matters, but my php,ini file shows a captial M

how many modules are you using ? and are they all updated to their latest releases ?

_____________________________________________________________________
My posts & comments are usually dripping with sarcasm.
If you ask nicely I'll give you a towel : )

rsellwood’s picture

rsellwood commented

Actually, you also kindly responded to my other post (http://drupal.org/node/271739) re memory vs modules and pointed me in the right direction there.

Unfortunately, it will be about 5 hours before I'm away from this firewall, it seems so I'll try your ideas and if I still have problems let all who are listening know!

Thanks for you help.

rsellwood’s picture

rsellwood commented

I've run phpinfo.php and I can see the memory update as I change the php.ini file i.e. if I change the file to 128M I can see that's taken effect by looking at phpinho.php. At present the setting is 256M but this the problem persists. There must be something else I not doing.

Any ideas will be gratefully received!

Thanks

vm’s picture

vm commented

The only thing you can do now is begini disabling modules from the DB, by setting them to zero. it's possible one of the alpha or beta modules have a problem and now you try and narrow it down.

_____________________________________________________________________
My posts & comments are usually dripping with sarcasm.
If you ask nicely I'll give you a towel : )

rsellwood’s picture

rsellwood commented

Thanks. Will give it a go. Already turned some off without any luck but will try more. May just have to start over.

Thanks again for your help.

5 mins later...

For the record it didn't work, but worth a go. Time to start over. I see I'm not the only person to have this issue recently with v6. I'll see if I can reproduce it.

olskar’s picture

olskar commented

I have the very same issue :(