3.5 rc1 crashing Apache2 - status 3221225477

Next topic

Author	Message
Dave Myron	Wednesday 08 December 2004 12:15:22 pm Since I wasn't able to get past the first setup step with 3.4.4 I decided to try 3.5 RC1. Now the index.php won't even load even the first step of setup. (Returns "document contains no data" in Firefox and "the page cannot be displayed" in IE). Checking Apache's error log reveals this error: [Wed Dec 08 12:09:33 2004] [notice] Parent: child process exited with status 3221225477 -- Restarting. Any ideas? I'm using The Saint WAMP (TSW) - an open-source (sourceforge project is named yawamp) WAMP server. Server software is: Apache 2.0.50 Mysql 4.0.20d PHP 4.3.8 Perl 5.8.3 TIA, chicken
Alex Jones	Wednesday 08 December 2004 12:49:48 pm Apache 2 isn't officially supported, though apparently some people have managed to get it working. See this page for the requirements: http://ez.no/ez_publish/documentation/general_information/what_is_ez_publish/ez_publish_requirements If possible, you may want to use Apache 1.3 instead. Alex [ bald_technologist on the IRC channel (irc.freenode.net): #eZpublish ] <i>When in doubt, clear the cache.</i>
Dave Myron	Wednesday 08 December 2004 1:06:29 pm Hmm. I meet or best those requirements (I try to make sure and read as much documentation as possible to avoid looking like an idiot - usually I'm successful). It's just weird that it's only occurring with EZP. Unfortunately rolling back to 1.3 isn't an option currently. Tight schedules and all on this project (of which I'm burning more and more time on). I know this isn't the best place to ask <wink> but can anybody recommend another CMS that I can try? I was really excited to learn and implement EZP but if I can't get past the first setup step I'm pretty much dead in the water. If anybody out there is using Apache2 successfully did you run into any issues that may be related here? Thanks, chicken
Bruce Morrison	Wednesday 08 December 2004 1:51:42 pm We host around 30 ez sites all running on apache 2 and haven't seen an issue related to apache 2 since upgrading apache. There was a discussion previously about the use of apache 2 with php in general here: http://ez.no/community/forum/install_configuration/apache_2_0_support_official With that said, I'm pretty sure that this error is not an apache issue. The error log is simply reporting that the child process (php I suspect) exited with that status. I suggest that you loik some standard php settings memory_limit - the default is 8Mb ez needs more than this 20Mb should be OK max_execution_time - (i think) the default is 30 secs, depending on your hardware you will probably need to increase this is template compiling is turned on. A google on the error message indicates that this is an issue with other apps as well. http://www.google.com.au/search?sourceid=mozclient&ie=utf-8&oe=utf-8&hl=en&q=+Parent%3A+child+process+exited+with+status+3221225477 My Blog: http://www.stuffandcontent.com/ Follow me on twitter: http://twitter.com/brucemorrison Consolidated eZ Publish Feed : http://friendfeed.com/rooms/ez-publish
Łukasz Serwatka	Wednesday 08 December 2004 2:22:20 pm Hi, Bruce you have right. I`ve run and test a lot of eZ publish websites on apache 2 on Win32 and Unix platforms and i never had any problems. Good configuration of web server is a key for stable work. I think that apache 2 is full supported platform. We running php.pl on apache 2.0.52 without any problems. Personal website -> http://serwatka.net Blog (about eZ Publish) -> http://serwatka.net/blog
Derick Rethans	Thursday 09 December 2004 12:30:22 am Hello! I would advise you to install the different parts of your WAMP server from official sources. Both Apache 2.0.50, MySQL and PHP 4.3.8 are also not the latest version and usually a lot of bug fixes are done between releases, especially related to stability on Windows. In case you can reproduce this with the latest versions of all the components from the original sources, and you are still getting this error you should file a bug with the PHP development team at http://bugs.php.net, as I am convinced that this is not a problem in eZ publish itself. As you are running RC1 now, you might want to retest with RC2 which is due out in the next few days. regards, Derick
Gabriel Ambuehl	Thursday 09 December 2004 12:03:58 pm Make sure you aren't using threaded Apache 2 as PHP isn't thread safe. You must stick to the traditional prefork model. Disclaimer: I can't personally be bothered with Apache 2, but that's what I found in short tests. And Windows is pretty much the worst platform for Apache... Visit http://triligon.org
Dave Myron	Friday 10 December 2004 1:07:16 pm Well I moved everything to a FreeBSD box I have (running Apache 2.0.52 prefork and PHP 4.3.9). I did run into a problem with MySQL 4.1.7 on this system but apparently it's already been found to have problems with ezPublish (the other way around, rather) and rolling back to the latest 4.0.x release fixed it. I've now cruised through the tutorial twice (and found some bugs that I'm hoping my fresh RC2 install will take care of) Thanks for the insight guys. Much appreciated, chicken