WordPress.org

Support

Support » How-To and Troubleshooting » GoDaddy and INSERT INTO wp_postmeta issues

GoDaddy and INSERT INTO wp_postmeta issues

Viewing 15 replies - 1 through 15 (of 20 total)
  • Hello,
    I’m getting errors similiar to yours when I edit existing posts now that I have upgraded to 2.0.1 from 2.0.0

    WordPress database error: [Lost connection to MySQL server during query]
    INSERT INTO wp_postmeta (post_id,meta_key,meta_value) VALUES (’12’,’_pingme’,’1′)

    Warning: Cannot modify header information – headers already sent by (output started at /home/content/E/5/a/login name/html/journal/wp-includes/wp-db.php:102) in /home/content/E/5/a/login name/html/journal/wp-admin/post.php on line 122

    Like yours it only affects the old posts and I’m also on a godaddy server.

    Thanks,
    Erik

    I have NO idea what has changed. Editing existing posts seems to work. However I get this now…

    Warning: preg_match(): No ending delimiter ‘!’ found in /home/content/s/h/y/shystie/html/wp/wp-includes/classes.php on line 1542

    Warning: preg_match(): No ending delimiter ‘!’ found in /home/content/s/h/y/shystie/html/wp/wp-includes/classes.php on line 1543

    Warning: preg_match(): No ending delimiter ‘!’ found in /home/content/s/h/y/shystie/html/wp/wp-includes/classes.php on line 1542

    Warning: preg_match(): No ending delimiter ‘!’ found in /home/content/s/h/y/shystie/html/wp/wp-includes/classes.php on line 1543

    Warning: preg_match(): No ending delimiter ‘!’ found in /home/content/s/h/y/shystie/html/wp/wp-includes/classes.php on line 1542

    Warning: preg_match(): No ending delimiter ‘!’ found in /home/content/s/h/y/shystie/html/wp/wp-includes/classes.php on line 1543

    Warning: preg_match(): No ending delimiter ‘!’ found in /home/content/s/h/y/shystie/html/wp/wp-includes/classes.php on line 1542

    Warning: preg_match(): No ending delimiter ‘!’ found in /home/content/s/h/y/shystie/html/wp/wp-includes/classes.php on line 1543

    If I edit these lines and change the ” to ‘ the error goes away, but the url’s don’t work anymore 🙁

    Getting frustrated and needing help,
    Shoshanna

    I’m having the exact same problem Mischievous and j9bluenile. I’m also on a GoDaddy server.

    The only difference, is that I’m getting the error message at random (it seems like it) and it’s affecting new posts as well as old ones.

    The error doesn’t seem to interfere with the editing/publising process… but getting this error message can’t be a good thing.

    Help???

    I have the same problem!

    I get the following when saving posts (writing new as well as editing existing ones):

    WordPress database error: [Lost connection to MySQL server during query]
    INSERT INTO wp_postmeta (post_id,meta_key,meta_value) VALUES ('44','_pingme','1')

    Everything seems to work (i.e. the posts get saved properly), but something must be missing somewhere.

    [edit: I found this thread with Google, I did not know it was related to GoDaddy (whatever that is), which I am not using…]

    I’m joining the club. I’m not using GoDaddy but anyway I see teh same problem as mookid and others:

    WordPress database error: [Lost connection to MySQL server during query]
    INSERT INTO wp_postmeta (post_id,meta_key,meta_value) VALUES (‘5′,’_pingme’,’1′)

    Warning: Cannot modify header information – headers already sent by (output started at /usr/home/web/databasemane/wordpress/wp-includes/wp-db.php:102) in /usr/home/web/databasemane/wordpress/wp-admin/post.php
    on line 122

    The post are saved but this odd behaviour is no good news for a newbee in WordPress.

    klix

    I’ve posted this to the hackers mailing list, see if we can get a response.

    Note that it’s the INSERT failure that’s the problem — the errors after that are >because< the failure printed something out ‘too early’, before the page headers start.

    I’m getting a similar message when I save posts on a new 2.01 install:

    WordPress database error: [Lost connection to MySQL server during query]
    INSERT INTO wp_postmeta (post_id,meta_key,meta_value) VALUES (’20’,’_pingme’,’1′)

    Add me to the list of people seeing this error on 2.01 hosted with GoDaddy. It appears after I hit “Publish”, but the post is still published and the pings are still sent.

    Mine isn’t hosted by godaddy, but fatcow.

    I moved the site to another host and still had the same error (the second Warning: preg_match(): error) Starting fresh fixed it! I think it would have also been fine on GoDaddy as well. But this is a better hosting package anyway so I am still glad it’s moved…

    I wonder what causes the error when you move an instillation (following the directions on the Wiki)compared to starting fresh…

    Yet another person with the same problem. Just updated to 2.0.1 and get this error when I publish a new post. Hosted by GoDaddy. Post seems to get to the web site. Pretty annoying. Guess I will go back to 2.0 until fixed.

    WordPress database error: [Lost connection to MySQL server during query]
    INSERT INTO wp_postmeta (post_id,meta_key,meta_value) VALUES (’31’,’_pingme’,’1′)

    Warning: Cannot modify header information – headers already sent by (output started at /home/content/j/l/t/jltomcat/html/wp-includes/wp-db.php:102) in /home/content/j/l/t/jltomcat/html/wp-admin/post.php on line 59

    it doesnt look like its just a godaddy issue, im having the same problem on several different hosts.

    me to. we have dozens of wordpress blogs in production. most of our 2.0.1 blogs are fine but some show the same error occasionally. and one gives almost always this error.

    we tried everything from disabling pinging to removing references to the old host in the database but nothing helps.

    is their a tool that ‘fixes’ a wordpress 2.0.1 database? or is there a tool that migrates a database from one host to another?

    Same Story, slightly different error message. I’m on Godaddy.com as well. it looks like this:

    WordPress database error: [Lost connection to MySQL server during query]
    DELETE FROM wp_postmeta WHERE Post_ID = 34 AND meta_key = '_tc_post_format';

    Warning: Cannot modify header information – headers already sent by (output started at /home/content/m/a/i/mailman0/html/wp-includes/wp-db.php:102) in /home/content/m/a/i/mailman0/html/wp-admin/post.php on line 122

    i found a fix that works for me.

    in the my.cnf (/etc/mysql/my.cnf on apache) i had the following line
    wait_timeout 15

    i changed that to 30 (and later to 50 to be sure) and i did not encounter the error again.

    i think we need a little exta time to ping…

    hope it works for you as well.

Viewing 15 replies - 1 through 15 (of 20 total)
  • The topic ‘GoDaddy and INSERT INTO wp_postmeta issues’ is closed to new replies.
Skip to toolbar