XML Sitemap Generator has notified errors

Status
Not open for further replies.

iman24

Banned
Banned
572
2010
67
0
i had installed XML Sitemap Generator on my site
and works fine but since 3 weeks ago
it didn't generate or update the sitemap
so i tried to make it manually but it shows errors


# There was a problem while notifying Google. View result
# There was a problem while notifying Bing. View result
# Ask.com was successfully notified about changes.
# It took 5.22 seconds to notify Ask.com, maybe you want to disable this feature to reduce the building time.
# The building process took about 25.52 seconds to complete and used 26.25 MB of memory.
i made the following steps

* disabled notify Ask.com
* reduce number of the posts
* increase memory usage

but no luck at all and has the same errors
also here is the Errors in debug function


Notice: WP HTTP API Web Request failed: name lookup timed out in /home/xxxxxx/public_html/wp-content/plugins/google-sitemap-generator/sitemap-core.php on line 2364
Notice: Failed to ping Google: in /home/xxxxxx/public_html/wp-content/plugins/google-sitemap-generator/sitemap-core.php on line 2201
Notice: WP HTTP API Web Request failed: name lookup timed out in /home/xxxxxx/public_html/wp-content/plugins/google-sitemap-generator/sitemap-core.php on line 2364
Notice: Failed to ping Bing: in /home/xxxxxx/public_html/wp-content/plugins/google-sitemap-generator/sitemap-core.php on line 2228

P.S.: my site on Shared Host Server
Thanks
 
4 comments
Mine started doing this a while ago and I assumed it was some kind of routing error, although I could successful connect to google and bing at the time.

In the end I just switched to BWP Google XML Sitemaps and it works much better.
 
BWP works by pinging search engines when you post something new. When a spider crawls your site, the sitemap it is rebuilt, hence why I think it is much better than the standard google sitemaps plugin (less load).

It sounds like you are having dns and/or routing issues and the name lookup error is almost certainly dns related. I would try changing the nameservers your server is using (see resolv.conf) or if you don't have root access, raise a ticket with your host.
 
Status
Not open for further replies.
Back
Top