Wednesday 06 January 2010 6:51:32 am
In approximate order of ease of use, my typical steps to troubleshoot eZ.. Examine apache server error log. On my server.. #tail /var/log/apache2/error_log CentOS may have different path or log file name. The concept is to view the last few lines of apache errors returned immediately after the failed attempt. eZ provides error logging as well. From the eZ Publish doc root.. # tail var/log/error.log ..can also be informative for troubleshooting. Same concept, more eZ specific errors. Obviously only works if installation was successful. Another option --temporarily-- set PHP to display errors in the output. Various methods depending upon your server setup. eZ facility for switching debug output off/on (after successful installation) is /settings/override/site.ini.append.php
[DebugSettings] DebugOutput=disabled Change to..
[DebugSettings] DebugOutput=enabled Of course, many levels of debug available in admin after eZ is working. A pure guess for your specific problem, a permissions problem on a file that index.php is trying to load. But rather than guessing, go straight to definitive troubleshooting using the provided facilities. Hope this helps and saves time and troubles for you and others. Cheers!
Doug Brethower
Apple Certified Technical Consultant, Southwest, MO USA
http://share.ez.no/directory/companies/lakedata.net
|