[Help] Fatal error without bug report during installation.

Next topic

Author	Message
Timm Papke	Friday 30 September 2005 3:34:09 am Hi there. I just installed the current version correctly and wanted to install it. First of all it told me: <i>"Welcome to the eZ publish content management system and development framework. This wizard will help you set up eZ publish. Your system is not optimal, if you wish you can click the Finetune button. This will present hints on how to fix these issues. Click Next to continue without finetuning."</i> It doesn't matter which option i select i get this message: <i>"Fatal error: eZ publish did not finish its request The execution of eZ publish was abruptly ended, the debug output is present below."</i> So I don't know what i should do now. I have not found anything to fix the problem. PS: Running Apache Server 1.3.26 (UNIX) & PHP 4.3.1
Kristof Coomans	Saturday 01 October 2005 3:19:14 am Modify your PHP settings file (php.ini): error_reporting = E_ALL display_errors = On Now the PHP error messages are also printed and you can trace the problem. independent eZ Publish developer and service provider \| http://blog.coomanskristof.be \| http://ezpedia.org
Marko Žmak	Saturday 08 October 2005 10:49:33 am This error usuall occurs when PHP comes to a critical errror that doesn't reproduce an error message. It haappened to me something similar. I had a working installation of eZ and I noticed the bug when tried to execute som eZ PHP scripts from the shell. After days of debugging, I found out that the CGI version of PHP (the one used in shell execution of scripts) didn't have mysql extension loaded. So when PHP came to the eZ code that tried to execut mysql_connect() function, PHP crushed without any error or warning. Possible soluutions: 1) You could check out your configuration of PHP, or try to execute your own script that executes only mysql_connect() or any other PHP function that you suspect is missing. 2) You could also try debbuging eZ code as I did... by putting to comments some parts of the eZ PHP code, or putting exit() command in some places of PHP code. So you can see exactly where the script crashes. But I suggest to try the first sollution first. Hope this helps you. -- Nothing is impossible. Not if you can imagine it! Hubert Farnsworth

Author

Message

Friday 30 September 2005 3:34:09 am

Hi there. I just installed the current version correctly and wanted to install it.

First of all it told me:
<i>"Welcome to the eZ publish content management system and development framework. This wizard will help you set up eZ publish.
Your system is not optimal, if you wish you can click the Finetune button. This will present hints on how to fix these issues.
Click Next to continue without finetuning."</i>

It doesn't matter which option i select i get this message: <i>"Fatal error: eZ publish did not finish its request

The execution of eZ publish was abruptly ended, the debug output is present below."</i>

So I don't know what i should do now. I have not found anything to fix the problem.

PS: Running Apache Server 1.3.26 (UNIX) & PHP 4.3.1

Kristof Coomans

Saturday 01 October 2005 3:19:14 am

Modify your PHP settings file (php.ini):

error_reporting  =  E_ALL
display_errors = On

Now the PHP error messages are also printed and you can trace the problem.

independent eZ Publish developer and service provider | http://blog.coomanskristof.be | http://ezpedia.org

Marko Žmak

Saturday 08 October 2005 10:49:33 am

This error usuall occurs when PHP comes to a critical errror that doesn't reproduce an error message.

It haappened to me something similar. I had a working installation of eZ and I noticed the bug when tried to execute som eZ PHP scripts from the shell. After days of debugging, I found out that the CGI version of PHP (the one used in shell execution of scripts) didn't have mysql extension loaded. So when PHP came to the eZ code that tried to execut mysql_connect() function, PHP crushed without any error or warning.

Possible soluutions:

1) You could check out your configuration of PHP, or try to execute your own script that executes only mysql_connect() or any other PHP function that you suspect is missing.

2) You could also try debbuging eZ code as I did... by putting to comments some parts of the eZ PHP code, or putting exit() command in some places of PHP code. So you can see exactly where the script crashes. But I suggest to try the first sollution first.

Hope this helps you.

--
Nothing is impossible. Not if you can imagine it!

Hubert Farnsworth

eZ debug

Timing:	Jan 20 2025 08:48:58
Script start
Timing:	Jan 20 2025 08:48:58
Module start 'layout'
Timing:	Jan 20 2025 08:48:58
Module start 'content'
Timing:	Jan 20 2025 08:48:58
Module end 'content'
Timing:	Jan 20 2025 08:48:58
Script end

Main resources:

Total runtime	0.0184 sec
Peak memory usage	2,048.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0070	589.4375	152.6563
Module start 'layout'	0.0070	0.0028	742.0938	39.4922
Module start 'content'	0.0099	0.0063	781.5859	89.5547
Module end 'content'	0.0162	0.0022	871.1406	34.3047
Script end	0.0184		905.4453

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0029	15.5728	14	0.0002
Check MTime	0.0014	7.5105	14	0.0001
Mysql Total
Database connection	0.0009	5.1117	1	0.0009
Mysqli_queries	0.0027	14.4910	3	0.0009
Looping result	0.0000	0.0866	1	0.0000
Template Total	0.0018	9.9	1	0.0018
Template load	0.0010	5.1556	1	0.0010
Template processing	0.0009	4.7226	1	0.0009
Override
Cache load	0.0007	3.5672	1	0.0007
General
dbfile	0.0003	1.3661	8	0.0000
String conversion	0.0000	0.0388	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	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs