Segmentation fault (11)

Next topic

Author	Message
Phlip Wards	Tuesday 04 May 2004 9:36:30 pm I am trying to setup eZ publish 3.3-4 on Red Hat 9, Apache 1.3, PHP 4.3.3 and PostgreSQL 7.3.4. When I enter the servername/username/password and click Next at the Database Initialization step of the setup wizard, I am sent back to the first step of the wizard. Looking through my Apache logs, I found a segmentation fault. I do have PHPBB, Mad.Thought and Horde running on the same installation without problems. I do know that eZ publish with MySQL will work on the same installation (but I don't like MySQL). What can I do to fix the problem? If you need more detail about my setup, I can post the output from phpinfo. Thanks.
Sten Thorstensen	Wednesday 05 May 2004 2:42:28 am please go through the whole Apache configuration, i most cases I've found Segmentation fault (11) being caused by a missconfigured VirtualHost or something. I've also read in many forums that this can be caused by bad physical memory, but I think you should check your configuration first. ~st
Willie Seabrook	Wednesday 05 May 2004 4:02:29 pm I'd like to pump the significance of this post up a little cause I think there may be more to it. I use Zend to develop in. Whenever I debug I regularily get segmentation faults exactly like that. The Zend guys never figured it out. I think they ended up thinking I was crazy ;-) But it happens all the time and randomly. Both on Apache 1.3 and 2.0 (I've found 2.0 much more stable) Stepping through the debugger to find out what line or lines causes it comes to no avail as it happens in random places.
Phlip Wards	Wednesday 05 May 2004 5:55:27 pm I do not have eZ publish running in virtual host mode, but I do have virtual hosts. I have gone over my Apache configuration and I do not see anything wrong with it. Should I post my configuration?
Phlip Wards	Friday 07 May 2004 7:36:18 am Alright, here's another weird thing going on. I know the problem is with eZ publish now. I have two computers: one at work and one at home. My original post refers to my home computer. My work computer runs eZ publish on PostgreSQL just fine (except for a problem with module not found errors when I use the setup link class, but I'll save that problem for another post). My work computer runs the exact same software (Red Hat 9, Apache 1.3, PHP 4.3.3 and PostgreSQL 7.3.4) because I built the RPMS at home and brought them to work. Anyways, I upgraded my work computer to eZ publish 3.3-5. Now it gets segmentation faults. I reverted back to eZ publish 3.3-4 and everything works again. I will try diffing the two and see if I can fix this myself, but if anyone has any ideas on how to fix this, please share. Thanks.
Phlip Wards	Friday 09 July 2004 6:29:20 am Just an update. Whatever you guys did in 3.4 fixed the segmentation fault problem. Keep up the great work!

eZ debug

Timing:	Jan 18 2025 18:24:43
Script start
Timing:	Jan 18 2025 18:24:43
Module start 'layout'
Timing:	Jan 18 2025 18:24:43
Module start 'content'
Timing:	Jan 18 2025 18:24:44
Module end 'content'
Timing:	Jan 18 2025 18:24:44
Script end

Main resources:

Total runtime	0.5301 sec
Peak memory usage	4,096.0000 KB
Database Queries	68

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0085	587.9141	152.6250
Module start 'layout'	0.0085	0.0027	740.5391	39.4609
Module start 'content'	0.0111	0.5176	780.0000	567.6797
Module end 'content'	0.5288	0.0012	1,347.6797	12.1719
Script end	0.5300		1,359.8516

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0038	0.7116	16	0.0002
Check MTime	0.0014	0.2560	16	0.0001
Mysql Total
Database connection	0.0013	0.2519	1	0.0013
Mysqli_queries	0.4774	90.0734	68	0.0070
Looping result	0.0006	0.1208	66	0.0000
Template Total	0.4961	93.6	2	0.2480
Template load	0.0021	0.3894	2	0.0010
Template processing	0.4940	93.1919	2	0.2470
Template load and register function	0.0002	0.0315	1	0.0002
states
state_id_array	0.0016	0.2939	1	0.0016
state_identifier_array	0.0011	0.2039	2	0.0005
Override
Cache load	0.0017	0.3274	24	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0012	0.2271	3	0.0004
Fetch class attribute name	0.0011	0.2016	7	0.0002
XML
Image XML parsing	0.0009	0.1683	3	0.0003
class_abstraction
Instantiating content class attribute	0.0000	0.0025	7	0.0000
General
dbfile	0.0009	0.1658	16	0.0001
String conversion	0.0000	0.0013	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded
1	node/view/full.tpl	full/forum_topic.tpl	extension/sevenx/design/simple/override/templates/full/forum_topic.tpl
6	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
6	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
1	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
1	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 16 Number of unique templates used: 6

Time used to render debug report: 0.0001 secs