Reword crawler error message on status page [#612326]

Boost crawler did not get a 200 response.
403 returned. Crawler URL (https://www.gatedev.com/boost-crawler) is not available,

Actually, I'm only reporting this because you asked for it ... this occurs on my development site after restoring from the latest DB backup ... the main site works fine but on the restored version I get the above error in the status report. In all other respects the restored site works perfectly, albeit with a completely different name. (http://www.gatevillage.com becomes http://www.gatedev.com). Of possible relevance is that I use the Elysia Cron with a cron key but that is not new nor unique to either setup (they are as identical as I can make them without having them called the same)

Not sure what other information is relevant but I'll answer whatever questions you might have.

Comment	File	Size	Author
#3	boost-612326.patch	2.48 KB	mikeytown2
#3

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

mikeytown2 CreditAttribution: mikeytown2 commented 23 October 2009 at 02:40

Title:	Boost crawler did not get a 200 response.	» Boost crawler did not get a 200 response.
Category:	bug	» support

Thanks for the report, Does the error go away when you press the 'Clear cached data' button on the performance page? I'll be changing this status error report with instructions for each error code, so people can fix it.

Comment #2

Froggie-2 CreditAttribution: Froggie-2 commented 23 October 2009 at 06:13

Hi Dave, I had a similar situation recently after restoring from the latest back up on a new server but after several cron runs and re setting of boost crawler on the Performance>Boost page the error vanished and the crawler started to work.
Don't know if this is of any help but I just thought I should bring it to your notice.

Comment #3

mikeytown2 CreditAttribution: mikeytown2 commented 23 October 2009 at 09:21

Status:

Active

» Needs review

File	Size
boost-612326.patch	2.48 KB

Comment #4

Dave Kinchlea CreditAttribution: Dave Kinchlea commented 23 October 2009 at 12:10

I hope to not have to reset the cache if possible (I know, I know, different host names mean that the cache isn't valid in any case but the dev site provides multiple services) but doing so did in fact fix the problem. I'll try out the patch and verify it provides the feedback you are hoping it will.

Cheers

Comment #5

mikeytown2 CreditAttribution: mikeytown2 commented 23 October 2009 at 15:47

You don't have to clear the boost cache, just the caches that come with Drupal; mainly the menu cache, so the downside to doing this should be a lot smaller then what you may have in mind.