From: Searcher (no email)
Date: Mon Jan 06 2003 - 10:27:04 EST
This indexing ran for over two weeks. Now I'm finding that it looks like nothing
much happened? How can I tell from this ./index -S what went wrong?
I do think I might have had a DNS problem, could it be that nothing was being
resolved?
You answered another query about why I was having a hard time running any of the
aspseek processes. It turned out that it was the directory tree permissions that
had been changed in error. The user 'aspseek' could not run ./index or anything
else within the tree. I thought your answer might be the answer to this problem but
now, as I think about it, the permissions were not changed before this run, they
were changed after the run.
I'm stumped as to why nothing seems to have been indexed? But then, because of the
permissions, I was not able to run ./index -D either, which I'm running right now.
Would that be the answer?
Here is what the database looks like;
ASPseek database statistics
Status Expired Total
-----------------------------
0 9471703 9471703 Not indexed yet
1 1082 1121 Unknown status
200 2785527 3572354 OK
204 2 7 No content
300 143 211 Multiple Choices
301 31639 44021 Moved Permanently
302 161376 209965 Moved Temporarily
400 40 66 Bad Request
401 8949 11873 Unauthorized
403 15969 19853 Forbidden
404 126123 181627 Not found
406 1 1 Not Acceptable
410 5 5 Gone
500 14051 20046 Internal Server Error
502 203 233 Bad Gateway
503 337 503 Service Unavailable
504 785 973 Gateway Timeout
508 127 147 Unknown status
-----------------------------
Total 12618062 13534709
Mike
|
|
|