• Resolved KirkM

    (@kirkm)


    Hi all,

    I’m seeing a rather strange set of SQL errors cropping up every time I publish or edit a post using Windows Live Writer 2008. I believe these errors began when I updated to WordPress version 2.3.2 and I still get them since updating to 2.3.3. These are the errors that show up in my root directory error log. It’s the same set each time I publish or edit:

    [16-Feb-2008 11:26:51] WordPress database error MySQL server has gone away for query SELECT * FROM wp_posts, wp_postmeta WHERE wp_posts.ID = wp_postmeta.post_id AND wp_postmeta.meta_key = ‘_pingme’ LIMIT 1

    [16-Feb-2008 11:26:51] WordPress database error MySQL server has gone away for query SELECT * FROM wp_posts, wp_postmeta WHERE wp_posts.ID = wp_postmeta.post_id AND wp_postmeta.meta_key = ‘_encloseme’ LIMIT 1

    [16-Feb-2008 11:26:51] WordPress database error MySQL server has gone away for query SELECT ID FROM wp_posts WHERE CHAR_LENGTH(TRIM(to_ping)) > 7 AND post_status = ‘publish’

    [16-Feb-2008 11:26:51] WordPress database error MySQL server has gone away for query UPDATE wp_options SET option_value = ‘0’ WHERE option_name = ‘doing_cron’

    The kicker is that Windows Live Writer publishes with no problem at all and the posts show up just fine like they always have and I never would have noticed these errors if I wasn’t in the habit of checking my error logs on a regular basis.

    Currently I have pinging turned off in both my admin and Windows Live Writer but that hasn’t made any difference and so far deactivating various plugins hasn’t made a difference either. Considering that I was running the same group of plugins before this problem arose it seems rather doubtful that it’s a plugin related problem.

    Unfortunately I’m SQL light and admittedly don’t have a clue of where to go with this. I’ve already talked with Joe Cheng (WLW developer) about the problem and this is the first time he’s heard of it and recommended posting here. Any help would be thankfully appreciated.

    Running:

    Windows Live Writer: Publishing in XHTML

    PHP: 5.2.5

    MySQL: 5.0.45

Viewing 4 replies - 1 through 4 (of 4 total)
  • Kafkaesqui

    (@kafkaesqui)

    Possible solution?

    https://robsnotebook.com/wordpress-mysql-gone-away

    Note: For MySQL errors, always good to search Google or your favorite search engine with the error you’re getting — in this case, “MySQL server has gone away” — and “WordPress” as your search terms. If that fails to turn up anything, just searching on the error will often lead to a resolution.

    Thread Starter KirkM

    (@kirkm)

    Thanks Kafkaesqui! Looks like this is the answer. And me being someone who Googles just about everything like this didn’t even think about it this time around. Go figure. I’ll try it out in the morning.

    Perhaps this is also the reason for the 2.3.2 disappearing posts that some folks are having.

    Thanks again and I’ll post back on the results.

    Still no solutions?

    [crossposted to several threads]

    If you are recieving the “WordPress database error MySQL server has gone away” error in your logs and you have access to your mysql configuration you may want to look through this page from the mysql documentation. It details what the generic error means and how to try to fix it at the Mysql server level:

    https://dev.mysql.com/doc/refman/5.0/en/gone-away.html

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘SQL Errors publishing with Windows Live Writer’ is closed to new replies.