|
Author
|
Message
|
|
LORENZO FOLEGATI
|
Tuesday 08 June 2004 1:25:42 am
I HAVE INSTALLED EZP 3.4 WITHOUT ANY PROBLEM. WHEN I CLICK IN THE LAST SCREEN TO GO TO THE LINK OF THE USE AREA OR TO THE ADMIN AREA APPREAR THIS MESSAGE
Fatal error: Maximum execution time of 30 seconds exceeded in /var/www/html/sintesys/ezp/lib/ezxml/classes/ezxml.php on line 274
Fatal error: eZ publish did not finish it's request The execution of eZ publish was abruptly ended, the debug output is present below.</
|
|
Lazaro Ferreira
|
Tuesday 08 June 2004 10:18:47 am
Hi,
Go to your php.ini file and increase this settings, you can double default values to
i.e:
max_execution_time = 60 ; Maximum execution time of each script, in seconds
memory_limit = 32M ; Maximum amount of memory a script may consume (8MB) Restart your web server if you needed (php module)
Lazaro
...
http://www.mzbusiness.com
Lazaro
http://www.mzbusiness.com
|
|
Tor Magne Ulsund
|
Wednesday 04 August 2004 8:41:35 pm
I have the same problem. I've tried setting the timeout to 600 seconds and the PHP memory limit to 128M without any luck. I'm running Apache 2.0.50 and PHP 4.3.8 on W2K Server. Any good or bad ideas?
|
|
Paul Wolotsky
|
Sunday 22 August 2004 5:44:06 am
I have the same probome - any resolution??? php.ini settings are correct.
|
|
Zbyněk Voráček
|
Monday 23 August 2004 3:47:03 am
I have some problem.
My php.ini
max_execution_time = 300
max_input_time = 180
memory_limit = 32M Win2000/Apache2.0.49/PHP4.3.7 On screeen "Finished" Note: The first time the user or admin site is accessed it will take some time (<b>30 to 60 seconds</b>). This is because eZ publish prepares the site for your machine. ??? My PC is: Pentium III /860 MHz /128 MB RAM
|
|
Hans Melis
|
Monday 23 August 2004 4:34:08 am
Hi, The max_execution_time setting in php.ini doesn't matter for template compiling (which is what's happening when you first click those links) because it's overriden anyway unless the timeout value is set to 0. There's a fixed 30 second timeout for each template, so each template has 30 seconds to compile. The fact that 30 seconds aren't enough indicates another problem that causes template compiling to be extremely slow. Are you using a (very) low end machine? As an alternative idea, you could use the commandline script to compile templates. It's bin/php/eztc.php, and use the --help option to see what's possible.
--
Hans
Hans
http://blog.hansmelis.be
|
|
Maarten Holland
|
Wednesday 25 August 2004 4:30:20 am
I've got the same problem with 3.4.1, even tough I managed to install 3.4 beta (2 I believe) on that machine without any problems. Did the compiler get that heavy recently? I've increased the max exectiont time up to 3000 seconds and set the memory limit to 64 MB. I tried 3.4.1 on several machines (PIII 933MHz 512MB Windows XP; PIII 500 MHz 512MB SuSE Linux 9.0; PIV 2.8GHz, 1GB RAM) and only the PIV went okay. I hope PIV isn't the new minimum requirement for ezPublish? The compilerscript doesn't seem to work either...
|
|
Francesca G
|
Wednesday 25 August 2004 6:58:47 am
I had the same problem. I modified the htaccess ( http://ez.no/community/forum/developer/if_you_have_problems_as_slow_or_30_sec_solution ) and it worked :)
--------
My artworks collective @ http://www.something-good.com/francy
|
|
Valerie Lynn
|
Wednesday 25 August 2004 9:15:35 am
Same problem. Modifying php.ini did not solve the problem. Now I'm currently uploading the latest revision.
Val
~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
Is it dinnertime yet?
|
|
Wilko van der Lingen
|
Sunday 29 August 2004 4:29:14 am
I had the same problem running 3.4.1 on a PII 200Mhz, but it works now. As mentioned before, the problem is a hardcoded time limit. See also bugreport http://www.ez.no/community/bug_reports/set_time_limit_hardcoded_leading_to_timeout
Because I have a slow server the max_execution_time in php.ini is 120, but this didn't solve the problem. To solve the problem I have modified the file lib/eztemplate/classes/eztemplatecompiler.php. In that file you can find two lines with @set_time_limit( 30 )
Changing 30 to a higher hardcoded value will solve the problem. Another option is to change both lines to @set_time_limit( ini_get( 'max_execution_time' )
to read the max_execution_time value from the php.ini file, so there are no hardcoded values anymore. I have choosen the last option with success.
|
