ExpressionEngine CMS
Open, Free, Amazing

Thread

This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.

The active forums are here.

Upgrade Apache/PHP index.php fail

May 27, 2010 8:37pm

Subscribe [6]
  • #1 / May 27, 2010 8:37pm

    We recently upgraded to PHP 5.3.2 and Apache 2.2.15 and since then have not been able to get EE working properly. When going to the admin or other portion it seems to have an issue with redirecting and trying to download the index.php as a file?

    PHP is working any other .php page in the directory works, index.php is set as default page as well. This is with EE version 1.6.8 and 1.6.9.

  • #2 / May 27, 2010 10:35pm

    Brandon Jones

    5500 posts

    Hi, and welcome to the forums!

    I’m running on PHP 5.3, but on Apache 2.0. Still, plenty seem to be using Apache 2.2 without these sorts of issues.

    Sometimes Apache upgrades can require changes to an .htaccess file - do you have one of these? Try removing it and setting index.php back as your index page. Let us know if there’s any improvement with .htaccess out of the equation.

  • #3 / May 28, 2010 2:01pm

    Unfortunately no .htaccess and I even tried to re-install. The installation gets up to the fourth step and all of a sudden wants to download the install.php after having just been using it for the previous 3 steps.

  • #4 / May 28, 2010 3:26pm

    Sue Crocker

    26054 posts

    How much memory does PHP have allocated to it?

  • #5 / May 28, 2010 4:15pm

    Our php.ini has

    memory_limit = 16M

  • #6 / May 28, 2010 4:17pm

    Sue Crocker

    26054 posts

    16M is not a lot.. I’d tend to recommend 64M. That’s what EngineHosting uses. Can you up that and try again?

  • #7 / May 31, 2010 2:18pm

    I boosted the memory to 32MB the same as other systems and it still does this. The server can read PHP fine, as it can get to page=4. So it gets to the point of pressing “Click here to install ExpressionEngine” and THEN it tries to download install.php.

  • #8 / May 31, 2010 5:32pm

    Ingmar

    29245 posts

    Is that a public site? Do you’ve got a link? I am afraid everything points to a problem with your PHP setup, not an EE issue.

  • #9 / May 31, 2010 5:41pm

    It is unfortunately not a public site but one that is being developed internally. Are there any specific modules that PHP requires aside from the basic XML, etc? The server itself can read right up to page=4 and then whatever function it is trying to do fails at that point.

  • #10 / May 31, 2010 7:47pm

    Just to confirm that

    PHP 5.3.2 and Apache 2.2.15 are compatible with version 1.6.9?

  • #11 / May 31, 2010 8:15pm

    Sue Crocker

    26054 posts

    Yes,  you shouldn’t have any issues. The real issue here is that you should try upping your PHP memory to 64M.

  • #12 / May 31, 2010 8:23pm

    The PHP memory has been increased to 64MB with no effect to the issue. On Firefox it attempts to download install.php after page4 and on other browsers it simply states it cannot display the page.

  • #13 / May 31, 2010 9:03pm

    Sue Crocker

    26054 posts

    Have you seen this wiki entry:

    http://expressionengine.com/wiki/HowTo_Turn_on_Error_Reporting/

    With error reporting turned on, do you get any sort of error messages?

  • #14 / Jun 22, 2010 6:30pm

    Have you seen this wiki entry:

    http://expressionengine.com/wiki/HowTo_Turn_on_Error_Reporting/

    With error reporting turned on, do you get any sort of error messages?

    So far error reporting has not indicated the cause of the problem. Have you encountered before any issues where upon going to stage 5 is causes a segmentation fault in Apache? Basically we discovered it, from page 4 to page 5 in install.php it causes all of the children in Apache to fault and therefore no information comes through.

    We have attempted to install a few other CMS packages, all of which seem to be able to completely install on the same platform.

    Update:

    We believe it is not giving us errors as it is faulting before it can write them.

  • #15 / Jun 22, 2010 8:07pm

    Brandon Jones

    5500 posts

    Have you encountered before any issues where upon going to stage 5 is causes a segmentation fault in Apache?

    No, a script should never be able to crash the server. Unfortunately that’s a software issue on the server. Perhaps some other module isn’t quite compatible with the latest Apache release? Please let us know what you find.

.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases