This STABLE release causes a Stack Overflow on Apache2/WinNT4

Next topic

Author	Message
dave jones	Tuesday 01 July 2003 2:32:48 am Hello. I am running Apache2 on Windows NT 4 Server SP6a w/800Mhz Celeron 256Mb RAM. PHP 4.3.2 works wonderfully under this setup. I have successfully run b2, php-nuke, postnuke, phpWebSite, drupal, envolution, XOOPS2, mambo, phpBB, XMB, phpOpenChat, phpMyAdmin, myPHPBlog, and several other CMS/blogging systems on this setup. I am currently running a postnuke based system very successfully and have had over 15,000 hits with no problems. I have done a clean install (twice) of the eZ3.1 system but straight after the install completes any access to index.php causes a Stack Overflow error in Apache. I'm not sure what to do, since I've read the forums on here and you are undoubtedly going to blame my system, Apache2, my PHP set, my competence, my ability to read and freak sun spot activity before any one will admit that this is a problem with eZ - but I have run just about every other open source CMS on the same box and they all work like a dream. So, any ideas?
Bård Farstad	Tuesday 01 July 2003 2:36:12 am Up your PHP memory limit. eZ publish uses more than 8 MB on before it creates cache files. Try setting the memory limit to 20MB and see if it helps. If you're running Apache2 in CGI mode you will have problems, since eZ publish does not officially support CGI. You can find a patch for this in the forums. --bård Documentation: http://ez.no/doc
dave jones	Tuesday 01 July 2003 3:01:36 am OH yeah I forgot to say that I read the installation documentation, so I upped the memory limit to 20MB and enabled PATHINFO on the eZ directory. Not using PHP as CGI (ugh)! Thanks anyway.
mariuz popa	Wednesday 02 July 2003 1:26:22 am had the same issues I have changed the log level of apache from warn to debug and it seems that the index.php is crashing it ( child process exited with status 3221225725) and changed the MaxRequestsPerChild to 250 but the Requests per child still exists (infinite loop) but server don't crash now only it doesn't do anything (empty page) So i reverted to apache 1.3.27 + php 4.3.2 where it works .
dave jones	Saturday 05 July 2003 6:45:10 am thanks for the info. so is this potentially a problem with php4 or apache2. i can't change server to apache1.3 cos it's deprecated and i have to go with the latest technology. none of my production servers are running apache1.x code anymore, so i'll just have to wait until ez produces some STABLE code for the current realease of web servers.
Bård Farstad	Saturday 05 July 2003 9:00:02 am Dave, this is not an eZ publish issue. It's because PHP is not stable under Apache 2. There is nothing we can do in eZ publish about this. The reason for this is because PHP and it's extensions are not thread safe and since Apache 2 uses multithreading they do not play very well together. So until PHP is stable under Apache 2 I would not recommend running PHP applications under it in a production environment. --bård Documentation: http://ez.no/doc