Support » Fixing WordPress » WordPress database error

  • Resolved skarld

    (@skarld)


    Last weekend my host (1and1), upgraded their servers and broke my site.

    When I made a new post, or if I tried to delete a post or draft, I got the following error statement:

    WordPress database error: [MySQL client ran out of memory]
    SELECT * FROM wp_jb_posts WHERE ID = ‘204’ LIMIT 1

    WordPress database error: [Lost connection to MySQL server during query]
    SELECT * FROM wp_jb_posts WHERE ID = ‘205’ LIMIT 1

    WordPress database error: [MySQL server has gone away]
    SELECT * FROM wp_jb_posts WHERE ID = ’76’ LIMIT 1

    WordPress database error: [MySQL server has gone away]
    SELECT * FROM wp_jb_posts WHERE ID = ’92’ LIMIT 1

    I have two blogs with the same host running version 2.0.11. The big one broke (over 2,000 posts), the small one did not.

    I tried the solution offered at these two sites:
    http://www.openadvent.com/blog/?p=30 and
    http://robsnotebook.com/wordpress-mysql-gone-away#comment-8411
    but it did not work on the big site.

    My host suggested PHP5. Stating the following:

    Try switching to PHP5. Scripts parsed in PHP4
    use more memory than PHP5 in our systems. You can switch to PHP5 by
    adding line below in your .htaccess file:

    AddType x-mapp-php5 .php

    ….and IT WORKED!

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

    (@ianternet)

    I get this after the maintenance:

    MySQL server has gone away on line

    and I still get it after a post – and I checked my htaccess it is already there

    I executed the fix recommended above in the robsnotebook.com link.
    The WordPress database error: [MySQL client ran out of memory] did not go away….

    Because I had been updating plugins minutes before this error occurred, I started to de-activate the plugins one by one.
    The first plugin I de-activated was WP Super Cache 0.9
    The database error vanished immediately and my dashboard returned to normal.

    Someone smarter than me will immediately see the significance of that plugin and its expected, normal behaviour, and how that behaviour might mess with the database.

    I’m glad that I dumbly blundered into my solution so quickly.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘WordPress database error’ is closed to new replies.