WordPress.org

Ready to get started?Download WordPress

Forums

Experiencing random "Internal server Errors" (Update WP 2.9) (26 posts)

  1. deus62
    Member
    Posted 4 years ago #

    Hi everyone,

    just a quick question if anyone else is experiencing the same problem.

    Update to latest WP version (2.9) went smoothly and my site seems to run without a problem.

    But ...

    When I try to edit a longer post, I get completely irregular "Internal server Errors". I've had 6 of these in the last two hours. Sometimes edits work fine ... but take a long time to be saved to the server).

    Now I'm wondering if ...

    a) it's my host (has been stable for years without a single server error for about 8 or 9 years!)

    b) or if sth changed with WP 2.9 (f.ex. longer runtime for scripts or sth like that) that could cause this error.

    Again, I've never had this problem before.

    Any comment or help is appreciated.

    deus62

    P.S.: The post in question is this one (editing works 50% of the time ... for the rest I get server errors):

    http://livingwithmusic.com/mosaic/

  2. Andrej Mihajlov
    Member
    Posted 4 years ago #

    What's inside errors_log of apache?

  3. deus62
    Member
    Posted 4 years ago #

    I do not have access to error logs. I think.

  4. deus62
    Member
    Posted 4 years ago #

    If anyone else reads this, has script time in WP 2.9 increased (substantially)?

    I have the feeling that's my problem. I'm on manged hosting that sets script run-time limits for the various accounts.

    Unfortunately, I don't have access to error logs (only to FTP and access logs).

  5. deus62
    Member
    Posted 4 years ago #

    Yep.
    Looks like the WP update pushed me above script limits.
    Bummer.
    :/

  6. Denis de Bernardy
    Member
    Posted 4 years ago #

  7. deus62
    Member
    Posted 4 years ago #

    OK, but if it sometimes works and sometimes doesn't, file permissions can't really be the culprits, can they?

  8. Andrej Mihajlov
    Member
    Posted 4 years ago #

    You shoudn't get 500 error if you have not enough memory, usually php shows error like 'tried to allocate ... memory exhausted ...' on most mod_php web hostings. But it can be 500 error on some fast-cgi/cgi web hostings with memory limit per user account in OS. Depends on how web server is configured.

    If your web hosting is mod_php based and you got 500 error so u should contact your web hosting provider about a problem. For example, I've got a same problem when used a web hosting with IIS + php configured and the problem was solved with a php downgrade.

  9. Jimi Wikman
    Member
    Posted 4 years ago #

    I am having the same issue.

    Error logs state:
    [Sat Dec 19 20:54:43 2009] [error] [client xxx] Premature end of script headers: post.php, referer: http://www.mortfiles.se/xxx/wp-admin/post-new.php
    [Sat Dec 19 20:54:43 2009] [error] [client xxx] File does not exist: /home/mfse01/public_html/500.shtml, referer: http://www.mortfiles.se/xxx/wp-admin/post-new.php
    [Sat Dec 19 20:54:53 2009] [warn] mod_fcgid: process 19804 graceful kill fail, sending SIGKILL

    [Sat Dec 19 20:57:52 2009] [error] [client xxx] Premature end of script headers: post.php, referer: http://www.mortfiles.se/xxx/wp-admin/post-new.php
    [Sat Dec 19 20:57:52 2009] [error] [client xxx] File does not exist: /home/mfse01/public_html/500.shtml, referer: http://www.mortfiles.se/xxx/wp-admin/post-new.php
    [Sat Dec 19 20:57:59 2009] [warn] mod_fcgid: process 21878 graceful kill fail, sending SIGKILL

  10. Andrew Ozz
    WordPress Dev
    Posted 4 years ago #

    You'll probably need to contact your host's support. Unfortunately the "Premature end of script headers" error message only means "something didn't work...". It can be caused by a number of things: too large error logs, a kill script that quits a process when it uses more than a certain amount of memory or CPU, routing problems, high packet loss, etc.

  11. Jimi Wikman
    Member
    Posted 4 years ago #

    To large error logs, CPU and memory I can rule out since I am the host :)
    Routing problem seems unlikely and package loss would effect other services as well.

    It's only the post.php file that is causing this problem as far as i have seen. All else seem to work just fine.

    Whats confusing is that it works sometimes and sometimes not, even when dealing with the same post. If I make a preview I always have to refresh and then it shows the page. When making new posts or updating posts it seems more random.

  12. dragonintuitive
    Member
    Posted 4 years ago #

    Horrible page load times when I'm trying to edit/publish a post or page! Often getting 505 error or Mysql server has gone away. It's making 2.9 unusable.

  13. wardrox
    Member
    Posted 4 years ago #

    I'm also finding similar problems. Often getting 500 Internal Server Errors as well as very, very long save times.

  14. wardrox
    Member
    Posted 4 years ago #

    Looks like everything saves fine, it just doesn't update the writer informing them and just hangs. I suggest to people struggling with slow saves simply refreshing the page and seeing if the edits, counter to what WP is saying, has been saved.

  15. Jimi Wikman
    Member
    Posted 4 years ago #

    It does post, I posted 2 posts even though the post.pm showed a Internal Server Error when posting.

  16. wardrox
    Member
    Posted 4 years ago #

    I just upgraded to the newest version of YARPP (Yet Another Related Posts Plugin) and I think it's solved the problem for me.

    According to the YARPP twitter, there was a time-out bug that's been fixed with the new version (3.1.2)

  17. dragonintuitive
    Member
    Posted 4 years ago #

    Yes, Response time is back to it's old self with the new version of YARPP.

  18. Andrej Mihajlov
    Member
    Posted 4 years ago #

    unclosed php tag ('?>') in the end of 'wp-admin/admin-header.php' (http://core.trac.wordpress.org/browser/trunk/wp-admin/admin-header.php#L128) can cause same error.

  19. Hendison Scott
    Member
    Posted 4 years ago #

    I'm seeing the exact same issue - "Premature end of script headers: post.php" and it's totally intermittent - I think it's not a webhost problem, it's a WP 2.9 problem.

  20. ALJ
    Member
    Posted 4 years ago #

    Sorry to not bring a solution, but I wanted to weigh in that I'm seeing the same problem.

    The "Internal Server Error" only happens on the live WP site (running 2.9), not my local development machine. It's also rare and intermittent. It sometimes happens when posting, maybe about one in 10 posts.

    I've also seen it happen once or twice as an external user just browsing blog posts, which is a bit scary.

    -ALJ

  21. documaker
    Member
    Posted 4 years ago #

    I'm having the same problem when trying to post.

  22. documaker
    Member
    Posted 4 years ago #

    Also wanted to note that I'm using wordpress 2.9. Posts over 152 word count causes problems for me.

  23. RoyV
    Member
    Posted 4 years ago #

    Same here. Experiencing intermittent Internal Server errors

  24. documaker
    Member
    Posted 4 years ago #

    Just want to suggest a work around for anyone still stuck with this problem. Using the Windows Live Writer program will bypass this error no matter what the post size.

  25. Luke Gedeon
    Member
    Posted 3 years ago #

    Wow! This is a lot of people with the same problem for a long time and no solution. I have been having this problem for about two weeks.

    Documaker's solution would only affect errors during posting. I am getting these all over the place - both admin and reader sides.

    Is there a ticket for this?

  26. James
    Happiness Engineer
    Posted 3 years ago #

    Internal server errors can happen for a variety of reasons and are usually described in detail in the server error log.

    If you have access to your server error log, generate the error again, note the date and time, and immediately check the server error log for anything useful.

    If you don't have access to your server error log, ask your hosting provider to look for you.

Topic Closed

This topic has been closed to new replies.

About this Topic