Quantcast
Channel: Issues for XML sitemap
Viewing all articles
Browse latest Browse all 1238

Problems running cron to build the sitemap on large sites

$
0
0

Hi,
I am unable to generate a sitemap with 6.x-2.0-alpha2.
I have a Drupal 6.13 site with almost 200k nodes, of which, ideally I would like to put about 70k in the sitemap.

I've installed the module, followed the readme.txt instructions, however I don't seem able to get the module to generate a sitemap either on cron or using the rebuild function. Cron times out when the module is installed, and when I use the rebuild function the module progress bar shows it is processing the records (and it does seem to populate the xmlsitemap table in the database) but the process terminates with an error message like: "An error has occurred.Please continue to the error page An HTTP error 500 occurred. /batch?id=13&op=do" . Returning to admin/settings/xmlsitemap confirms that the sitemap is out of sync and needs to be rebuilt. And there is no data at sitemap.xml (although the module has sometimes produced an index page of links to sitemap pages, although these pages are empty).

I am aware that the volume of pages I want to index is an issue, so have experimented with the "Maximum number of sitemap links to process at once" and other settings. And have also set content to be excluded from the sitemap, have even tried excluding everything except a few nodes or menu links. I have also uninstalled and reinstalled the module twice (NB I did receive error messages on one of these uninstalls - as per issue- http://drupal.org/node/705226 - not sure if this is an issue?). However the same errors, both with cron and with the rebuild function, persist regardless.

Before upgrading to 6.x-2.0-alpha2, I was using 6.x-2.0-unstable5. With this version I was able to successfully build the sitemap - the rebuild function worked exactly as expected- although a little while later had problems with Cron timeouts (which I think occurred once the "Minimum Sitemap Lifetime" period I had specified expired).

I hope you can help point me to a solution. Not sure if this a bug I've uncovered or an issue with how I have configured the module. Is there a site size limitation on the module?
Thanks very much for the module, and appreciate your help.


Viewing all articles
Browse latest Browse all 1238

Trending Articles