Forums / Install & configuration / Fatal error: Allowed memory size of 12582912 bytes exhausted

Fatal error: Allowed memory size of 12582912 bytes exhausted

Previous topic

Install & configuration

Next topic

Author	Message
m robo	Sunday 21 January 2007 4:20:48 pm Fatal error: Allowed memory size of 12582912 bytes exhausted (tried to allocate 737280 bytes) in /home/free/tym.sk/a/aait/root/www/share/db_schema.dba on line 6405 Fatal error: eZ publish did not finish its request The execution of eZ publish was abruptly ended, the debug output is present below. get this error after install can anybody help me
kracker (the)	Sunday 21 January 2007 6:03:41 pm Greetings! I would recommend increasing the PHP memory limit. From: <i>http://ez.no/doc/ez_publish/technical_manual/3_8/installation/normal_installation/requirements_for_doing_a_normal_installation#eztoc23485_2_1</i> <i>PHP memory limit issue eZ publish needs at least 64 MB in order to complete the setup wizard. This means that you'll have to increase the default "memory_limit" setting which is located in the "php.ini" configuration file. (Don't forget to restart apache after editing "php.ini".) Normal operation requires about 16 MB. However, it is highly recommended that you keep the 64 MB setting since eZ publish consumes a lot more memory as soon as you use PDF export feature, reindex the search, etc. Multi-lingual sites that store the content in Unicode (UTF-8) will also require at least 64 MB.</i> Related threads, <i>http://ez.no/community/forum/install_configuration/hitting_memory_limit_with_64_mb http://ez.no/content/advancedsearch?SearchText=Allowed+memory+size+&SubTreeArray[]=308&SearchPageLimit=5</i> <i>//kracker titanic - Titanic tehcno remix</i> Member since: 2001.07.13 \|\| http://ezpedia.se7enx.com/
Luke Barton	Monday 22 January 2007 6:30:54 pm m robo, Another approach is this. Set your DebugOutput setting to enabled. If you see several permissions error (e.g., EZP cannot write to error logs, cache files in the var directory, etc.), then you may want to change the permissions, owner and/or group of the var directory until the errors go away. To test, chmod everything with 0777, then tighten things up as much as you can. Good luck. -Luke

Author

Message

m robo

Sunday 21 January 2007 4:20:48 pm

Fatal error: Allowed memory size of 12582912 bytes exhausted (tried to allocate 737280 bytes) in /home/free/tym.sk/a/aait/root/www/share/db_schema.dba on line 6405
Fatal error: eZ publish did not finish its request

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

get this error after install can anybody help me

kracker (the)

Sunday 21 January 2007 6:03:41 pm

Greetings!

I would recommend increasing the PHP memory limit.

From: http://ez.no/doc/ez_publish/technical_manual/3_8/installation/normal_installation/requirements_for_doing_a_normal_installation#eztoc23485_2_1

PHP memory limit issue

eZ publish needs at least 64 MB in order to complete the setup wizard. This means that you'll have to increase the default "memory_limit" setting which is located in the "php.ini" configuration file. (Don't forget to restart apache after editing "php.ini".) Normal operation requires about 16 MB. However, it is highly recommended that you keep the 64 MB setting since eZ publish consumes a lot more memory as soon as you use PDF export feature, reindex the search, etc. Multi-lingual sites that store the content in Unicode (UTF-8) will also require at least 64 MB.

Related threads,
http://ez.no/community/forum/install_configuration/hitting_memory_limit_with_64_mb
http://ez.no/content/advancedsearch?SearchText=Allowed+memory+size+&SubTreeArray[]=308&SearchPageLimit=5

//kracker

titanic - Titanic tehcno remix

Member since: 2001.07.13 || http://ezpedia.se7enx.com/

Luke Barton

Monday 22 January 2007 6:30:54 pm

m robo,

Another approach is this. Set your DebugOutput setting to enabled. If you see several permissions error (e.g., EZP cannot write to error logs, cache files in the var directory, etc.), then you may want to change the permissions, owner and/or group of the var directory until the errors go away. To test, chmod everything with 0777, then tighten things up as much as you can.

Good luck.

-Luke