• So, I am a bit stumped. I am trying to just get this site functional and hit a wall. So the errors I am getting are a couple and they vary. To sum easily: I get a 500 internal server error when anyone updates a post.

    [Wed Mar 19 16:36:54 2014] [warn] [client 10.180.11.135] mod_fcgid: read data timeout in 45 seconds, referer: http://www.movieguide.org/wp-admin/post.php?post=484557&action=edit
    [Wed Mar 19 16:36:54 2014] [error] [client 10.180.11.135] Premature end of script headers: post.php, referer: http://www.movieguide.org/wp-admin/post.php?post=484557&action=edit

    And

    mod_fcgid: stderr: WordPress database error You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ‘LIMIT 1’ at line 1 for query SELECT meta_value FROM wp_postmeta WHERE meta_key = ‘_wp_attached_file’ AND post_id = LIMIT 1 made by require(‘wp-blog-header.php’), require_once(‘wp-includes/template-loader.php’), include(‘/themes/movieguide/single.php’), include(‘/themes/movieguide/single-reviews.php’), W3_Db->query, W3_DbCache->query, W3_DbCallUnderlying->query, W3_Db->query, W3_DbProcessor->query, W3_Db->default_query`
    `
    The problems arise anytime someone is logged in and they try to edit and update a page. The backend is also rather slow. I have also been looking at a ton of the suggestiosn on other threads but they havent seemed to work. Upping the define( ‘WP_MEMORY_LIMIT’, ’64M’ );

    Im just not even sure where to look anymore. Any insight would b fantastic and much appreciated.

    The site is movieguide.org

Viewing 2 replies - 1 through 2 (of 2 total)
  • What happens if you turn off W3 Total Cache. Speaking of which, do you realise you’ve got its debug option turned on? There’s a whole raft of stuff spat out at the end of your page if you view the source.

    Maybe try turning debug off and see if things improve?

    Thread Starter maxwellmovieguide

    (@maxwellmovieguide)

    Things improved but overall it still occurs. Now posts will be able to edit and update without crashing but its still takes about 25-30 seconds for it to save. Feel like that might be too long.

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Internal 500 post.php Error (Read data timeout)’ is closed to new replies.