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.

"Premature end of script headers" error while upgrading from EE v.1.7.0 to v2.1.3

December 25, 2010 1:30pm

Subscribe [3]
  • #1 / Dec 25, 2010 1:30pm

    Laisvunas

    879 posts

    Hi,

    I tried to upgrade from EE v.1.7.0 to v2.1.3 on virtual private server.

    Upgrade script failed to finish leaving me with error 500:

    500 Internal Server Error

    Internal Server Error

    The server encountered an internal error or misconfiguration and was unable to complete your request.

    Please contact the server administrator, .(JavaScript must be enabled to view this email address) and inform them of the time the error occurred, and anything you might have done that may have caused the error.

    More information about this error may be available in the server error log.

    Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.

    I asked the host about this error, and it is their answer:

    I can recreate the error from my end. From the logs I can see the issue is due to script.
    —————
    [Sat Dec 25 12:51:06 2010] [error] [client 122.167.248.88] Premature end of script headers: index.php, referer: http://rrrrrrrrrrrr.com/system/index.php?C=wizard&M=do_update&agree=yes&language=english&ajax_progress=yes
    [Sat Dec 25 12:56:06 2010] [error] [client 122.167.248.88] File does not exist: /home/classic1/public_html/500.shtml, referer: http://rrrrrrrrrrrr.com/system/index.php?C=wizard&M=do_update&agree=yes&language=english&ajax_progress=yes

    What should be done in the situation when upgrade script fails levving you with “Premature end of script headers”. It does not seem to be memory issue because I allocated memory_limit 400M (!) though php.ini

  • #2 / Dec 25, 2010 4:02pm

    handyman

    509 posts

    Not sure if I can be of any help, but that is a very general message!

    Some possible causes are an improperly set .htaccess or httpd.conf file or a script gone bad….almost any script!

    What is that file, 500.shtml, that this looks for…...???
    Perhaps it is part of an add-on?
    You might want to strip out all of your extensions and plug-ins and mods before running the script again…....

  • #3 / Dec 27, 2010 3:55pm

    Ingmar

    29245 posts

    Adding to what handyman said, can we rule out server side issues such as mod_security? Are you using any extensions?

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

ExpressionEngine News!

#eecms, #events, #releases