Support » Alpha/Beta/RC » Errors when updating posts with comments in 2.7 RC1

  • jayp

    (@jayp)


    I had commented earlier in a thread about the beta version of 2.7, but I thought it might be best to start a new thread about this issue.

    When I edit posts and try to update them, I’m getting an error message that reads:

    WordPress database error: [MySQL server has gone away]
    SELECT comment_approved, COUNT( * ) AS num_comments FROM wp_comments GROUP BY comment_approved

    WordPress database error: [MySQL server has gone away]
    SELECT * FROM wp_posts WHERE ID = 361 LIMIT 1

    You attempted to edit a post that doesn’t exist. Perhaps it was deleted?

    The update actually works and the page is successfully saved, but it’s a pretty jarring experience and you can have to close the browser window or directly type in a URL to get back to your blog.

    Also, I just realized that this problem appears to only happen for those posts that have comments. Uncommented posts appear to be saving without incident for me.

    Otherwise, 2.7 looks wonderful. A huge improvement from 2.5 and 2.6.

Viewing 7 replies - 1 through 7 (of 7 total)
  • jayp

    (@jayp)

    Hmmmm. I spoke too soon? For the first time, I’ve updated a post that had comments, so I’m not sure if what I wrote above applies. Previously, I was getting the above error consistently, and I never saw any kind of a database error while browsing the site or working in the admin area. (Thus I didn’t think it was a problem with my database or server configuration…)

    I won’t post more unless I really think I’ve learn something. But the error might be worth looking into before the release of 2.7.

    jayp

    (@jayp)

    I’m still having these problems, though I don’t know how to reliably reproduce them. It just seems to randomly give the error when updating some pages.

    Moderator Samuel Wood (Otto)

    (@otto42)

    WordPress.org Admin

    “MySQL server has gone away” is a generic error indicating that something is wrong with your database server. Google for it, or talk to your web host about the problem.

    WordPress can demonstrate a lot of weird behavior when the database is randomly dropping connections.

    jayp

    (@jayp)

    @otto42, it’s not a database problem.

    How do I know?

    1) The page updates successfully and updates are written to the DB but I see this error message… (It’s never failed to successfully write to the DB.)

    2) I’ve been using worpdress since version 1.5 and have never seen this error message. Ever. I manage my own VPS and WordPress and lots of other apps that use MySQL haven’t had a single glitch, until WP RC1.

    3) Others are reporting exactly the same behavior for the Beta and RC1.
    http://wordpress.org/support/topic/216203?replies=11

    Moderator Samuel Wood (Otto)

    (@otto42)

    WordPress.org Admin

    @otto42, it’s not a database problem.

    I’m sorry, but you are incorrect. You can make numerical lists all day long, but “MySQL server has gone away” is a database problem. Period.

    Really. I’m not making things up here just to mess with your head or something.

    Could be one of any number of things. Could be bad settings on your database, like connection timeouts set too low. But whatever it is, the problem is in the database. I don’t care what it did before, that error message cannot occur from any other issue except the database disconnecting from the PHP process.

    jayp

    (@jayp)

    Ok. I’m more than willing to accept that I miss things or make mistakes.

    But you still haven’t answered why no other application I’ve ever run (including WordPress from version 1.5 and onwards) has ever given me any trouble.

    And you’ve apparently ignored the fact that the updates are always saved to the database. In other words, the error appears but WordPress is obviously writing to the database without fail… I also don’t see these errors when doing anything else with WP. Logging in, posting, editing categories, comments, plugins, page views. Every other thing I do which hits the database, doesn’t show this message. It’s only updating pages where I’ve seen the message.

    And you’ve also ignored the link I provided above, where 11 comments are given regarding the same behavior, noticed in the 2.7 beta.

    I’m not an idiot Otto. Neither are lots of others who come to these forums. (Some are, but that’s besides the point.) It would be nice if you wouldn’t treat people as such.

    So if this is truly a database problem, where the connection is getting dropped, it would seem that it’s still a problem in WP that’s dropping the connection. Perhaps after writing to the DB it’s trying to do something that’s taking too long? I know at times the admin interface has seemed sluggish, as others have reported for 2.7 betas and RC1.

    Bottom line. I’m willing to be corrected, and I’m certainly capable of being wrong. But until you address my points and give me specific suggestions, you’re just wasting everyone’s time.

    Moderator Samuel Wood (Otto)

    (@otto42)

    WordPress.org Admin

    But you still haven’t answered why no other application I’ve ever run (including WordPress from version 1.5 and onwards) has ever given me any trouble.


    Are you serious? So, because it works for one thing, it must work for everything? Do you think that one database server could run the entirety of the internet?

    Different applications have different needs. I don’t know what threshold you hit, but you hit one. Perhaps your traffic has increased. Perhaps the extra queries in 2.7 take a bit longer. Perhaps your database is filling up its space and needs to be optimized. I don’t know, nor do I have any way to know. It’s your site, it’s your database. All I can do is give you advice and words, you still have to solve the issue.

    And you’ve apparently ignored the fact that the updates are always saved to the database. In other words, the error appears but WordPress is obviously writing to the database without fail…

    Yes, I’m ignoring that because it’s irrelevant. WordPress executes more than one query per page load. It’s entirely possible for the UPDATE query to occur and then some other query, later, to fail because the database server has disconnected. A page load is not an atomic operation.

    So if this is truly a database problem, where the connection is getting dropped, it would seem that it’s still a problem in WP that’s dropping the connection.

    PHP and MySQL simply does not work that way. No database works that way, in point of fact. And the “MySQL Server has gone away” is a dropped connection that occurred on the database side of things. There is no other explanation possible.

    Perhaps after writing to the DB it’s trying to do something that’s taking too long?

    This is entirely possible. However, it’s still a database problem. If you need the connection to wait a while and the connection timeout in MySQL is set too low, then the database needs to be adjusted to wait longer.

    Alternatively, if you need the PHP code to run faster, then you need to throw more horsepower/CPU at it.

    I know at times the admin interface has seemed sluggish, as others have reported for 2.7 betas and RC1.

    WordPress 2.7 is actually measurably faster in this respect, however, it does perform more queries to the database. So a slow database server or one with not enough memory allocated to it might be the issue here.

    I’m not an idiot Otto.

    Honestly, I would not make that assumption if I were you. You’re certainly displaying all the signs. Insulting people who are trying to help you, for example.

    Bottom line. I’m willing to be corrected, and I’m certainly capable of being wrong. But until you address my points and give me specific suggestions, you’re just wasting everyone’s time.

    And you’re wasting mine and everybody else’s on this forums by ignoring advice and suggestions from people trying to assist you.

    Bottom line: This thread is closed because you can’t seem to take advice gracefully. If you feel like not being a complete jerk to people who are really trying to assist you, then feel free to post again. But if you want to continue to act like you’re doing here, then I would suggest not bothering.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Errors when updating posts with comments in 2.7 RC1’ is closed to new replies.