Premature end of script headers upon install of 2.3

  • I just upgraded to 2.3 on two blogs. Immediately, both started showing “Premature end of script headers” on their index pages in the error log. This is a real problem on one blog, because it’s also is generating huge “core dump” files I have to delete every few hours to avoid running out of disk space.

    I’ve upgraded all my plugins and removed any that were on the incompatible list. I deactivated a few plugins that supposedly ARE compatible (or don’t appear on either list as compatible or incompatible) such as WP-cache, Google Sitemaps 3.0, and Ajax Edit Comments 1.1.1.2. This has reduced the number of errors, but not fixed it.

    Any suggestions would be appreciated. My permissions settings (which are the same as they were on 2.2) are 755 for folders and 644 or 755 for files.

Viewing 7 replies - 1 through 7 (of 7 total)
  • Thread Starter Sapphire

    (@sapphire)

    Okay, now I just got some core dumps without getting any premature end of script headers errors at the same time, so I’m not positive they’re connected.

    Thread Starter Sapphire

    (@sapphire)

    The core dumps are not related (or if they are, they’re still irrelevant since that’s a host problem, and I’m now moving hosts before anything more strange happens).

    But the premature end of script headers is definitely a WordPress issue. Is there a place where I should submit a bug report or something?

    Anything in the web server error logs?

    For testing purposes, I’d also suggest switching to the Default theme and disabling all plugins. Does it work then?

    Thread Starter Sapphire

    (@sapphire)

    At first the error logs I can see through cpanel (if that’s what you mean?) only list “premature end of script headers” on the home page over and over, sometimes several per minute. Later they started showing errors on wp-comment-post.php, too. And wp-post.php.

    I ended up moving one of the blogs to a new host this morning because of a growing sense that the old host doesn’t configure their server as well as they could. So far there are no errors on the new host, but it’s only been an hour since it resolved on my IP, so I’m still watching. (The other host where I upgraded is still reporting the same “premature…” errors.)

    As for testing… everything IS working, so it’s not like switching themes or deactivating plugins tells me anything. I’ve tried both of those things, and sometimes there wouldn’t be an error for a while, but within a couple of hours it would start again.

    Thread Starter Sapphire

    (@sapphire)

    Okay, these errors stopped happening on both sites as soon as I upgraded to the new versions of the Lester Chan plugins I use. I’m not sure which plugin (or all?) were conflicting with the new WP – I was using WP-Print and WP-email on both sites (as well as WP-DBManager and WP-PageNavi on another).

    So I guess it was those two plugins causing the trouble, and now they’ve been updated to work with WP 2.3.

    We had this issue on one server, it disappeared after we switched Zend compatibility mode off in php.ini:

    zend.ze1_compatibility_mode = Off

    I am using pretty much the same plug ins and I am getting the same 500 errors:
    The results:

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

    Please contact the server administrator, [email protected] 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.

    And the cpanel error log:
    [Sun Mar 16 18:45:09 2008] [error] [client 190.64.62.151] File does not exist: /home/xxx/public_html/xxxx/500.shtml
    [Sun Mar 16 18:45:09 2008] [error] [client xxx.64.62.151] Premature end of script headers: /home/xxx/public_html/xxxx/index.php
    [Sun Mar 16 18:45:04 2008] [error] [client xxx.64.62.151] File does not exist: /home/xxx/public_html/xxx/500.shtml
    [Sun Mar 16 18:45:04 2008] [error] [client xxx.64.62.151] Premature end of script headers: /home/xxx/public_html/xxx/index.php
    Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.
    Apache/1.3.39 Server at xxx.info Port 80

    I’m really stuck on this one, all I know is that my .php sites (WP) are down, hard.

    Any suggestions?

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Premature end of script headers upon install of 2.3’ is closed to new replies.