• My site was running just fine up until about half an hour ago when I attempted to access my index page and I am now getting 500 Internal Server Errors. I checked my error logs and I am getting the following error message:

    Premature end of script headers: /home/xxxx/public_html/index.php

    I am able to login to WP and move around within it, but I just can’t get my index.php page to load. I have contacted my host (Jaguar PC) but haven’t heard back yet. I did notice that they upgraded their system and Cpanel so I’m not sure if something on this end is causing the problem or if my WP just pooped out on me.

    Any suggestions?

Viewing 4 replies - 16 through 19 (of 19 total)
  • Well, we’ve seen plugins cause errors due to hitting memory constraints. Typically (ime) that is usually fixed by adjusting PHP’s max mem setting upwards. (default is often 8MB)

    RLimitMEM is a new one on me…, but I’m apache’tarded.

    I’ve got similar problem (I didn’t noticed it in WP < 2.1).
    Some browsers (FF under Win, links, konqueror) showed me 500, the apache log showed:
    Premature end of script headers.

    The error showed only when I was accessing the post perm link.
    Main page and the list of posts was ok.

    I’ve commented out gzip_compression() in wp-blog-header.php and it works now. A bug?

    I’m using su_php, mod_rewrite.

    Regards,
    Piotr Budny

    I’m having same issue with my server. I read other threads but changing file permission to 755 did not work for me. Also playing with memory should not be an option since nothing was changed (code and configuration) on server. Weird thing is; this started happening all of sudden and absolutely nothing was changed on server as far as configuration goes. Another weird thing is; this error shows up on couple of scripts not all site. The third weird thing is that two scripts are nearly exactly the same and while one works one, the other doesn’t. When I run scripts through shell, I got this error;
    *** glibc detected *** malloc(): memory corruption: 0x0a21a3c0 ***

    Any suggestion really appreciated.

    I too recently started having this problem. I’ve contacted my host to see if it is fact a memory limit problem. If so, I’ll remove some of my plugins and see if that solves the problem.

Viewing 4 replies - 16 through 19 (of 19 total)
  • The topic ‘Premature end of script headers: index.php’ is closed to new replies.