Forums / Install & configuration / installation of 3.9.1: Segmentation fault
Michael Kress
Thursday 15 March 2007 5:01:27 am
Hi,
I can't get ez publish installed, I get the following error in apache's error log:[notice] child pid 2492 exit signal Segmentation fault (11)
I tried this: * unpack 3.9.0 * executed a simplified chown apache.apache . -R* first call of index.php works
(delete everything)
* unpack 3.9.1 * executed a simplified chown apache.apache . -R* first call of index.php shows up the error above, browser win: empty
Environment: * centos4 @ i686 * httpd-2.0.52-28.ent.centos4 * self compiled php 4.4.6* memory_limit in php.ini: 84M
This is kind of similar to http://issues.ez.no/8148 but the chown didn't work. Any ideas? RegardsMichael
Nabil Alimi
Thursday 15 March 2007 5:24:02 am
Hi Michael,
I had the same problem earlier. My server lacked php-cli. After installing it, everything worked fine.Actually, I also adjusted server clock, but I don't think this was the solution to the problem. :)
My blog : http://www.starnab.com/ezpublish / http://www.starnab.com/ / http://www.assiki-consulting.com eZ Publish Freelance developper. Feel free to contact me +33 674 367 057 nabil at assiki d0t fr
Thursday 15 March 2007 7:53:35 am
Hi, are you talking about the command line interface? I definiteley have the cli installed: # php -v PHP 4.4.6 (cgi) (built: Mar 5 2007 05:52:46) Copyright (c) 1997-2007 The PHP GroupZend Engine v1.3.0, Copyright (c) 1998-2004 Zend Technologies
RegardsMichael
Friday 16 March 2007 10:27:28 pm
JFYI, on x86_64 it works, same environment, just another arch.
Tuesday 17 April 2007 3:23:30 am
I noticed something strange.In my previous post, I said while joking, that I ajusted server clock as a solution to this issue. But it seems that server time has <i>actually</i> something to do with this.
I tested this a few minutes ago. I have local eZpublish instance running on my own PC with the local version of my own site (the one below;)). I changed Windows date to 1st February. I accessed my website without any problem. I then cleared caches. I was then unable to access my site. I changed the clock back to today.The site was running smoothly again.
I don't know how server clock can be related to such an issue, (Probably some cache expiry ?) but I wanted to share my experience with you.
Hope it can help someone.