Boost crawler did not get a 200 response.
404 returned. Crawler URL (http://cooperpointjournal.com/boost-crawler?nocache=1&key=ff7932f242d709...) is not available
| Comment | File | Size | Author |
|---|---|---|---|
| #12 | boost-567748.patch | 656 bytes | mikeytown2 |
Boost crawler did not get a 200 response.
404 returned. Crawler URL (http://cooperpointjournal.com/boost-crawler?nocache=1&key=ff7932f242d709...) is not available
| Comment | File | Size | Author |
|---|---|---|---|
| #12 | boost-567748.patch | 656 bytes | mikeytown2 |
Comments
Comment #1
mikeytown2 commentedTry flushing your caches. At the bottom of the performance page there is a "Clear cached data" button, try that and let me know if it works. Issue might have to do with the menu_router cache (cache_menu table).
Comment #2
mikeytown2 commentedNote to self, don't include the cron key in the error report output.
Comment #3
mikeytown2 commentedfixed so error doesn't output crawler key. Postponed until I hear back from seth.vincent in regards to the cache flush.
Comment #4
seth.vincent commentedthanks for your response!
flushing caches did not work on two different sites. what other information could i offer that would be helpful?
Comment #5
mikeytown2 commentedTry the latest dev, a bunch of errors where identified and fixed. Once #567808: Write update function to change .js to .json goes in, RC5 should be out the door, and hopefully people won't be getting these errors. Let me know what # it gave (if not 404) you just in case it's something else.
Comment #6
dbeall commentedWas going to run the newest dev yesterday, but never got to it.. work got in the way.
Version Updated from allow_url_fopen to current stable, could this be the reason?
All seems to normal, cleared cache, regenerate as expected.
error:
Boost crawler did not get a 200 response.
0 returned. Crawler URL (http://www.davebeall.com/boost-crawler) is not available, please report this issue
steps:
Upload 6.x-1.0, ran update.php, no database changes, run cron, received error on status page.
DbLog looks ok:
cron Sep 13 2009 - 17:32 Cron run completed. dave
boost Sep 13 2009 - 17:31 Crawler Start ... dave
update Sep 13 2009 - 17:25 Attempted to fetch information about all available ... dave view
boost Sep 13 2009 - 17:25 Flushed ALL files from static page cache. dave
After looking at DbLog, then return to status page minutes later, error is gone:
Boost Boost Installed correctly, should be working if properly configured.
maybe nothing...
EDIT: URL davebeall.com
Comment #7
mikeytown2 commentedmust have been some random error since a 0 for a http status code is not standard.
http://en.wikipedia.org/wiki/List_of_HTTP_status_codes
Comment #8
seth.vincent commentedI'm testing the latest version and still getting the same error.
When I run cron I get this:
Boost: Crawler is already running. Attempt to start crawler failed.
Comment #9
mikeytown2 commented@seth.vincent
Testing the url at the top, I get a 200 response. Go to
admin/settings/performance/boost
Boost crawler
and under live info, press the "stop crawler" button.
Comment #10
seth.vincent commentedI disabled the cron crawler and now my status report says that Boost should be working properly.
Cron is currently set to run every minute, which seems unnecessary. Maybe cron crawler kept trying to run and kept running into itself? Like the old snake game?
Is there a way to tell about how long cron crawler takes to finish?
Comment #11
mikeytown2 commentedRun this; will let you know how long it will take the crawler to finish, if its crawling every page.
Comment #12
mikeytown2 commentedfor #8
Crawler has a variable timeout, that guesses when a thread should be considered dead, and needs to be restarted. I forgot to change this to seconds instead of milliseconds.
Comment #13
mikeytown2 commentedcommitted