Forums / Install & configuration / Fatal error: Allowed memory size of 8388608...

Fatal error: Allowed memory size of 8388608...

Author Message

James Packham

Wednesday 17 September 2003 6:17:59 am

Hi I've just installed the latest version of eZ Publisher, but can't view the index.php page. When I try to load it up in a browser I get:

Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 11520 bytes) in /var/www/html/ezpublish-3.2-1/kernel/classes/datatypes/ezenum/ezenumtype.php on line 239
Fatal error: eZ publish did not finish it's request

I'm not entirely sure what all this means, so if anyone could point me in the right direction I'd much appreciate it :)

I'll put some details about my system on the end of this, along with the eZ debug (web browser view) below incase it's needed.

Many Thanks in advance,

James

-------------------------------------------------------------------------
And now for the *other* bits:

I'm running the new (non beta) version of publisher (as you can guess from the above), apache 2, php 4.2.2, ImageMagick 5.5.7, Mysql 3.23 on a Redhat 9 system.

The execution of eZ publish was abruptly ended, the debug output is present below.

eZ debug
Timing: Sep 17 2003 14:05:20

Script start

Timing: Sep 17 2003 14:05:20

Module start 'content'

Warning: eZModuleOperationInfo::execute Sep 17 2003 14:05:20

Missing main operation memento for key: b105510768d55ed7d3094a9a81c6571f

Debug: here 1 Sep 17 2003 14:05:20

array(1) {
[0]=>
string(86) "ezcontentobject.contentclass_id in (1,10,10,11,11,12,12,13,13,2,2,5,5,6,6,7,7,8,8,9,9)"
}

Timing points:
Checkpoint Elapsed Rel. Elapsed Memory Rel. Memory
Script start 0.0000 sec 0.0522 sec 0.0000KB 0.0000KB
Module start 'content' 0.0522 sec 0.0000KB 0.0000KB
Total runtime: 0.2481 sec
Time accumulators:
Accumulator Elapsed Percent Count Average
ini_load
Load cache 0.0112 sec 4.2858% 8 0.0014 sec
Mysql Total
Mysql_queries 0.0076 sec 2.9194% 13 0.0006 sec
Looping result 0.0009 sec 0.3413% 10 0.0001 sec
Template Total
Template load 0.0083 sec 3.1779% 1 0.0083 sec
Template processing 0.0000 sec 0.0000% 0 0.0000 sec
Template load and register function 0.0016 sec 0.6053% 1 0.0016 sec
override
Cache load 0.0068 sec 2.5938% 1 0.0068 sec
Total script time: 0.2604 sec

Karsten Jennissen

Wednesday 17 September 2003 6:52:30 am

Check here:
http://ez.no/developer/ez_publish_3/documentation/installation_and_configuration/troubleshooting/not_enough_php_memory

Regards,
Karsten

James Packham

Wednesday 17 September 2003 7:18:49 am

Thanks,

but I'd already tried this (I should have mentioned it really). It seems that even when I put the max allowed memory up I still get the error (I tried all the way up to 50M). I've had something like this before (on PHP Nuke), but can't remember for the life of me how I fixed it!

Anyone had this problem before? It's kind of annoying because I had the beta version of 3.2 working of sorts until this morning, when I tried to replace it with this one...

~James~

Paul Borgermans

Wednesday 17 September 2003 7:40:04 am

OK, brute force method:

1) clear the entire var/cache by hand
2) clear any php accelerator files (probably in /tmp); this you should always do after a release upgrade.

If that does not work,

3) put

phpinfo();

at the top of index.php and find the line which says which php.ini file it is using. If you used the installers, there may be a problem that the php.ini file is not the right one or it cannot find it. So your max memory settings are ignored.

hth

-paul

eZ Publish, eZ Find, Solr expert consulting and training
http://twitter.com/paulborgermans

Tony Wood

Wednesday 17 September 2003 7:57:09 am

I know this is a stupid question, but what settings did you change in the php.ini file and did you restart httpd afterwards? service httpd restart?

Tony

Tony Wood : twitter.com/tonywood
Vision with Technology
Experts in eZ Publish consulting & development

Power to the Editor!

Free eZ Training : http://www.VisionWT.com/training
eZ Future Podcast : http://www.VisionWT.com/eZ-Future

James Packham

Wednesday 17 September 2003 8:09:29 am

AH HA! It was because I didn't clear the cache, it seems to be working fine now. Sorry if I wasted your time!

Cheers,

~James~