WordPress.org

Ready to get started?Download WordPress

Forums

GoDaddy and INSERT INTO wp_postmeta issues (21 posts)

  1. Mischievous
    Member
    Posted 8 years ago #

    Hello,

    I am in the process of transferring a website I built for a friend from my server to his (unfortunately hosted on GoDaddy). I moved the installation following the easy instructions outlined here (http://codex.wordpress.org/Moving_WordPress#Moving_WordPress_to_a_New_Server)

    The site worked perfectly on my server. And at first blush seems to work well on his, but upon closer inspection I noticed when editing existing posts I get this error...

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

    Warning: Cannot modify header information - headers already sent by (output started at /home/content/s/h/y/shystie/html/wp/wp-includes/wp-db.php:102) in /home/content/s/h/y/shystie/html/wp/wp-admin/post.php on line 122

    After going back to the index the posts are updated to reflect the changes, but the error is unnerving. When I enter an entirely new post, there is no issue.

    I did some research and saw a few posts related to extra whitespace in the file causing the "headers already sent" error. I checked wp-db (in Notepad 2) and there was no extra whitespace.

    If anyone has any tips or pointers it would be greatly appreciated.

    Thanks,
    Shoshanna

  2. j9bluenile
    Member
    Posted 8 years ago #

    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

  3. Mischievous
    Member
    Posted 8 years ago #

    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

  4. FlawlessKnockoff
    Member
    Posted 8 years ago #

    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???

  5. mookid
    Member
    Posted 8 years ago #

    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...]

  6. klix
    Member
    Posted 8 years ago #

    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

  7. davidchait
    Member
    Posted 8 years ago #

    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.

  8. bornfamous
    Member
    Posted 8 years ago #

    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')

  9. mashable
    Member
    Posted 8 years ago #

    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.

  10. bornfamous
    Member
    Posted 8 years ago #

    Mine isn't hosted by godaddy, but fatcow.

  11. Mischievous
    Member
    Posted 8 years ago #

    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...

  12. jltomcat
    Member
    Posted 8 years ago #

    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

  13. dholster
    Member
    Posted 8 years ago #

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

  14. jurg2yellowscom
    Member
    Posted 8 years ago #

    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?

  15. mailman0
    Member
    Posted 8 years ago #

    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

  16. jurg2yellowscom
    Member
    Posted 8 years ago #

    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.

  17. hovercrafter
    Member
    Posted 8 years ago #

    I have WP 2.0.1 and run on GoDaddy and was having the same problem. I found a plugin that seems to fix it. Its the No Ping Wait plugin available here:

    http://somethingunpredictable.com/wp-no-ping-wait/

    Just upload and activate and your all set. Apparently its timing out when pinging other blogs. I don't have any trackbacks on my blog yet but it sure did the trick for me.

  18. FlawlessKnockoff
    Member
    Posted 8 years ago #

    Thank you oh so VERY VERY MUCH, hovercrafter!

    It works! No more "White Screen of Death"!

  19. 8wheels
    Member
    Posted 8 years ago #

    Yes, thank youse veby veby much!

  20. MaryRobinette
    Member
    Posted 8 years ago #

    I transferred to WP websites to a new host. One transferred fine, but the other gets the "preg_match(): No ending delimiter '!' found in..." I tried the no_ping plugin but it didn't fix the problem. I'll let you know if I find anything that does.

  21. MaryRobinette
    Member
    Posted 8 years ago #

    I've got no idea what I fixed, but this is what I did. I dropped all the tables in the database and reinstalled them from the file I had backed up at my old location. The "preg_match" error was still showing up. I updated my permalink structure and the error message magically vanished. I've got no idea why.

Topic Closed

This topic has been closed to new replies.

About this Topic