WP 3.0.1, Blogger Import, php_network_getaddresses: getaddrinfo failed

  • I have just installed WP3.0.1. I need to import a long-standing Blogger blog. I have once exported this blog to wp.com in the past, which worked with some borks. As a result, I wish to import the canonical version of the blog from blogspot.com.

    I have installed the Blogger import plugin.

    Running it, I get asked to sign in to Google (done), and grant access to Blogger (done). My Blogspot account shows that my new website has been granted access to Blogger.

    Let’s import.

    I get two duplicate error messages:

    Could not connect to
    There was a problem opening a connection to Blogger. This is what went wrong:
    php_network_getaddresses: getaddrinfo failed: Name or service not known (0)
    Could not connect to
    There was a problem opening a connection to Blogger. This is what went wrong:
    php_network_getaddresses: getaddrinfo failed: Name or service not known (0)

    However, there has clearly been communication between my WP install and Blogger, as the “magic button” appears along with the blog name and posts/comments counts. The counts, though, are both set to zero.

    The error seems to be vaguely as if there was a DNS or connectivity issue (getaddrinfo() failed) but there *is* clearly connectivity. I can ping blogger.com, google.com, and blogspot.com from my server’s command line, so again, there is connectivity.

    I wonder if there is some sort of poorly handled 302-redirect issue?

    (Also, WordPress won’t let me update plugins from the web interface – it doesn’t like my FTP pwd. I have checked this and it is correct. Further, I can happily sftp.)

    However, interestingly, I can’t reach googleusercontent.com…

Viewing 11 replies - 1 through 11 (of 11 total)
  • Thread Starter yorksranter

    (@yorksranter)

    Also, trying to use RSS Importer got an error asking if /wp-content/ was “writable by the server”.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    Sounds like googles being tetchy again. Have you skimmed through these posts: https://www.ads-software.com/tags/blogger

    Thread Starter yorksranter

    (@yorksranter)

    yes, just tried the hack of (re-) importing to wp.com, exporting that – importing from google to wp.com is failing with the same error.

    Thread Starter yorksranter

    (@yorksranter)

    so you actually imagine that was a valid or helpful reply? strange…

    current situation: no (no) exports from blogger->wordpress or blogger->wordpress.com. same errors. blogger file export working again. blogger2wordpress just drops the TCP connection when I try to upload to it.

    there are rumours that it’s possible to upload the export file to wp, but the only plugin that seems to fit is RSS Importer, which has an 8MB hard limit (why? why? why? why bother being *deliberately* [moronic expletive deleted]?)

    I do not want to learn PHP in order to upload some html files. this is poor.

    Thread Starter yorksranter

    (@yorksranter)

    also, would there happen to be a log file anywhere that might perhaps inform us as to what, in fact, is going wrong?

    Moderator James Huff

    (@macmanx)

    If it failed importing to WordPress.com, then the error is more than likely on Google’s end, which has been happening a lot lately. Since Google is pain to get a hold of, I recommend contacting WordPress.com support (don’t mention your self-hosted blog) as they have more resources to investigate the cause and implement a work-around.

    Afterwards, you can use the blogger to wordpress.com to WordPress work-around until either a fix is rolled into the WordPress core or Google fixes whatever is wrong on their end.

    Thread Starter yorksranter

    (@yorksranter)

    blogger to wordpress.com to WordPress work-around

    I tried this (see above). I had to upload a 12MB blogger dump on a sub-100kbps link! 12 hours later, no sign of the import being “processed”. Special wp.com blog now deleted. No great loss – I suspect that had they actually imported, they’d have broken all my ManyEyes visualisations and KML maps etc because WP.com kills anything with a <script> tag.

    This is getting to be an absolute disaster. WP has regressed over three years.

    Moderator James Huff

    (@macmanx)

    I tried this (see above).

    So, try it again and contact WordPress.com support if you run into a problem. Like I said, “they have more resources to investigate the cause and implement a work-around.”

    They were the ones who came up with the fix the last time Google changed Blogger’s export procedure.

    I suspect that had they actually imported, they’d have broken all my ManyEyes visualisations and KML maps etc because WP.com kills anything with a <script> tag.

    So does the self-installed WordPress, unless you have a plugin installed to use <script> in posts. It’s been this way since WordPress was first released. The <script> tags won’t be stripped out of your posts, they just won’t display.

    Thread Starter yorksranter

    (@yorksranter)

    OK, this utterly trivial migration has now wasted *three weeks* of my valuable time.

    WordPress.com have answered suggesting I should try again. Perhaps I may respectfully submit that someone could endeavour to ask them what they have changed and patch the blogger plugin?

    Although I don’t know PHP, I’ve been reading the code, and I conclude the problem is in result parsing. As far as I can see, the Google quasi-OAuth authorisation is working, and although the request for the blog metafeed usually times out a couple of times, the plugin handles this. What seems to fail is the metafeed parsing.

    Thread Starter yorksranter

    (@yorksranter)

    ….bump! Seriously considering puking the whole thing and installing MT.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    Good luck with that. There are, from what I can tell, a couple problems.

    1) You have a LOT of posts. At 120megs of data on an export file, most uploaders will choke. They like 10mb generally. Is there any way you can split up your export into maybe per-year (or if that’s too big, per-months?)

    2) Google screwed up their oAuth stuff for everyone. WP and MT.

    3) You have posts with <script> tags in them, and NO importer will handle those gracefully because that’s a common way jerks like to import hacks. To protect your site, even MT kills them. Consider editing your export file and removing them.

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘WP 3.0.1, Blogger Import, php_network_getaddresses: getaddrinfo failed’ is closed to new replies.